I know it is now five years after you posted your question, and who knows if you'll ever read this response.
But I had the same problem, and finally figured out the solution so I'll post it for others who may happen upon it. On 64-bit systems, the "Enable32BitAppOnWin64" is usually set to FALSE by default, so this causes the 500 error when running PerlEX (which is only included in the 32-bit release of ActivePerl). Here's what you do: in IIS, go into whichever application pool contains PerlEx (on my system it's just "DefaultAppPool"), then click "Set Application Pool Defaults". You'll see the option for "Enable 32-bit Applications" and you can set that to TRUE. You may have to re-start the web site / web server for it to take effect. Hopefully this will save someone the 2 hours of research I had to do to find this solution.... shew. - Larry McP. >________________________________ > From: Bryan M. Kramer <bryan.kra...@medeagroup.com> >To: activeperl@listserv.activestate.com >Sent: Tuesday, October 2, 2007 10:09 AM >Subject: PerlEx on windows server 2003, 64 bit > >PerlEx (from the latest ActivePerl 5.8.8 installer) (e.g. >http://localhost/PerlEx/env.plex) fails with a HTTP 500 - internal >server error on Windows Server 2003 - 64 bit. There are no >Perl/bin/PerlEx-Err*.log files, so it appears PerlEx isn't even getting >started. > >Does anyone know why this might be the case? I assumed that Windows >server would run the dll in 32 bit emulation mode. > >Thanks in advance >Bryan M. Kramer >_______________________________________________ >ActivePerl mailing list >ActivePerl@listserv.ActiveState.com >To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs > > > _______________________________________________ ActivePerl mailing list ActivePerl@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
