ParallelFun

A Couple of Cheatsheets (reference: http://geekswithblogs.net/.NETonMyMind/archive/2006/03/14/72262.aspx  and http://blogs.msdn.com/b/alejacma/archive/2009/06/30/sos-cheat-sheet-net-2-0-3-0-3-5.aspx ): Cheatsheet #1 Starting, Attaching, Executing and Exiting Start -> All Programs -> Debugging Tools for Windows -> WinDbg F6 attach to process Ctrl-Break interrupt debugee .detach detach from a process g continue debugee execution q exit WinDbg Getting Help ? help on commands that affect the debugee .help help on commands that affect the debugger .hh command view the on line help file !help help on the extension dll at the top of the chain (e. g., SOS) Issuing Commands up arrow, down arrow, enter scroll through command history Right mouse button paste into command window Examining the Unmanaged Environment lmf list loaded modules with full path lmt list loaded modules w...

In trying to save a site using the Site Settings -> Save as Template, I received the following error: 11/15/2012 15:57:26.84  w3wp.exe (0x1A64)                        0x1944 SharePoint Foundation          General                        c42u Monitorable SPSolutionExporter: System.InvalidOperationException: The Writer is closed or in error state.     at System.Xml.XmlWellFormedWriter.AdvanceState(Token token)     at System.Xml.XmlWellFormedWriter.WriteEndElement()     at Microsoft.SharePoint.ScopedXmlWriterElement.Closer(XmlWriter writer, ScopedObjectUsage`1 wrapper)     at Microsoft.SharePoint.ScopedObjectUsage`1....

Loading SOS For sometime now I have relied on windbg to show me exceptions occuring in SharePoint. You can attach windbg to any process and view the .NET exceptions occuring at runtime between the process and the CLR, even handled exceptions. Usually the true source of the error is hidden in a wrapper and rethrown as an irrelevant exception. Thank you SharePoint. In order to view these exceptions we can attach windbg to either the w3wp.exe related to your IIS website running the SharePoint site by clicking Start => Run => inetmgr => Click on server => Worker processes, or by powershell if you are executing or can execute the relevant command through powershell you can attach the to powershell.exe process. After launching windbg and attaching to a process we need to load the Sons of Strike SOS.dll to enable viewing managed exceptions in windbg, without the SOS dll we can only view native code. To do this within the windbg command prompt of the atta...