Master-SharePoint.com SharePoint Resource Blog

A common change to the web.config file for a SharePoint instance is to enable custom errors, and the stack trace of an error when it ocurrs.  Enabling custom errors will result in a more detailed description being displayed instead of the “An Unexpected Error has Ocurred” message or similar.  This will help when troubeshooting issues, as it will tell you where the problem is, or at least point you in the right direction.

The article SharePoint Web.Config: How to Show Full Errors explains the various configuration changes which can be made in order to display more information when an error ocurrs, including enabling custom errors, enabling the call Stack Trace feature, enabling debugging mode, and enabling the ASP.NET tracing feature.  Additional information and tips are also provided for when making changes to web.config files relating to some important steps and considerations which should be taken before making and applying changes to a web.config file.

SharePoint Web.Config: How to Show Full Errors

1. Where is SharePoint web.config?
2. SharePoint Web.Config
3. SharePoint Designer Workflow Error Resolutions & Workarounds
4. InfoPath Error – Updating Content Type Failed When Publishing to SharePoint
5. Managed Properties Not Populating with Data – Metadata Property Mappings

Tags: SharePoint, SharePoint Administration, SharePoint Troubleshooting, Web.Config

This entry was posted on Sunday, January 24th, 2010 at 11:21 am and is filed under MOSS 2007, SharePoint, SharePoint Administration, Troubleshooting. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.