I found the cause of the problem, it is detailed here: http://beta.fogbugz.com/default.asp?fogbugz.4.7553.7
Deleting the invalid script mime mappings fixed the problem. 1) The installer should not create an invalid entry 2) The uninstaller should remove them I hope this gets fixed in a future release. Doesn't do much to instill confidence in perl for the uninitiated at work. $Bill Luebkert wrote: > David Stanaway wrote: > >> Hello, >> I just installed ActivePerl (Latest 5.8 MSI installer from website) >> (Without ISAPI, PerlScript and PerlEx) on Windows 2003 Server with IIS, >> and it caused IIS to fail. I don't have access to the system now, but >> restarting IIS did not resolve the issue. All requests were yielding 500 >> - data invalid pages. Someone that was working with me on restoring the >> system reported that they fixed the problem by removing some blank files >> that the installer had set up in the default site. I am thinking >> global.asa or something. I will find out more on Monday when I see the >> postmortem. >> >> Has anyone come across this before? There should be an option on the >> installer to not touch IIS at all. I only need perl.exe for system scripts. > > Now you know why I like zips and separate trees with no registry interaction. > ;) > > The only change you should have to make in a system to add an app is to add > the bin dir to your path or put the binaries in a global dir. _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
