 |
|
SharePoint Quick Links
|
Article Categories
|
Archives
July, 2010 (4)
June, 2010 (6)
May, 2010 (11)
April, 2010 (11)
March, 2010 (9)
February, 2010 (9)
January, 2010 (3)
December, 2009 (10)
November, 2009 (15)
October, 2009 (15)
September, 2009 (7)
August, 2009 (4)
July, 2009 (10)
June, 2009 (8)
May, 2009 (2)
April, 2009 (9)
March, 2009 (6)
February, 2009 (16)
January, 2009 (6)
December, 2008 (12)
November, 2008 (12)
October, 2008 (27)
September, 2008 (13)
August, 2008 (14)
July, 2008 (14)
June, 2008 (12)
May, 2008 (23)
April, 2008 (12)
March, 2008 (15)
February, 2008 (13)
January, 2008 (12)
December, 2007 (10)
November, 2007 (8)
October, 2007 (15)
September, 2007 (20)
August, 2007 (21)
July, 2007 (16)
June, 2007 (8)
May, 2007 (25)
April, 2007 (16)
March, 2007 (18)
February, 2007 (18)
January, 2007 (12)
December, 2006 (16)
November, 2006 (13)
October, 2006 (18)
September, 2006 (22)
August, 2006 (27)
July, 2006 (23)
June, 2006 (23)
May, 2006 (23)
April, 2006 (9)
March, 2006 (17)
February, 2006 (15)
January, 2006 (23)
December, 2005 (31)
November, 2005 (32)
October, 2005 (38)
September, 2005 (53)
August, 2005 (30)
July, 2005 (63)
June, 2005 (30)
May, 2005 (59)
April, 2005 (29)
March, 2005 (74)
February, 2005 (27)
January, 2005 (22)
December, 2004 (32)
November, 2004 (42)
October, 2004 (39)
September, 2004 (20)
August, 2004 (14)
July, 2004 (27)
June, 2004 (40)
May, 2004 (5)
April, 2004 (6)
March, 2004 (16)
February, 2004 (26)
January, 2004 (23)
December, 2003 (7)
November, 2003 (14)
October, 2003 (20)
September, 2003 (4)
|
Post Categories
|



|
 |
|
So... all you SharePoint v3 developers out there (WSS v3 / MOSS 2007)... don't you just love when you run into that dreaded SharePoint error "Unknown error occurred" message on the generic yellowish & blue page? It's about as effective as the "Service Engine Soon" light on your car dashboard. Of course, sometimes they get a bit more detailed, but you still get stuck without enough info.
One thing I do on all my development SharePoint sites is to pop open the web.config and make two tweaks so I get the familiar ASP.NET yellow screen of death (YSOD) with the true exception and underlying call stack:
- Turn the call stack on by searching for <SafeMode ... CallStack="false" ...> and change it to CallStack="true".
- Turn off the SharePoint error pages by turning off custom error pages: change <customErrors mode="On" /> to mode="Off".
Shane posted about this a few weeks back. After a few questions were posted about this, I figured I'd repost it here as well.
posted on Thursday, February 01, 2007 9:34 PM
|
|