- This topic has 1 reply, 2 voices, and was last updated 13 years, 4 months ago by .
While not directly connected to Cloverleaf, we use VB scripts extensively to check engine status and other things via web browser on our test and production interface engines which run on Windows 2003 servers.
We’re upgrading to a new version of Cloverleaf running on a new Windows 2003 server with SP2. If I bring up a browser on the server, these scripts run fine. However, if I use a browser on any remote machine, the scripts fail. I was getting a wscript.exe not found error until I comment out that line, which resulted in a permission denied error.
I’ve checked settings and folder permissions between the new box and the current production box and I’m about to go crazy trying to figure out what might be wrong. I even changed the compatiblity settings on the web browser and nothing seems to help.
Anyone have an idea on what need to be done to let scripts run when not being run from localhost?
- The forum ‘General’ is closed to new topics and replies.