I Have an ASP.NET 500 Error
The Web-based ASP.NET program and sites do not always run according to plan, even when the underlying program code is correct. Programs that refuse to open or that open and crash, as well as the appearance of intermittent, cryptic error messages -- including 500 errors -- can leave you unsure of where to turn and even more uncertain about how to solve the problem. In the case of an ASP.NET 500 error, the “fix” is out of your hands. Information can, however, ease some of your uncertainty and provide a direction in which to turn for help.
Other People Are Reading
-
Facts
-
An ASP.NET 500 error is a server-side error, meaning it generates from a problem with the server running the website rather than from your computer, or from how you use the program. While the resulting error message may differ according to how the ASP.NET developer chooses to display the message, most include terms such as “HTTP Error 500 Internal Server Error,” “HTTP Error 500” or “500 Internal Server Error” somewhere in the statement. Regardless of what the messages say, however, all identify the same standard 500 HTTP status code that means “The server cannot complete the request because it encountered an error.”
Behind-the-Scenes
-
ASP.NET 500 errors generate more than just an error message on your computer screen. Log files in the site directory record and store information about the error. Depending on how the site administrator configures error message reporting, she may see the same error message as you -- with an option to turn off the “friendly message” to get to the root of the problem -- or see a message detailing the problem.
-
Cause
-
ASP.NET 500 errors most often originate from one of seven possible problems. While all you see is the general error message, the site administrator sees the 500 error along with a two-digit code that provides additional information about the source of the error. Going in order of the severity of the problem, from the least to the most severe, the site administrator sees the following codes:
500.12 - Application is busy restarting on the Web server
500.13 - Web server is too busy
500.15 - Direct requests for Global.asa are not allowed
500.16 - UNC authorization credentials are incorrect
500.18 - URL authorization store cannot be opened
500.19 - Data for this file is configured improperly in the metabase
500.100 - Internal ASP error - this error refers to internal ASP.NET coding errors
Action Steps
-
Correcting ASP.NET 500 errors is the responsibility of the website administrator. Because you cannot correct the problem on your own and 500 errors are most often only temporary, Microsoft recommends first closing out of and then returning to the site later. Contact the site administrator if the 500 error is still present when you return. Look for a link that says "Contact the site administrator to report problems” or get administrator contact information in the “Contact Us” or the “About” section of the website.
-
References
- Photo Credit Thinkstock Images/Comstock/Getty Images
