Prev: IIS ID7031
Next: IIS Worker Process encountered a problem and needed to close
From: David Wang [Msft] on 1 Nov 2005 17:29
1. In order to be able to execute Perl script on IIS6 you must:
- configure exactly like IIS5
- vdir has at least "ScriptS" Execute permissions
- have a .pl Application Mapping to Perl engine binary)
- remote authenticated user has permissions to both perl script and perl
engine binary
- IIS6 only: add WebServiceExtension for Perl engine binary and enable it
http://blogs.msdn.com/david.wang/archive/2005/04/20/IIS6_CGI_Web_Service_Extension.aspx

2. In order for Perl script which is executed to be able to call an EXE, you
must
- configure exactly like IIS5, including ACLs
- WS03 only: If script execution involves shell() or anything that touches
CMD.EXE, make sure that the remote authenticated user actually has
permissions to CMD.EXE (itself a security risk). WS03 security lockdown
prevents non-administrator users that log on via IIS to access system
console apps like CMD.EXE.

Finally, you must consider the possibility that your EXE may not run on
Windows Server 2003 or has elevated security requirements no longer provided
by IIS6 (You will have to determine and assess the risks yourself; IIS6
simply has no privileges and thuspassively prevent you from doing anything
until you explicitly configure it).

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"kevin" <kevin(a)discussions.microsoft.com> wrote in message
news:9ED5B12A-4DE2-4E8D-A8C5-5E82324DAA4F(a)microsoft.com...
I have made that change with no luck. I should note that the EXE being
called
resides in another directory, but that directory is in the path (I output
the
path and all the other environment variables to a log file). I have also
tried to run the exe in the script with a full pathname with no luck.

Is there any global /registry settings that cause this behavior? The script
runs fine until it has to execute the EXE. Thanks...


First  |  Prev  | 
Pages: 1 2
Prev: IIS ID7031
Next: IIS Worker Process encountered a problem and needed to close