Running Perl on IIS

[Bill McBride]

I am trying to set up Microsoft's IIS on my machine, running XP Pro., to run perl scipts. I have it set to execute perl5.8.0.exe for all .pl extensions. The problem I am having is that when I go to access a .pl file, perl seems to be called but it never completes its execution. This is with a script I know runs because I am running it on another system. Am I calling the right execution file? Or do I need to do something further to set up IIS properly? Thanks, Bill

[PodMaster]

Read the "Web Server Information/Config" part of ActivePerl's documentation (ActivePerl-Winfaq6.html).

[hardburn]

It's possible that the environment on your new server is different enough that the program fails. Try running this:

#! perl 
print "Content-type: text/plain\n\n";
$, = "\n";
print map { "$_: $ENV{$_}" } keys %ENV;

That ought to print out all the environment variables and should run anywhere (after modifying the shebang). If the above works, you know your installation is fine and you need to start looking into the script itself for the problem. If the above doesn't work, its almost certainly a configuration problem.

[tachyon]

Why IIS? Apache is far more suitable for Perl Hacking, has a free port for Win32, .....

[Roger]

But there are a few large global companies I know about that absolutely renounced Apache and swear by Perl asp on IIS instead. Yes you are right that Apache is more suitable for Perl CGI programming, but some people just don't seem to get it.

[inman]

Unless you have another version of perl installed, you can use perl.exe as the command to execute. The ActiveState documentation contains all of the information that you need to associate .pl scripts with perl.exe. This should have been set up when you did your perl install.

One problem to look out for is permissions. You need to make sure that the IIS virtual directory that contains your perl script has read / execute script access.

If you are running on a locked down machine (where the NTFS file permissions have been set to limit access) then you also need to make sure that the perl executable and any modules data files etc. can be read and executed by the IIS_Server user account. Typically the Users group can be granted read / execute access.

Inman

[Discipulus]

here my snipp-experience:

in the properties of the virtual web you arre intended to run pl or cgi script go to homedirectory->apllication->configuration ADD .pl c:\path\to\perlis.dll all verbs(or path\to\perle.exe %s %s)

THEN i have found that iis need, if you want to exit with html output from cgi, use CGI (-nph); this is the option no parsed headers that I don't know so well but it run.

plz share your win32/IIS code ;)
greetings lor*