I'm having a heck of a time getting Movable Type to continue to work properly. I have it all set up working, then all the sudden, I start getting 502 errors; like Perl doesn't like IIS or something?
I'm not exactly that great with IIS or Perl at this point, but I can manage to get whatever information you may need to help. I provided the error I get from the localhost IE window below.
Thanks for any help someone can provide.
Regards,
Damon
___________________________________________________________________________
Abbreviated Install steps:
- Downloaded Fresh MT-4.25-en files
- Created new site folder C:\inetpub\blogsite\
- Copied MT files in to .\mt directory
- (IIS 7) Created new Site (blog.domain.com)
- (IIS 7) In "Handler Mappings," Created .pl & .cgi Script Maps to perl.exe "%s" %s (Make sure to add exception for ISAPI)
- (IIS 7) Create virtual directory for /mt folder (Point /mt to physical folder location (/mt maps to C:\inetpub\blogsite\mt\)
- (IIS 7) Add permissions for IUSR account with proper permissions (PERMIT: read & execute, List folder content, read, write)
- (MYSQL) In "Catalog," create new Database Schemata (movabletype)
- (MYSQL) In "User Administration," give mt_user privileges to the "movabletype" Database Schemata (SELECT, INSERT, UPDATE, DELETE, CREATE, INDEX, ALTER, CREATE_TMP_TABLE)
- (IE7) Navigate to url - "http://blog.domain.com/mt/"
- (MT) Go through MT wizard
- (MT) Site was created
Error Summary
HTTP Error 502.2 - Bad Gateway
The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are "".
Detailed Error Information
| Module |
CgiModule |
| Notification |
ExecuteRequestHandler |
| Handler |
CGI Script Map |
| Error Code |
0xc00000fd |
| Requested URL |
http://blog.domain.com:80/mt/mt.cgi |
| Physical Path |
C:\inetpub\blog.domain.com\mt\mt.cgi |
| Logon Method |
Anonymous |
| Logon User |
Anonymous |
| Failed Request Tracing Log Directory |
C:\inetpub |
Most likely causes:
- The CGI process was shut down or terminated unexpectedly before it finished processing the request.
- The CGI process has a flaw and does not return a complete set of HTTP headers.
Things you can try:
- Check the event logs on the system to see whether the CGI process is shutting down unexpectedly.
- Troubleshoot the CGI application to determine why it is not sending a complete set of HTTP headers.