How to: turn off custom errors for debugging mode in SharePoint 2010 application pages
Unfortunately custom errors is a setting that lives at the SharePoint site level, not at the ‘application page / _layouts’ level, so you will have to edit the web.config that applies to the entire SharePoint site which is located at: C:inetpubwwwrootwssVirtualDirectories
Once there you’ll have to enable 3 different settings that should already be there for it to work:
- CustomErrors = ”Off” instead of the default which is ‘On’
- Debug=”true”. I keep hearing this might be set to false but in my case it shows true
- CallStack=”true”. Again, another value that is there for me by default but might not be in your setup.
Now remember that before making any chances you want to back up your web.config. It is a very long and delicate file and if you mess something up by accident rolling back your chances might be very hard.
In my case all I had to do is is go to the _layouts web.config and change the following line:
<customErrors mode=”RemoteOnly” />
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 tag within a “web.config” configuration file located in the root directory of the current web application. This 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 –>
<configuration>
<system.web>
<customErrors mode=”RemoteOnly”/>
</system.web>
</configuration>
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 configuration tag to point to a custom error page URL.
<!– Web.Config Configuration File –>
<configuration>
<system.web>
<customErrors mode=”On” defaultRedirect=”mycustompage.htm”/>
</system.web>
</configuration>
Love
Can we use Let's Encrypt, the free and open certificate authority?
Hola! gracias por la info, me sirvió el comando sacandole el nombre del server. En mi caso, fue una migración…
Yes 3rd option helped me too. I removed the WC key Values from config file then started working.
I know this is from 2014. But really, thank you!