POP QUIZ: Why would you get this error from Windbg?

Problem 1

So here is the scenario.  You open a dump from when you were experiencing a problem and try to run an SOS command and you see:

0:024> !dumpheap -stat
Cannot get the ThreadStore, do you have symbols 
for the mscorwks/mscorsvr files?

What could be going on here?  Any suggestions on how to fix this?

Problem 2

Also, since we are talking about this, what about this error:

0:024> !dumpheap -stat
Failed to find runtime DLL (mscorwks.dll), 0x80004005
Extension commands need mscorwks.dll in order 
to have something to do.

As always, post your thoughts in comments and I’ll turn them on and post the solution tomorrow.

kick it on DotNetKicks.com

Comments (4)

  1. You’ve been kicked (a good thing) – Trackback from DotNetKicks.com

  2. Steven says:

    Well, based on the 0x80004005 I’d say that you don’t have read and execute permissions to c:windowsmicrosoft.net

  3. Rohit says:

    The second error will occur if the dumheap command has been run too early before the .NET runtime DLL’s have been loaded or if the dumpheap command is being run on a unmanaged process.

    The same issue might apply to Scenario #1 but I am not sure.. since never seen that message before

  4. Russ Maxwell says:

    You would also get the second error if no managed code exists in the dump taken.  For example, taking a dump of a process that runs only native…

Skip to main content