Sign In
MSDN Blogs
Microsoft Blog Images
More ...
Advert
Translate This Page
Translate this page
Powered by
Microsoft® Translator
Search
Advanced search options...
Search In:
Everything
Blogs
Forums
People
Groups
Places
Pages
Date range:
All Time
Last Year
Last 6 Months
Last 3 Months
Last Month
Last Week
Last Two Days
Common Tasks
Blog Home
Email Blog Author
About
RSS for posts
Recent Posts
“A selected drive is no longer valid”–Error while Adding/Removing Features from Visual Studio 2008
Posted
over 2 years ago
by
Madhur Ahuja
0
Comments
Sharepoint Saturday in India! Apr 24 (Live Online!)
Posted
over 2 years ago
by
Madhur Ahuja
0
Comments
System.MissingMethodException: Method Not Found when running unit Tests
Posted
over 3 years ago
by
Madhur Ahuja
3
Comments
Adding Client script to TreeNode Click Event
Posted
over 4 years ago
by
Madhur Ahuja
2
Comments
Resolving Common issues while Applying Site Templates (.stp) on MOSS 2007
Posted
over 4 years ago
by
Madhur Ahuja
1
Comments
Tags
.NET
ASP.NET
Debugging
MOSS
My Site
VSTS
Web Part
WinDbg
Archives
Archives
November 2010
(1)
February 2010
(1)
January 2009
(1)
November 2008
(1)
October 2008
(2)
July 2008
(3)
April 2008
(17)
March 2008
(8)
Reveal Unknown Error on Sharepoint 2007 pages
MSDN Blogs
>
Code, Articles, Discussion on Microsoft Technologies
>
Reveal Unknown Error on Sharepoint 2007 pages
Reveal Unknown Error on Sharepoint 2007 pages
Madhur Ahuja
1 Apr 2008 12:35 AM
Comments
0
How often you have encountered the infamous Unknown Error on Sharepoint 2007 pages. If you are a Sharepoint developer, chances are that innumerable times :)
However, if you are also seasoned ASP.NET developer as well, you also know the trick behind it to reveal them., which I am going to give it here.
The trick is that ASP.NET Framework wants to show the real error message, but its the sharepoint which abstracts the message from the user. This is good for production systems since those cryptic error message may not be user friendly. Or revealing those full stack trace could cause potential security concerns.
But for an experienced developer, this is almost must to turn them off. This is achieved by turning off custom errors in web.config
Find the web.config for the site you normally use as your development site. Locate this tag
<SafeMode ... CallStack="false" ...> and change it to CallStack="true"
Set <customErrors mode="On" /> to mode="Off"
Set <compilation batch="false" debug="false"> to <compilation batch="true" debug="true">
Now you will get the full stack trace as soon as the error is raised.
0 Comments
Leave a Comment
Name
Comment
Please add 6 and 3 and type the answer here:
Post