perleager has asked for the wisdom of the Perl Monks concerning the following question:

I'm using a windows machine and these scripts worked fine, but when I installed ActiveState Perl and tried changing the path to #!C:/perl58/bin/perl5.8.2 (active state perl 5.8), it gave me a Internal Server 500 error?

I also tried using -w, and -wT, but no luck?

Is there any basic newbie mistake I'm doing, such as not configuring something to work with ActiveState Perl?

Thanks,

Anthony

---------------------------------- Updated:
Hey, after getting some help and researching, I found the answer to my problem.

If anyone has this type of situation you can go here and read How do I configure Microsoft IIS 4.0/IIS 5.0 to support ActivePerl?

Basically configuring your mappings/extentsions, you want to add %s %s to the end of the full perl path. :)

Once I did that, the 500 internal error problems went away and scripts seem to be working fine.

Anthony
  • Comment on 500 Internal Server Error - Using ActiveState perl

Replies are listed 'Best First'.
Re: 500 Internal Server Error - Using ActiveState perl
by chromatic (Archbishop) on Jan 07, 2004 at 04:19 UTC

    Is the binary called perl5.8.2 or perl? What does the error log say?

[reply]
[d/l]
[select]
Re: 500 Internal Server Error - Using ActiveState perl
by Roger (Parson) on Jan 07, 2004 at 04:23 UTC
    There are a few possibilities I can think of, the server log might tell you more...

    Possibility 1:
    Your Apache config has loadfile <previous_version_of_perl.dll>.

    Possibility 2:
    You haven't installed mod_perl for the newly installed Perl.

    Possibility 3:
    Need to specify the full path to the perl executable. 
    #!C:/perl58/bin/perl.exe -w

    [download]
[reply]
[d/l]
      Hey,

      Thanks for the help -

      Where can I install the mod_perl? Will using the ActiveState Perl PPM work? Also I checked the config for the loadfile , and changed it to the updated version of perl. Which one should I use?

      C:/perl58/bin/perlis.dll or C:/perl58/bin/perl58.dll?
      Or are both the same? -I tried both and both seems to still give me a 500 error message. Also where can I check the server log? I'm not really the admin of the server but I did check under adminstration tools > event viewer > and checked for any errors with 500? :(

      Anthony
[reply]
        You should load C:/perl58/bin/perl58.dll, and you definitely should install mod_perl.

        To get mod_perl:

        Official Website: http://perl.apache.org/

        To install the binary package (the quick and easy way) - open a CMD shell and then type the following:
        ppm install http://theoryx5.uwinnipeg.ca/ppms/mod_perl.ppd

        [download]
        You also need to download the mod_perl.so module from here -> http://theoryx5.uwinnipeg.ca/ppms/x86/. Drop this file under C:/Apache2/modules directory.

[reply]
[d/l]
        Also where can I check the server log?

        If you're using IIS, you're out of luck. It doesn't write error logs, and the reasearch I've done has not highlighted a hidden feature/setting either that can produce error logs. The access logs are all you get.

        --
        Barbie | Birmingham Perl Mongers | http://birmingham.pm.org/

[reply]
Re: 500 Internal Server Error - Using ActiveState perl
by bart (Canon) on Jan 07, 2004 at 10:43 UTC
    You could be missing some modules, or have some things that worked fine on an older perl but produces a warning on a newer perl. Try running the script from the command line — or at least, compile it, using 
    C:\perl58\bin\perl5.8.2 -cw yourscript.pl

    [download]
    That way you can figure out exactly what is wrong. Only proceed to try to run them via the web server, when this works fine.
[reply]
[d/l]
Re: 500 Internal Server Error - Using ActiveState perl
by MidLifeXis (Monsignor) on Jan 07, 2004 at 04:20 UTC
[reply]
Re: 500 Internal Server Error - Using ActiveState perl
by Art_XIV (Hermit) on Jan 07, 2004 at 14:24 UTC

    If you are trying to run your scripts using IIS rather than Apache then make sure you read the section 'How do I configure Microsoft IIS 4.0/IIS 5.0 to support ActivePerl?' in the Activeperl FAQ.

    Under IIS the shebang doesn't matter quite as much as making sure the the file extensions are mapped correctly.

    And use Apache instead of IIS if you can. ;)

    Hanlon's Razor - "Never attribute to malice that which can be adequately explained by stupidity"
[reply]
      Hey-

      Thanks for all the help

      I tried even using a simple print "HEllo" script to test if it works. No luck and still gives me 500 error. I tested the print hello script on the command line and works fine.

      I think reading that FAQ may just do, so going to get going on that, because right now I'm pretty sure this is a configuration problem.

      Anthony
[reply]

Back to Seekers of Perl Wisdom