You might want to check out Cannot run Perl under IIS or this.
Check to make sure you have E:\Perl (or whatever is appropriate for your isntallation) in your PATH environment variable.
Also, you need to have the same .pl extension defined at the OS level (file types within the folder options applet) | [reply] |
be sure you set up your virtual web directory correctly,
in which your cgi scripts are running. you have to assign
that directory the propper rights to run these scripts.
with your installation should be everything ok, cause the
installer from activeperl works very fine.
but the best would be, if you tell us the error message
you get when you try to access the script.
pitbull3000 | [reply] |
I uninstalled Perl and reinstalled it. Same behaviour. Perl works from the command prompt.
Here's the error when I click on the link:
"you have chosen to download a file from this location ..."
The virtual directory where the perl script resides has:
script source access - OFF
read - ON
write - OFF
Directory browsing - OFF
log access - ON
index this resource - ON
IIS seems to be configured to think a .pl is a downloadable file. This even though the "Home Directory - Configuration - Application Configuration clearly has:
Extention - .pl
Executable path - e:\perl\bin\perl.exe -T %s %s
Verbs - (all)
One can actually download the source if one says "save" when the download window is presented. If one choses "run from this location" a DOS box opens, shows the output of the execution and then closes.
| [reply] |
Contents of your PATH env var? E:\Perl\bin\ needs to be in there.
You say that the script mapping is configured a certain
way, but have you checked to make sure it is defined both
for the top level and the server instance below? The top
level in the IIS Manager is the machine name. Server instances
run under it in the tree display of the Manager and is
named 'WWW Server' by default. Perhaps
you have the top level script mapping defined,
but there is an anomaly in the server instance.
Try perl -V and check to mak sure the @INC paths are right.
| [reply] |
| [reply] |
| [reply] |