Troubleshooting Server Error in Application

In SharePoint you may run across this specific error, and not know how to proceed. When an error of this type is thrown make sure to locate the specific SharePoint web front end (WFE) server you are using to generate the error. In theory all WFEs should have the same content. If you are not sure of which WFE then all SharePoint WFEs that are serving pages need to be modified.

ULS Logs

First, look into the ULS for SharePoint typically located at:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS

You can use the Microsoft MSDN tool called ULS Viewer to sort through the various log files. The log files are in the file structure as follows:

<SERVER>-<DATE>-<TIMESTAMP>.log

An example would look like:

SharePointWFE-20120426-1726.log

You want to sort the logs by the Date Modified attribute, and open the appropriate log file that was created when the error occured. Search for any errors, or references to your page that has the error. This might give you a clue as to the problem.

Windows Application Logs

Next, take a look at your Windows Application Event logs during the same time frame that the server threw the error. You can find the Windows Application Event logs at:

Start>Administrative Tools>Event Viewer>Windows Logs>Application

Again, remember to sort by date, and track down any event that would have been triggered at the time you generated the error.

Modifying ‘”web.config”

Another important place to look at is the actual page that is given during the error. A typical error page will look like this.

Screen shot 2012-05-11 at 15 55 39

This is telling you that it wants to show you more information about the error, but it can’t since you are not at the correct location. To change that you have to modify some values within SharePoint’s IIS web.config file. There are a couple things to caution you about:

  • When making any changes make sure to make a backup of the original web.config to a safe location. In case things go really wrong it will be easy to get back to your starting point with the backup file.
  • Each time you save the web.config the IIS system will have to restart the web service. Meaning there will be a brief interruption in SharePoint services during this time.
  • Anyone can see the error regardless of where they are browsing the page.

To get to the appropriate web.config file open your IIS manager.

Start>Administrative Tools>Internet Information Services (IIS) Manager.

Once that is open you want to ‘explore’ the physical file structure of you SharePoint site in IIS.

image

Once that is open you will see something like this…

image

Caution: Remember to make a copy of the ‘web.config’ before you make any changes!

Do a search in the web.config file, and look for the ‘customErrors’ tag. By default the mode will be set to “RemoteOnly”. change the value of the mode to “Off”.

  • Only change the value!
  • It is case sensitive

At this point save, and close, your web.config. As soon as you save the modified version of your web.config this will trigger an IIS reset of the web front end you are working on. You will want to trigger the original steps to generate the error page again to will show you more details as to what is triggering the error.

–Javi

About the Author

1 thought on “Troubleshooting Server Error in Application

    • Author gravatar

      Javier… Great post. I’ve looked through quite a few blogs and webpages on AAM, trying to get a handle on what it was and why you’d use it, and yours was hands-down the simplest and clearest explanation out there. Keep it up! 

Leave a Reply

%d bloggers like this: