{"id":2478,"date":"2007-05-17T12:28:00","date_gmt":"2007-05-17T12:28:00","guid":{"rendered":"https:\/\/test.simple-talk.com\/uncategorized\/displaying-debugging-info-for-sharepoint-errors-in-your-browser\/"},"modified":"2016-07-28T10:49:04","modified_gmt":"2016-07-28T10:49:04","slug":"displaying-debugging-info-for-sharepoint-errors-in-your-browser","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/blogs\/displaying-debugging-info-for-sharepoint-errors-in-your-browser\/","title":{"rendered":"Displaying Debugging Info for SharePoint Errors in Your Browser"},"content":{"rendered":"<p>SharePoint does a good job of hiding errors from users.&#160; Out of the box, unhandled errors in SharePoint result in a fairly non-descript page that says &#8220;An Error Occurred&#8221; (or something to that effect).&#160; Although a good practice for your end-users, it&#8217;s pretty annoying when you&#8217;re trying to get a piece of code working or a configuration setting correct.&#160; Here&#8217;s how you can display debugging information in your browser:<\/p>\n<ul>\n<li>Find the following line in your web.config:\n<p>&lt;SafeMode MaxControls=&#8221;200&#8243; CallStack=&#8221;false&#8221; DirectFileDependencies=&#8221;10&#8243; TotalFileDependencies=&#8221;50&#8243; AllowPageLevelTrace=&#8221;false&#8221;&gt;<\/li>\n<li>Change the CallStack attribute to true  <\/li>\n<li>Change the AllowPageLevelTrace to true  <\/li>\n<li>Find the following line in your web.config:\n<p>&lt;customErrors mode=&#8221;On&#8221; \/&gt;<\/li>\n<li>Change the mode to &#8220;Off&#8221;<\/li>\n<\/ul>\n<p>The next time you have an error, it displays the familiar ASP.NET error information page with exception details and the callstack information.&#160; Much less frustrating than a blas&#233; error message.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>SharePoint does a good job of hiding errors from users.&#160; Out of the box, unhandled errors in SharePoint result in a fairly non-descript page that says &#8220;An Error Occurred&#8221; (or something to that effect).&#160; Although a good practice for your end-users, it&#8217;s pretty annoying when you&#8217;re trying to get a piece of code working or&#8230;&hellip;<\/p>\n","protected":false},"author":46738,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2],"tags":[],"coauthors":[],"class_list":["post-2478","post","type-post","status-publish","format-standard","hentry","category-blogs"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/2478","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/users\/46738"}],"replies":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/comments?post=2478"}],"version-history":[{"count":3,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/2478\/revisions"}],"predecessor-version":[{"id":54574,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/2478\/revisions\/54574"}],"wp:attachment":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/media?parent=2478"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/categories?post=2478"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/tags?post=2478"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/coauthors?post=2478"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}