If you have developed webparts, or even made a few customization on your WSS 3.0 site, you may have met the error of the most annoying: "An unexpected error occurred", (eg in my case, the Page DispForm.aspx a simple list) and a proposal to clear some webparts on the page, they could pose a problem. The problem is that there is no indication of the nature of the error, nor trace...Gold MOSS / WSS 3.0 is the ASP. NET and ASP.NET developers know it is possible to hide or enable error messages + track the display. It happens of course in the web.config file. We must change:
Code:
<SafeMode MaxControl = "200" callstack = "false"
AllowPageLevelTrace = "false "....
in
<SafeMode MaxControl = "200" callstack = "true" AllowPageLevelTrace = "false" ...
and disable custom errors in putting "Off":
<customErrors mode="On"/>
to replace
<customErrors mode="Off"/>
Once changed, save the web.config file. (However, this causes an application pool recycling, and disconnect any current users.). The next call to the page, the error becomes a page classic ASP.NET, and is clearly more meaningful to debug!
Bookmarks