Question for young techies.

Thanks, but even that's over my head.
Anyway, I'm bald as a cue ball. I don't have plug ins.
Probably should have gotten them decades ago.
 
NiftyNiblick said:
Thanks, but even that's over my head.
Anyway, I'm bald as a cue ball. I don't have plug ins.
Probably should have gotten them decades ago.
Click to expand...

yeah, you have plugins, everyone does. They are special little programs intended to help your computer do work with your browser. Here are some more specific descriptions, look for that 2nd number after the 500:

  • 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. A configuration or inbound rule execution error occurred.
  • 500.51: A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.
  • 500.52: A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.
  • 500.53: A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling. An outbound rule execution error occurred. The rule is configured to be executed before the output user cache gets updated.
  • 500.100: Internal ASP error.

Sometimes its going to be "them". Best bet is t try again later. They may just be busy.
 
Celticguy said:
yeah, you have plugins, everyone does. They are special little programs intended to help your computer do work with your browser. Here are some more specific descriptions, look for that 2nd number after the 500:

  • 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. A configuration or inbound rule execution error occurred.
  • 500.51: A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.
  • 500.52: A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.
  • 500.53: A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling. An outbound rule execution error occurred. The rule is configured to be executed before the output user cache gets updated.
  • 500.100: Internal ASP error.

Sometimes its going to be "them". Best bet is t try again later. They may just be busy.
Click to expand...

Thanks. I'll try to figure it out. The message didn't give me a suffix after 500.
I suspect it was an accidentally corrupted file in a post that I tried to make, and the website won't let me get on the thread to delete the offending post.
 
You must log in or register to reply here.
Back
Top