Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: SQL Server Management Studio - mscorlib.tlb could not be loaded

692 views
Skip to first unread message

Anthony Thomas

unread,
Dec 24, 2005, 1:47:36 PM12/24/05
to
This smacks of two possible issues: first, there was some mention of
UNICODE issues regarding .NET Framework. I'll look for that information.
The second is the possible removal of the Version 2 .NET library. It's the
odd characters between the Framework and mscorlib.tlb that is drawing me to
these conclusions.

In either case, a download and reinstallation of the Version 2 .NET library
should fix this condition.

Sincerely,


Anthony Thomas


--

"Patrick Roos" <patrick.roos_@_timeware.ch> wrote in message
news:ucp3j7GB...@tk2msftngp13.phx.gbl...
> Hi all,
>
> I've a problem with the SQL Server Management Studio. When I start the
> Management Studio I get follow (error)message:
>
> 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 programm.
>
> When I click [OK] I can use the Management Studio without errors. What
> can I do, that I don't get this message?
>
> Thanks for your answers.
>
> Greets
>
> Patrick
>
>
>


----------------------------------------------------------------------------
----

Steve Harnish

unread,
Feb 12, 2006, 3:05:48 PM2/12/06
to
For what it's worth, I get the identical message when starting SQL
Server 2005. I had been using .Net 2.0 exclusively but needed 1.1 to run
another program. Right after installing the 1.1 Framework (but not the
SDK) the message appeared. Haven't figured out how to fix it yet. This
doesn't address your question, but may help identify the cause.

*** Sent via Developersdex http://www.developersdex.com ***

Larry Baldridge

unread,
Apr 12, 2006, 6:33:02 PM4/12/06
to
Apparently the .Net Framework 2.0 repair does the trick. I ran into the same
issue when someone installed VS 2003 on my SQL Server 2005 development box.
Once rebooting, the errors went away.

It seems like the system variable %CLRVERSION% goes bad when .Net 1.1 was
installed (?).

0 new messages