Looks to me like you need to allow script and/or executable permission on the "business_subjects" subfolder. You should be able to do this in IIS (right-click on the folder in IIS and choose properties). If you allow executable permission, then don't allow write permission on the same folder, as this opens a potential opportunity for someone to write an executable to the folder and run it.

Veritant:

Looks to me like you need to allow script and/or executable permission on the "business_subjects" subfolder. You should be able to do this in IIS (right-click on the folder in IIS and choose properties). If you allow executable permission, then don't allow write permission on the same folder, as this opens a potential opportunity for someone to write an executable to the folder and run it.

Ok, I finally got it working.  I got the Admin guy at our work to give read/execute permission to cscript.exe in the windows/system32 directory.

Now that I got that working, I am having problems with the script actually doing anything.  If I double click the script from the server, a PDF file gets created w/o a problem.  If I actually execute the script via an ASP page, it says it runs successfully but no file gets created.

What should I look at now?  Sorry for bothering you so much but I am still learning.

Thx
jonpfl

I think the most likely problem is, again, permissions on folders - this time write permission for the pdf file. When you run the script yourself it will be run with your own user id's permissions, and you have the necessary permission to write to the folder. When it is run from the asp page, the user will probably be whatever has been set up in IIS as the user account for anonymous access (I think this is by default something like IUSR_<server name>). It is likely that this user does not have write permissions on the folder to which the application is trying to write the pdf.

Another possibility: I think when you double-click on a vbs script, the default is to use wscript, not cscript. There may be some difference between these when running your script. Is there any input required to the script when it is run that it may be failing on?

There's still a permission problem somewhere. Some suggestions...

1. Try putting the email code directly in the asp page, and see if it runs OK. As a matter of interest, why are you running it in a separate shell anyway?

2. Have you allowed script & executable permission on the \credit_reporting\maintenance\business_subjects (virtual) folder within IIS itself?

3. I thought you would have to set the SMTP server address, email account name and email account password as parameters on the Message object before you can send?