Lỗi package microsoft management studio package failed to load năm 2024

I had an odd issue where SQL Server Management Studio (SSMS) 2008 R2 would start up, display the following error message, then exit:

Nội dung chính Show

SQL Server Management Studio (SSMS) setup failed or requires restarting the machine
In this article
Suggested resolution

Package ‘Microsoft SQL Management Studio Package’ failed to load

Using SysInternals Process Monitor tool to monitor SSMS.exe it seemed that it was looking for the following registry key but not finding it:

HKEY_CURRENT_USERSoftwareMicrosoftMicrosoft SQL Server100Tools

By renaming a parent key (rather than delete it – just in case it didn’t fix the issue) solved the issue for me. The key I renamed was:

HKEY_CURRENT_USERSoftwareMicrosoftMicrosoft SQL Server

Running SSMS again recreated the 100Tools sub keys and all was well again. I hope it works for you too.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

SQL Server Management Studio (SSMS) setup failed or requires restarting the machine

Article
05/21/2024

Suggested resolution

Following these steps to uninstall the "Microsoft ODBC Driver 17 for SQL Server" before beginning the SSMS installation commonly allows the setup to succeed if it fails with one of the aforementioned or similar error messages.

There is no documented errors of this kind in Technet but there were some notes on this problem in obscure internet web sites.

This was a new install of just the Management Studio...client utilities. No betas or anything like that. SQL Server 2000 client utilities are also on this machine. It worked for awhile before this error began. I am unable to do any work in SQL Server 2005 until this problem is solved.

michaela SSCertifiable Points: 5649 Have to reinstall .Net 2.0; if stil doesn't work then have to repair sql client tools installation: start /wait (your sql path)\SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS from cmd prompt; Good luck.
Sugesh Kumar One Orange Chip Points: 27311 Yes as told by michael you have to reinstall .Net framework 2.0. Also go ahead with a clean installation of client tools from the machine you try to connect.
Martin Vrieze SSCrazy Points: 2760 I reinstalled .NET 2.0 last night. Did not fix the problem. Moving to SQL Client Tools...By "clean install" you mean both uninstall and reinstall client tools, correct? If so, does it matter if I miss removing some of the registry stuff that uninstall does not automatically remove?
vikmalani SSC Enthusiast Points: 168 Following steps fixed my problem: 1. Reinstalled .Net 2.0; 2. Repaired "sql client tools installation" from cmd prompt: ...SQL2005\Tools\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS -vm
Pat Henz SSC-Addicted Points: 464 Could this also fix an install issue with SQL Server 2005 Standard Edition? The same error is occurring and the SSIS services will not start.
vikmalani SSC Enthusiast Points: 168 SSC Rookie, Steps i listed are for client tool related issues (Standard Edition included), not sure they will help with SSIS service issue. -vm
vw_driver78 Valued Member Points: 73 October 13, 2008 at 10:22 am I suddenly encountered this problem today on my Windows Vista laptop. SQL Server 2005 SP2 had been installed for 5 months and was working fine. In my case the solution was insufficient disk space, which Vista had warned me about on startup today. I freed up enough disk space so that I had at least 10% of disk space free, and the problem went away. I did not reinstall .NET 2.0, or SQL Server, or run any application repairs.
Tejas M. SSC Enthusiast Points: 114
cbozdag Valued Member Points: 71
Karl Grissom SSC Enthusiast Points: 134 Hello, I am getting the same message and I have done all steps above and I still get the failed to load message. But I can lauch it fine if opening a sql file. I did find that by switching XP apperance to Wndows Classic look, the regular menu short cut works. I am running XP SP2 with 4GB ram on Latitdue D630 laptop
Tejas M. SSC Enthusiast Points: 114 Install xp sp3 & try again. !
Karl Grissom SSC Enthusiast Points: 134 Thanks for the info. SPs pushes are controlled by my company. In fact I thought I was on SP2 but looing this morning I am on SP3. So that not the issue.
Bo Gulledge SSC Enthusiast Points: 123 I had this problem today. I went into 'Add/Remove Programs' and did a 'Repair' on .NET 3.5 SP1 and it seems to have resolved the problem.
rongolini SSC Enthusiast Points: 116 Got my SQL Management Studio 2005 to work again by doing a Repair on .NET 3.5 SP1 through Add or Remove Programs. When I started Management Studio afterwards, it configured "for first time use" and then opened successfully. I had to dock the Object Explorer window to its usual location at the left.