in reply to IIS & perl - are they compatible ?

The quick answer to your question is yes, IIS and perl work fine together.

In this case, moritz is correct. You are not sending the correct header, so you are getting an error from IIS. Admittedly, the message from IIS wasn't extremely helpful, but the suggestion given was. Print the header first, using either the CGI module as indicated above or just adding print "Content-type: text/html\n\n" to the top of your script.

Replies are listed 'Best First'.
Re^2: IIS & perl - are they compatible ?
by Discipulus (Canon) on Feb 01, 2008 at 09:22 UTC
    my quick replay is: yes they are compatible BUT they does not work well together:

    1-you have to use the minor-useful perl.dll
    2-you get into a lot of blind error filled dungeon..
    3-you have many account problem
    4-if you wish to use some more complex then a primitive club it will be a pain to debug
[reply]

      I agree with all of your points, but unfortunately they don't apply just to perl. The blind dungeons and difficult to manage permissions issues are endemic to C# as well. In reality, it is the model imposed by IIS that causes most of these problems.

      That wouldn't even be so bad if it weren't for the lack of accessible, correct documentation. The LAMP world has MS beat by a mile when it comes to quality support tools.

[reply]
Re^2: IIS & perl - are they compatible ?
by Bloodnok (Vicar) on Feb 04, 2008 at 12:40 UTC
    TFT Digger ,

    Done as suggested and included the printing of a header ... still doesn't work, but the symptoms have now changed (no surprises there then, TFT M$). The error is now a 404 error - the so-called error log indicates an alternating sub-status of 00 and 02 !?!

    • The file is most definitely present (at the browsed location),
    • A web service extension is enabled allowing access to the perl binary and ...
    • that self-same binary is configured as being required to run files having a '.pl. extension and moreover, ...
    • The indicated perl binary has identical permissions to a DLL that can be run from the same location.

    P.S. I have downloaded the IIS 6 toolkit - all the tools contained therein appear to do is to present the 404 error web page in a number of different formats. What an idiot for thinking it might be useful and give me a clue (no matter how small) as to WTF is going on !!

    At last, a user level that best describes my experience :-))
[reply]
      How about the permissions on the .pl script?
[reply]

In Section Seekers of Perl Wisdom