Package 'Microsoft SQL Management Studio Package' failed to load - by bob_walker99

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 218645 Comments
Status Closed Workarounds
Type Bug Repros 4
Opened 10/5/2006 2:20:52 AM
Access Restriction Public


When starting SQL Server 2005 Management Studio, I regularly (at least once a week) get a warning message box (yellow triangle) containing the above error message. If I click on it, I get another message box, this time an error(red circle, white cross) with the same message. If I click that, the program exits. It is not possible to recover from this error without rebooting - subsequent restarts of the software result in the same behaviour. No hint is given as to where to look for error messages or possible resolutions, nor is the option given to report the problem to yourselves. 

On examining the System Event Log, I see a series of DCOM errors relating to SQL Servers I have set up that I normally access over a VPN link. These errors occur only once, corresponding to the first time I tried to start SQL Management Studio this morning. The errors are  all as follows:
"DCOM was unable to communicate with the computer XXXXXX using any of the configured protocols". 
(Where XXXXXX is the name of a server normally accessed over VPN).

Simply starting the management studio should not try to connect to these machines - the connection should be initiated at my request unless I instruct it otherwise; either way it should not cause the software to exit.
Sign in to post a comment.
Posted by Sudarshan Narasimhan [MSFT] on 8/3/2012 at 1:54 PM
Also check to see if the following locations are present and it contains the files mentioned below.

VSDebugUI.dll --> C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\Packages\Debugger\1033\

vsdebug.dll --> C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\Packages\Debugger\

If for some reason this directory is missing or there is lack of permissions for the account running SSMS, you will get this error. You can use Process Monitor to find this out when opening up SSMS. HTH.
Posted by wjb21 on 1/19/2012 at 4:45 AM
I have just started seeing this problem with SSMS 2008 R2
Posted by Ravi Gottumukkala _ on 11/10/2011 at 2:29 PM
after 2 days of google searches and attempts to fix this, finally found a solution.

repairing windows 7 didn't work.

repairing sql installation didn't work.

uninstalling and re-installing .net framework 3.5 didn't work. (by the way this is provided natively in windows 7).

navigate to the ssms.exe executable located at C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\

right click on the file, goto properties, goto 'compatibility' tab and change compatibility mode to 'windows 7'
Posted by Adam Greene1 on 4/19/2011 at 11:43 AM
Getting this problem now with a fresh install of Vista x65 SP2, VS2010 SP1, and SQL 2008 R2. Tried reinstalling, tried repairing, etc. Nothing works.
Posted by allanmwanza on 12/21/2009 at 1:58 AM
Agreed, repairing or installing .NET 3.5 SP1 solves the problem.
Posted by trackerbo on 8/27/2009 at 12:15 PM
I had this issue today. I went into Add/Remove Programs and performed a "Repair" on .NET 3.5 SP1 and it seems to have resolved the problem.
Posted by Microsoft on 1/21/2008 at 11:37 AM
Hello - I'm not going to be able to get this in for SQL Srever 2008. This does not mean that the information is not relevant or valid; but we are not able at this time to work on this item. Note that this issue may also be fixed as a result of some framework issues we are dealing with.
Buck Woody, SQL Server Program Manager
Posted by Microsoft on 10/5/2006 at 10:35 AM
Hi bob_walker99,

I've put this issue in the queue to be looked at for the next general release of SQL Server. I'll request that test look at this, however it would be great if you could provide us a solid repro.

We appreciate that you took the time to log this with us and make the community aware of this issue.

Thank You,

Terrence Nevins
SQL Server Program Manager