Originally Posted by Fou-Lu
Yep, kinda sounded like a privilege issue. I remember how much of a pain it was configuring the 2003 machines with IIS, and I haven't looked back since :P
Take a look at this one: http://www.iis-aid.com/articles/trou...unable_to_fork
which indicates to modify the acl for the IIS user. I'm not sure if I like that approach, but I think it beats executing it as another user with more access.
I checked out that site & it was helpful. I tried using icacls to modify the permission on c:\windows\system32\cscript.exe but it kept saying permission was denied. I then copied cscript from \system32 to the same folder where the .vbs file is and I was then able to set the permissions on the copy of cscript to give (RX) access to it.
I also found several pages that said to create these registry keys:
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows Scripting Host
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows Scripting Host\Settings
and set the permissions to allow EVERYONE
Read access, which I did.
Doing those things made the
CScript Error: Loading your settings failed. (Access is denied. )
error go away, but the batch file still won't execute.
The batch file now contains a line like this:
c:\scripts\labor\scheduled\cscript.exe //B c:\scripts\labor\scheduled\labor.vbs /store_list:"store1;store2" /start_date:"2013-01-21" /end_date:"2013-01-24"
if I run it from the command line it works perfectly, but the
still doesn't work. I set the permissions on the .bat, and .vbs files and cscript to allow read & execute access to these accounts:
"nt authority/iusr" (shows up as iusr)
Do you have any more ideas?