“SOS的版本与您正在调试的CLR的版本不匹配”在WinDbg？ [英] What to do with "The version of SOS does not match the version of CLR you are debugging" in WinDbg?

问题描述

我有一些应用程序出现问题。这是一个在Windows 2003 Server（x86）IIS6下运行的基于wcf的应用程序：

在事件日志中，我从W3SVC-WP源（EventID = 2262）得到这样的错误：

  ISAPI'C：\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll'报告为不健康原因如下：'检测到死锁'。 
  

我正在弄清楚发生了什么。我已经按照 KB 中的描述为孤儿工作进程创建转储。
当发生死锁时，会创建一个minidump。

然后我拿这个minidump来尝试了解发生了什么。这是我被卡住了。

我运行WinDbg x86，打开我的转储，然后：

  0：037> .loadby sos clr 
 0：037> .sympath SRV * c：\temp\symbols * http：//msdl.microsoft.com/download/symbols 
符号搜索路径是：SRV * c：\temp\symbols * http：// msdl.microsoft.com/download/symbols 
扩展符号搜索路径是：srv * c：\temp\symbols * http：//msdl.microsoft.com/download/symbols 
 0：037> ; ！clrstack 
 SOS的版本与调试的CLR版本不匹配。请加载您正在调试的CLR版本的SOS的匹配版本。 
 CLR版本：4.0.30319.1 
 SOS版本：4.0.30319.235 
 CLRDLL：C：\WINDOWS\Microsoft.NET\Framework\v4.0.30319\mscordacwks.dll： 4.0.30319.235 f：8不匹配所需的版本4.0.30319.01 f：8 
 CLRDLL：加载的DLL c：\temp\symbols\mscordacwks_x86_x86_4.0.30319.01.dll\4BA1D9EF66f000\mscordacwks_x86_x86_4。 0.30319.01.dll 
操作系统线程标识：0x690（37）
无法走管理堆栈。当前线程可能不是托管线程。 
您可以运行！线程以获取进程中的托管线程列表
  

如何处理此错误 - SOS版本与调试的CLR版本不匹配？

同样的错误（The版本的SOS与您正在调试的CLR版本不匹配）我在VS2010中打开minidump时收到。

我已经阅读了这篇文章 - a href =http://tech-thinker.com/Forums/tabid/62/forumid/12/postid/471/scope/posts/Default.aspx =noreferrer> http：// tech-thinker。 com / Forums / tabid / 62 / forumid / 12 / postid / 471 / scope / posts / Default.aspx ，并尝试安装 KB2518870 。没有帮助。

解决方案

WinDbg将无法使用调试适配器mscordacwks.dll，除非它是相同的版本作为原始机器的一个。您可以通过将生成转储的目标计算机的DLL复制到Windows目录的调试工具来解决此错误。

我们使用WinDbg调试.NET 2.0应用程序。我们会不断收到与mscordacwks_x86_x86_2.0.50727.3615.dll相同的错误。我不得不将该文件从服务器复制到我的客户端，并将其放在C：\Program Files\Debugging Tools for Windows（x86）\文件夹中。 WinDbg在此之后停止抱怨。

如果所有其他失败，您可以尝试使用WinDbg在您检索到崩溃转储的同一服务器上进行调试。

I'm having a problem with some of my apps. It's a wcf-based app running under IIS6 in Windows 2003 Server (x86):
In Event Log I get such an error from "W3SVC-WP" source (EventID=2262):

ISAPI 'C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'.

I'm trying figuring out what's going on. I've set up creating dump for Orphan Worker Process as described in this KB. When an deadlock occured a minidump is created.
Then I take this minidump to try to understand what's happened. Here's I'm stuck.

I run WinDbg x86, open my dump and then:

0:037> .loadby sos clr
0:037> .sympath SRV*c:\temp\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\temp\symbols*http://msdl.microsoft.com/download/symbols
Expanded Symbol search path is: srv*c:\temp\symbols*http://msdl.microsoft.com/download/symbols
0:037> !clrstack
The version of SOS does not match the version of CLR you are debugging.  Please load the matching version of SOS for the version of CLR you are debugging.
CLR Version: 4.0.30319.1
SOS Version: 4.0.30319.235
CLRDLL: C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\mscordacwks.dll:4.0.30319.235 f:8 doesn't match desired version 4.0.30319.01 f:8
CLRDLL: Loaded DLL c:\temp\symbols\mscordacwks_x86_x86_4.0.30319.01.dll\4BA1D9EF66f000\mscordacwks_x86_x86_4.0.30319.01.dll
OS Thread Id: 0x690 (37)
Unable to walk the managed stack. The current thread is likely not a managed thread.
You can run !threads to get a list of managed threads in the process

What to do with this error - "The version of SOS does not match the version of CLR you are debugging" ?

The same error ("The version of SOS does not match the version of CLR you are debugging") I'm getting when I open the minidump in VS2010.

I've read this post - http://tech-thinker.com/Forums/tabid/62/forumid/12/postid/471/scope/posts/Default.aspx, and tried installing KB2518870. It doesn't help.

解决方案

WinDbg will not be able to use the debugging adapter mscordacwks.dll unless it is the same version as the one from the original machine. You can get around this error by copying this DLL from the target machine which generated the dump to your Debugging Tools for Windows directory.

We debug .NET 2.0 applications with WinDbg. We would continually get this same error regarding mscordacwks_x86_x86_2.0.50727.3615.dll. I had to copy this file from the server onto my client and put it in the C:\Program Files\Debugging Tools for Windows (x86)\ folder. WinDbg stopped complaining after that.

If all else fails, you can try debugging with WinDbg on the same server from which you retrieved the crash dump.

这篇关于“SOS的版本与您正在调试的CLR的版本不匹配”在WinDbg？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！