Hosting

What are the common error codes generated fron IIS 7.0?
IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 500 error:
  • 500.0 - Module or ISAPI error occurred.
  • 500.11 - Application is shutting down on the Web server.
  • 500.12 - Application is busy restarting on the Web server.
  • 500.13 - Web server is too busy.
  • 500.15 - Direct requests for Global.asax are not allowed.
  • 500.19 - Configuration data is invalid.
  • 500.21 - Module not recognized.
  • 500.22 - An ASP.NET httpModules configuration does not apply in Managed Pipeline mode.
  • 500.23 - An ASP.NET httpHandlers configuration does not apply in Managed Pipeline mode.
  • 500.24 - An ASP.NET impersonation configuration does not apply in Managed Pipeline mode.
  • 500.50 - A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. .
  • 500.51 - A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling.
  • 500.52 - A rewrite error occurred during RQ_SEND_RESPONSE notification handling.
  • 500.53 - A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling.
  • 500.100 - Internal ASP error.
  • 501 - Header values specify a configuration that is not implemented.
  • 502 - Web server received an invalid response while acting as a gateway or proxy.
  • 502.1 - CGI application timeout.
  • 502.2 - Bad gateway.
  • 503 - Service unavailable.
  • 503.0 - Application pool unavailable.
  • 503.2 - Concurrent request limit exceeded.
    • Tips:
    Visit Microsfot KB Article 943891