CLR Debugger startup error

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

stevenkobes@hotmail.com - 14 Jan 2006 17:04 GMT

I recently installed the .NET SDK 2.0. When I run the Microsoft CLR
Debugger, it says:

"The file C:\WINDOWS\Microsoft.NET\Framework\\mscorlib.tlb could not be
loaded. An attempt to repair this condition failed because the file
could not be found. Please reinstall this program."

Has anyone seen this before? Looks like mscorlib.tlb exists, but the
CLR Debugger is missing the "v2.0.50727" part of the path. What could
cause this to happen?

--Steve

Reply to this Message

sharnish@att.net - 12 Feb 2006 19:51 GMT

For what it's worth, I get the message when starting SQL Server 2005. I had been using .Net 2.0 exclusively but needed 1.1 to run another program. After installing the 1.1 Framework (but not the SDK) the message appeared. Haven't figured out yet how to fix it. This doesn't address your question, but may help identify the cause.

Reply to this Message

Kunkel - 09 Mar 2006 16:47 GMT

I fixed this problem by recreating the envirionment variable CLRVERSION and gave it the value "v2.0.50727" the error message no longer appears.

Reply to this Message

heavycrag@gmail.com - 04 Apr 2006 14:17 GMT

Thank you for this information. This fixed my problem! By the way, you
can find out the latest CLRVERSION that you have by going to
C:\windows\Microsoft.NET\Framework

Also check out the registry key

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\DbgClr\8.0\TlbAutoRepair\mscorlib.tlb

Thanks!

Reply to this Message

ericb - 19 Nov 2007 17:42 GMT

It appears that this also happens when using .NET 3.0. The same environment variable mentioned above seems to fix it. I had to add it to the list of system variables

From http://www.developmentnow.com/g/25_2006_1_0_0_661959/CLR-Debugger-startup-error.ht

Reply to this Message

CLR Debugger startup error

Free Magazines