SharePoint Web Application Debugging Errors

Outputting Verbose Errors Versus the Standard Error Output in SharePoint

Verbose error output to the error web page should only be enabled for development or test farms, or temporarily to fix a drastic problem in production.

We will need to edit web.config for the website.  This will be located in the IIS virtual directories, or template/admin in the SharePoint hive for central admin.

  • Turn on the call stack (CallStack="true")
  • Disable custom errors (<customErrors mode="Off" />)
  • Enable compilation debugging (<compilation batch="false" debug="true">)
Edit the following lines: (Ctrl-F is you friend)

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <configuration>
        ...
        <SharePoint>
            <SafeMode MaxControls="200"
                CallStack="true"
                DirectFileDependencies="10"
                TotalFileDependencies="50"
                AllowPageLevelTrace="false">
                ...
            </SafeMode>
        ...
        </SharePoint>
        <system.web>
            ...
            <customErrors mode="Off" />
            ...
            <compilation batch="false" debug="true">
            ...
            </compilation>
            ...
        </system.web>
        ...
    </configuration>

Restart the website.  If you have other websites and do not wish to restart the entire web server (i.e. iisreset), navigate to the website in IIS Manager, right-click, Manage Website, Restart.

Comments

Popular posts from this blog

SharePoint Designer 2013 Approval Workflow with Comments

Change SharePoint server hostname and Web Application Names

The Timer Service Failed to Recycle