StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>You need to get more debug information.</p> <p><strong>Using Visual Studio</strong></p> <p>Try setting the debugger to break on all exceptions. Go to <strong>Debug</strong>, <strong>Exceptions</strong> and tick <strong>Common Language Runtime Exceptions</strong>. Then go to <strong>Tools</strong>, <strong>Options</strong>, <strong>Debugging</strong> and untick <strong>Enable Just My Code</strong>. Finally attach to w3wp.exe. Try running your console application now and you should find that it triggers an exception in w3wp.exe. Check the stack trace and see if that gives you more information.</p> <p><strong>Using dump files</strong></p> <p>You could also try working from a crash dump. This is admittedly significantly more hard-core but should give you the detail you are otherwise lacking. The tool <a href="http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx" rel="nofollow noreferrer">ProcDump</a> will can be attached to w3wp.exe (provided the -s switch isn't used) and will create a dump if an unhandled exception occurs. If you have trouble with ProcDump, try <a href="http://blogs.technet.com/askperf/archive/2007/06/15/capturing-application-crash-dumps.aspx" rel="nofollow noreferrer">ADPlus</a> which does something similar.</p> <p>From the created dump file, use <a href="http://support.microsoft.com/kb/315263" rel="nofollow noreferrer">this KB article</a> to set up WinDbg and get started. There is an example case of how to use WinDbg on <a href="http://blogs.msdn.com/tess/archive/2006/04/27/584927.aspx" rel="nofollow noreferrer">Tess Ferrandez's blog (Strategy #2)</a>.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload