WinDbg Configuration Issues Summary

. Loadby SOS.dll Mscorwks
. Symfix C:\windows\symbols

WinDbg configuration Issues Summary

1. Failed to find runtime DLL (clr.dll), 0x80004005

The correct. NET SOS version must be loaded

0:000>!clrstack
failed to find runtime DLL (clr.dll), 0x80004005
Extension commands need clr.dll in order to has something to do.
0:000>. Load C:\Windows\Microsoft.NET\Framework\v2.0.50727\sos.dll
0:000>!clrstack
Failed to load data The Access DLL, 0x80004005
Verify that 1) has a recent build of the debugger (6.2.14 or newer)
2) the file Mscorda Cwks.dll that matches your version of Mscorwks.dll was
in the version directory
3) or, if you are debugging a dump File, verify that the file
Mscordacwks_<arch>_<arch>_<version>.dll are on your symbol path.
4) You is debugging on the same architecture as the dump file.
For example, an IA64 dump file must is debugged on a IA64
machine.

You can also run the debugger command. Cordll to control the debugger ' s
Load of Mscordacwks.dll. . cordll-ve-u-L'll do a verbose reload.
If that succeeds, the SOS command should work on retry.

If You is debugging a minidump, you need to make sure that your executable
Path is pointing to Mscorwks.dll as well.

2. Failed to load data access DLL, 0x80004005

Mscordacwks.dll version is incorrect, the correct version of Mscordacwks.dll must be loaded

0:000>! Dumpheap-stat
Failed to load data access DLL, 0x80004005
Verify that 1) you have a recent build of the debugger (6.2.14 or newer)
2) The file mscordacwks.dll that matches your version of Mscorwks.dll is
In the version directory
3) or, if you is debugging a dump file, verify that the file
Mscordacwks_<arch>_<arch>_<version>.dll is on your symbol path.
4) You is debugging on the same architecture as the dump file.
For example, an IA64 dump file must is debugged on an IA64
Machine.

You can also run the debugger command. Cordll to control the debugger ' s
Load of Mscordacwks.dll. . cordll-ve-u-L'll do a verbose reload.
If that succeeds, the SOS command should work on retry.

If You is debugging a minidump, you need to make sure that your executable
Path is pointing to Mscorwks.dll as well.

3. Mscordacwks.dll version mismatch
0:000>. Cordll-ve-u-L
CLR DLL status:no load attempts
0:000>. exepath+ C:\Windows\Microsoft.NET\Framework\v2.0.50727
Executable Image Search Path is:c:\windows\microsoft.net\framework\v2.0.50727
Expanded executable Image Search Path is:c:\windows\microsoft.net\framework\v2.0.50727
0:000>! Dumpheap-stat
clrdll:c:\windows\microsoft.net\framework\v2.0.50727\mscordacwks.dll:2.0.50727.5420 f:0
doesn ' t match desired version 2.0.50727.5472 f:0
Clrdll:unable to find Mscordacwks_x86_x86_2.0.50727.5472.dll by mscorwks search
Clrdll:unable to find ' mscordacwks_x86_x86_2.0.50727.5472.dll ' on the path
Clrdll:unable to get version info for 'C:\windows\symbols\mscorwks.dll\5174DD695ad000\mscordacwks_x86_x86_2.0.50727.5472.dll', Win32 error 0n87
CLRDLL:ERROR:Unable to load DLL mscordacwks_x86_x86_2.0.50727.5472.dll, Win32 ERROR 0n87
Failed to load data access DLL, 0x80004005
Verify that 1) you have a recent build of the debugger (6.2.14 or newer)
2) The file Mscordacwks.dll that matches your version of Mscorwks.dll is
In the version directory
3) or, if you is debugging a dump file, verify that the file
Mscordacwks_<arch>_<arch>_<version>.dll is on your symbol path.
4) You is debugging on the same architecture as the dump file.
For example, an IA64 dump file must is debugged on an IA64
Machine.

You can also run the debugger command. Cordll to control the debugger ' s
Load of Mscordacwks.dll. . cordll-ve-u-L'll do a verbose reload.
If that succeeds, the SOS command should work on retry.

If You is debugging a minidump, you need to make sure that your executable
Path is pointing to Mscorwks.dll as well.

See the following path, copy the following two files (the long one to the short name) to the specified directory: Mscordacwks.dll,mscordacwks_x86_x86_2.0.50727.5472.dll