By default (and this is a good thing), SharePoint displays a simple generic "an error has occurred" message when a problem arises. In troubleshooting these problems, it's useful to turn on more descriptive error messages.
The first thing to realize in any discussion of detailed error messages on the web is that it's generally not a good thing to keep your site configured to display details of the errors that are generated; it can reveal much about your infrastructure and security that is best kept secret.
So: when you make these changes, be sure to unmake them later.
Locating Web.config
Configuring SharePoint to display a details (including a stack trace) of its errors involves two simple changes to the web.config file that is stored in the root of the affected web site. Hopefully, in setting SharePoint up, you opted to use meaningful names for the web sites. If, however, that didn't happen, call up the Web Application List in SharePoint's application management tab. You'll see a list of the sites (name) and their respective URLs. Those names correspond to the site names in IIS.
Of course, SharePoint doesn't care where that document root is, so if you don't already know where the document root is, open up IIS manager and view the web site's properties. Click on the Home Directory tab, and you'll see the path to use. web.config will be in that directory.
Modifying Web.config
Having located web.config, open it in a text editor, and find the following line:
<customerrors mode="on" />
Change the above setting to Off.
This tells the web app server to display errors as they occur, instead of the generic SharePoint-defined custom error of "An Error occurred."
Likewise, find
<SafeMode MaxControls="200" Callstack="false"
Change the false above to true.
This tells the web app server to display the error stack when an error occurs.
When you save your changes, you should be set, and your SharePoint errors now will display as they occur.
No comments:
Post a Comment
Thanks for leaving a comment!