Windbg.exe：无法加载数据访问DLL，0x80004005

Question

我正在尝试从 x64 计算机上运行的进程调试 32 位进程转储。我在 x64 笔记本电脑上运行 x86 版本的 Windbg。我已遵循建议这里，但我仍然得到这个：

0:000> .cordll -ve -u -l
CLR DLL status: No load attempts
0:000> !clrstack
CLRDLL: C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscordacwks.dll:4.0.30319.17020 f:8
doesn't match desired version 4.0.30319.237 f:8
CLRDLL: Loaded DLL c:\symbols\public\mscordacwks_x86_x86_4.0.30319.237.dll\4DD234A8670000\mscordacwks_x86_x86_4.0.30319.237.dll
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 clr.dll is 
                in the version directory
            3) or, if you are debugging a dump file, verify that the file 
                mscordacwks_<arch>_<arch>_<version>.dll is on your symbol path.
            4) you are debugging on the same architecture as the dump file.
                For example, an IA64 dump file must be 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 will do a verbose reload.
If that succeeds, the SOS command should work on retry.

If you are debugging a minidump, you need to make sure that your executable
path is pointing to clr.dll as well.

据我所知， mscordacwks_x86_x86_4.0.30319.237.dll 已成功加载，但我仍然收到错误。我缺少什么？

Answer 1

我通过使用 ProcDump 获取 32 位进程的 32 位转储解决了该问题那是在 64 位机器上运行的。我可以使用 32 位 Windbg 成功地检查这一点。有更多详细信息 此博文。

Answer 2

看起来您有一个 32 位转储文件 - 否则错误将类似于

CLR DLL status: ERROR: Unable to load DLL mscordacwks_AMD64_x86_2.0.50727.3053.dll, Win32 error 0n87

至少是这样到博客文章 “无法加载数据访问 DLL，0x80004005” – 或 – 什么是mscordacwks.dll？ 位于“黑暗角落笔记”博客上。

请注意错误消息中 AMD64_x86 与 x86_x86 的混合。

对我来说，这总是因为我没有正确版本的 mscordacwks。也有可能windbg找不到它。请参阅我对问题调试hang-dump in Windbg的回答我用来从安全补丁中查找/提取正确版本的一种方法。为了让 Windbg 加载它，我将 Windbg 的图像路径设置为指向我存储它的目录。