Forum Moderators: open

Message Too Old, No Replies

WScript.Shell in Windows 2003

Why the heck isn't this working?

         

digitalv

1:43 pm on May 18, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I have a script I've been running for some time in Windows 2000 that uses WScript.Shell to run a command-line program from the web server (my own web server, not owned by a hosting company so that's not an issue).

I have the "allow service to interact with the desktop" set and I even have the Anonymous user set to ADMINISTRATOR, who has "full control" permissions on the directories I'm working with.

Here's the deal though. This script, which works fine in Windows 2000 won't work at all on a Windows 2003 server. The part that sucks is I get no error message, no this or that denied, nothing... it just doesn't work. Can anyone shed some light on this for me?

Also another note here - not only will WScript.Shell not work, but it seems NO execute components work. I tried ASPExec, ASPExecute, and I even wrote my own in Visual Basic. None of them work, so it's definitely something about Windows 2003 that's different from 2000. I'm running IIS 5 on 2003 (same version of IIS as 2000, not using IIS6).

digitalv

4:37 pm on May 18, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I figured out the problem - and discovered a bug in Windows 2003 in the process.

The user "Administrator", which I was using as the anonymous user to get this script to run, is part of the group "Administrators". The GROUP had full control permissions on the file, which should have been all that was necessary.

Here's the bug though: I added the individual USER "Administrator" to the file permissions list on the program I was trying to execute and it worked fine. So for whatever reason, in Windows 2003 the "anonymous user" has to have explicitly defined permission to execute the program, not just the group the user is in. If this isn't a bug, it's another one of Microsoft's classic "undocumented features" heh.