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
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] |
Okay thank you,
Would installing this solve the 500 problem you think? What if I'm not running apache?
Thanks,
Anthony
| [reply] |
Would installing this solve the 500 problem you think?
Would drinking some water solve it? You need to read the documentation for whatever webserver you're running, and you need to read your webservers error logs. Only you can help yourself.
| [reply] |
Don't tell me you are running IIS? ;-)
| [reply] |
Have a look at PerlIS (more commonly known as 'Perl for ISAPI', which comes as part of the default install with ActivePerl) from ActiveState. If you're using IIS then change the shebang line to:
#!/usr/bin/perlis.dll
If you then need to switch to Apache, without changing the shebang line, find the following line in the httpd.conf and ensure it's uncommented:
ScriptInterpreterSource registry
This will ensure you run the script against the Perl binary referenced in the registry and will ignore the shebang line. I use this to switch between IIS and Apache all the time.
--
Barbie | Birmingham Perl Mongers | http://birmingham.pm.org/
| [reply] [d/l] [select] |
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] |