permission denied Microsoft VBScript runtime error '800a0046' using WScript.Shell

OK, I did that on the script file, the batch file, the folder and wscript.exe
Still no luck.

Maybe wscript.exe is the wrong file I'm changing permissions on. (I made an assumption there).

is the batch file trying to write anything?  if so, you will need to give write permissions to the folder location where it is writing to.

the batch file has one line as follows:

ping 192.168.1.1


It doesn't return anything nor write anything yet.
I had a long fancy batch file before, but simplified it until I can figure this permissions issue out.
I think a big problem is that it is a domain controller (as in there are no local accounts) - I'll have to test it out on a W2K3 server that is not a DC.

I changed permissions on the ping.exe file as well

you might try adding the iwam_machine as a domain account.  you will have to uncheck the box that tells iis to control the password.

Yes, IWAM_machine account is already a member of Domain Users as well as the IUSR_machine account.

you are setting the iis permissions or ntfs permissions?

NTFS permissions (all set to Full Control).

I set the IIS permissions (right click on the site, selected permissions, added IUSR & IWAM, set to Full Control)

Maybe there is a bug with WScript itself with file version "5.6.0.8827" like there was in the past with version 5.0 (there was a bug mentioned in the past in this forum).
This is ridiculous.
 

I added a completely new user with full administrative rights on the entire machine.  I changed IIS, NTFS permissions as well to "God Mode" , and it STILL refuses permission!  There are no policies that I can find that would prevent this and this is basically a brand new server installation.

I have the same problem. I get "Permision Denied" error from my classic ASP page.

Here's the senerio:

This Works:
Network user FRED on his desktop opens browser and goes to site on ServerA.  ServerA runs a WScript.Shell run command on an Exe that does some stuff.

This Does NOT work:
(Same as above except, the website starts on a different server.)
Network user FRED on his desktop opens browser and goes to site on ServerB.  ServerB then does a response.redirect to a page on ServerA and that page runs same WScript.Shell run command on an Exe that does some stuff.

However, this DOES work:
(Same as above except different network user. JOE is an admin on ServerA.)
Network user JOE on his desktop opens browser and goes to site on ServerB.  ServerB then does a response.redirect to a page on ServerA and that page runs same WScript.Shell run command on an Exe that does some stuff.

In all cases, same exe, same website runs the exe, just that the web browser started from another server and it behaves differently depending on the user logged in using the browser.

Here is what I have already tried:
1) Set IWAN_machine and IUSR_machine to have full everything access to exe and dirs.
2) Set IWAN_machine and IUSR_machine as Admins on the server
3) The exe to run and folder has everyone in the world access.
4) Changed ServerA IIS default application pool to use "LOCAL SERVICE" instead of "NETWORK SERVICE" (this allowed the third senerio to work, ie JOE user it works)

I'm at my wits end and could use any insight in how to get this to work!
Thanks in advance!
---JHG

How would get the script to work if you a send a batch script to a few people who are not comfortable with changing file permissions, buy you need to copy a few files to a particular location in their documents folders using the script?

I had this problem using Windows Server 2003 and IIS. All my connection strings were correct, and filemon was not giving me any kind of error I could track down.

The problem was with the application pool on the IIS server. To fix the problem, I had to manually recycle the worker process to free up the connection. The application pool was set too generous on the amount of time to recycle.

To recycle the worker process:
1. Open IIS Manager through administrative tools
2. Expand your computer holding the web site
3. Expand the application pools
4. Find the application pool that your web site is using
5. Right click and choose recycle