Jean Paul's Blog

There are 2 types of People in the World, One who Likes SharePoint and..

  • Microsoft MVP

  • MindCracker MVP

  • CodeProject MVP

  • eBook on SharePoint 2010

  • eBook on Design Patterns

  • eBook on Windows Azure

  • NLayers Framework @ CodePlex

  • MSDN Forums

  • .Net vs. Java

    Due to Public Demand
  • Advertisements

Server Error in ‘/’ Application.

Posted by Paul on December 13, 2012

Server Error in ‘/’ Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed. 

Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".


<!– Web.Config Configuration File –>




        <customErrors mode="RemoteOnly"/>



Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application’s <customErrors> configuration tag to point to a custom error page URL.


<!– Web.Config Configuration File –>




        <customErrors mode="On" defaultRedirect="mycustompage.htm"/>




The Problem

Sorry for the lengthy error message.  One of my colleague mentioned about the problem.  He is new into SharePoint and was having ASP.NET background.

Changing the INETPUB web.config was not solving the problem. (making customErrors mode=”Off”)

Locations of Configuration Files

SharePoint had a series of web.config files.  Following are the locations:

  1. C:\inetpub\wwwroot\wss\VirtualDirectories\80
  2. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS

More Info:


The Solution

To modify the customErrors mode to Off, please go to the LAYOUTS folder.


Open the web.config file and modify the customErrors mode to Off.


Now you can retry the request, this time you should be getting the exact error message.

Good Luck My Friend!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s