Custom Vocabulary Internal Failure Please Try Your Request Again

Showtime published on MSDN on May 22, 2014

A "Server Error in '/' Awarding" error when browsing your Microsoft Azure Web Site tin be a flake tricky to troubleshoot if you don't know where to look for information.

Here is an example of one of these errors. Equally you lot can see, although it does not tell y'all the root cause of the error, it does tell you lot how to troubleshoot the error in the Details section. In this post we will encompass how to enable CustomErrors as well every bit another logging that may help diagnose these issues.

Server Error in '/' Application.

Runtime Mistake Description: An application error occurred on the server. The current custom error settings for this application forestall the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed past browsers running on the local server automobile.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "spider web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should and so have its "mode" aspect set to "Off".

<!-- Spider web.Config Configuration File -->

<configuration>
<system.web>
<customErrors manner="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can exist replaced past a custom error folio by modifying the "defaultRedirect" attribute of the application'southward <customErrors> configuration tag to point to a custom error folio URL.

<!-- Spider web.Config Configuration File -->

<configuration>
<organization.web>
<customErrors manner="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

First we will cover the built-in logging in Azure Web Sites and what this shows for this fault.  If you are not familiar with how to connect to your site using FTP see

How to FTP into a WAWS Site

Web Server Logging:

Equally yous can run across here, the web server logging shows an HTTP status ( sc-status ) of 500 with a sub-condition (sc-substatus ) of 0 and a Win32 condition (sc-win32–status ) of 0. This information doesn't get u.s.a. any closer to agreement the root cause of the error, simply I practise recommend checking this as in some cases these codes provide additional data. For example the status code might exist something like 500 19 where the 19 is a meaning piece of information see HTTP 500.xix Errors .

For this example nosotros volition focus on the  500 0 0 as shown in the follow IIS log entry ( Note we take removed some of the fields you might normally see.)

appointment fourth dimension s-sitename cs-method cs-uri-stem sc-status sc-substatus sc-win32-condition sc-bytes cs-bytes time-taken

2014-04-xviii 19:45:06 RMARRAZUREMGMTAPI GET /servererror.aspx 500 0 0 3847 944

More information on HTTP status codes can be found here: HTTP Status Codes

Detailed Errors

The Detailed Errors logs are located in the Logfiles/DetailedErrors folder. A log file named ErrorPagexxxxxx.htm is created for each HTTP Status code of 400 or greater.

From the proper name of the log, logically yous might think to look hither adjacent , merely from an exception perspective, this is not too helpful in this case.

EventLog.XML

The eventlog.xml file is located in the root of the LogFiles folder of your site. It may contain additional information about why an fault occurred. In the instance below, nosotros run into that in that location was an unhandled exception of type "NullReferenceException" that occurred in  ServerError.aspx.cs in the Page Load  method.

In many cases, this information may be all yous demand to fix the problem, simply there might be cases where you need more details.

This is where the customErrors settings may be helpful.

CustomErrors

The customErrors department  along with the compilation debug settings can assist when y'all demand more details about an mistake and the code where the error originated.

WARNING : This setting will expose your code to external users. Remove these settings after troubleshooting.

To use the customErrors section, add together the post-obit to the <system.spider web> department of the web.config for your site:

<customErrors mode="Off"/>
<compilation debug="true">

Reproduce the error and now you lot should run across the exception details and the line of lawmaking where it originated.

Server Error in '/' Application.

Object reference not set to an instance of an object.
Clarification: An unhandled exception occurred during the execution of the electric current web request. Delight review the stack trace for more information about the error and where it originated in the code.

Exception Details: Arrangement.NullReferenceException: Object reference not prepare to an instance of an object.

Source Fault:

Line 10: protected void Page_Load(object sender, EventArgs e)
Line 11: {
Line 12: throw new Organisation.NullReferenceException();
Line xiii: }
Line 14: }

Source File: d:\habitation\site\wwwroot\ServerError.aspx.cs Line: 12

Stack Trace:

[NullReferenceException: Object reference non set up to an instance of an object.]
ServerError.Page_Load(Object sender, EventArgs e) in d:\dwelling\site\wwwroot\ServerError.aspx.cs:12
Organization.Spider web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs east) +51
Organisation.Web.UI.Control.OnLoad(EventArgs e) +92
System.Web.UI.Control.LoadRecursive() +54
Organisation.Spider web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +772

For an example of how to get the root of an exception without using CustomErrors meet Using ELMAH in Windows Azure Web Sites .

doironusen1958.blogspot.com

Source: https://techcommunity.microsoft.com/t5/apps-on-azure-blog/azure-web-sites-troubleshooting-8220-server-error-in-application/ba-p/392307

Share this post