Recently, I have been studying SharePoint development, and it is inevitable that errors may occur frequently. For example:
Obviously, this error prompt is not helpful in solving the problem except for making people crazy, and has made ASP. net friends should have thought of modifying the website's web. config file to solve website-related problems. This method also applies to SharePoint sites. The procedure is as follows:
(1) Find the Web corresponding to the SharePoint website. config file, which is located in the following directory (X is the system disk drive letter, NNNN is the website port number): X: \ Inetpub \ wwwroot \ WSS \ virtualdirectories \ NNNN \
(2) Search for the following content in the web. config file: < SharePoint >
< Safemode Maxcontrols = "200" Callstack = "False" Directfiledependencies = "10" Totalfiledependencies = "50" Allowpageleveltrace = "False" >
< Pageparserpaths >
</ Pageparserpaths >
</ Safemode >
ThenCallstackAndAllowpageleveltraceIs set to"True".
(3) Search for the following content in the web. config file:<CustomerrorsMode= "On" />
Change it:<CustomerrorsMode= "Off" />
(4) save Web. config.
After this is done, the error message is like this. Is it too pleasing to the eye?
From: http://blog.csdn.net/jackjoy/archive/2007/07/31/1719012.aspx
