Error opening Microsoft Studio SQL Server

Question

I installed SQL Server Management Studio and worked fine. After that I updated my Visual Studio from 2010 to 2013 Express Edition, now it does not work with this error message:

Cannot find one or more components. Please install the application

I installed it again, but still the same problem. Any suggestion?

Answer 1

I just solved the problem: SSMS depends on VS 2010 and removing this error.

• In the server installation folder there is a folder named 1033_enu
• Inside, I found the VSS folder ie Visual Studio shell
• and inside this VVS installation. I just run this setup and it solved the problem for me. Thank.

Answer 2

Answer SQL Server 2014 Management Studio

SSMS 2014 relies on the Microsoft Visual Studio 2010 Redistributable Shell Package (isolated). If this is removed, SSMS will display the error message "One or more components cannot be found. Please reinstall the application." This can be fixed with:

1. Reinstall the VS 2010 shell from here: https://visualstudio.microsoft.com/vs/older-downloads/isolated-shell/
2. Try opening SSMS again. If this still gives an error, then:
3. Perform recovery in a SQL Server installation (2014)

Answer SQL Server 2016 Management Studio

SSMS 2016 relies on the Microsoft Visual Studio 2015 redistributable shell package (isolated). If this is removed, SSMS will display the error message "One or more components cannot be found. Please reinstall the application." This can be fixed by reinstalling VS 2015 or by installing the Microsoft Visual Studio 2015 shell redistributable package (isolated).

Answer 3

For SSMS 2016 (at least v16.5.3), delete the following folder from the registry and restart the application:

HKEY_CURRENT_USER\Software\Microsoft\SQL Server Management Studio\13.0_Config 

Answer 4

Answer SQL Server 2017 Management Studio

SSMS 17.1 also depends on the Visual Studio 2015 shell (stand-alone). I had to repair Shell to get SSMS working. If someone is looking for VS 2015 Shell: LINK

If you cannot find the installer from the above link, the SSMS 17.x installer HERE includes the VS 2015 shell.

Scott Hanselman also added a link here for each (> = 2008 R2) Express and SSMS version here: LINK

Answer 5

To free up space on my disk, I uninstalled some programs, after which I started getting this error.

I followed all the solutions here, but that did not solve my problem.

For me, after installing Visual Studio Shell, I had to remove the key from my registry by following the steps described here . Then, finally, my SSMS started working again.

Quoting from the page:

1. Run regedit.exe
2. Go to HKEY_CURRENT_USER \ Software \ Microsoft \ SQL Server Management Studio.
3. Delete 13.0_Config
4. Restart ssms.exe

Answer 6

I had the same problem with me when I rented my entire Microsoft machine to update my system with versions of Microsoft products in 2016-2017. Having done this for the first time, I uninstalled the Visual Studio shell and installed all of 2017, except for the 2015 VS shell (not sure if 2017 does not work), here is my mistake.

To solve .. first turn off, make sure you have Visual Studio Isolated Shell installed. Some SSMS versions SSMS a specific shell version. My situation required VS Shell 2015 with my SSMS 2016 ..

Just installing and repairing Shell did not help me completely fix the error. Which helped me remove the key from my Registry Editor . Run the regedit from anywhere on your computer, and then find:

 'HKEY_CURRENT_USER/Software/Microsoft/SQL Server Management Studio/*shellversion*_Config' 

Right click and delete this folder / key. For SSMS 2016 I deleted 13.0_Config.. Immediately I was able to open SSMS as usual.

Answer 7

All the answers here did not help me (SQL Server 2014).

What happened:

1) Remove the shell of Visual Studio 2010 using the official installer ( not through programs and functions ). The VSIsoShell.exe file can be downloaded here: https://www.microsoft.com/en-us/download/details.aspx?id=1366

2) After uninstallation, start the installation of SQL Server and click Restore

Answer 8

Try running SSMS as an administrator! After recovering and reinstalling several components in the end, it was only the level of security of my account.

Answer 9

I solved the problem with SQL Management Studio 2016 by configuring VS, selecting Modify, and then installing the extension tools update. 3. After that, I just started SQL Management Studio 2016 and reset the VS isolated shell

Answer 10

For all versions of SQL Server, this can be fixed safely without data loss, including any plugins that can be installed and their data.

This is a common mistake, and the solution in all versions of SQL Server is to fix the installation of the program "Microsoft Visual Studio 20xx Shell (Isolated)", which takes about 30 minutes to run unattended.

To carry out repairs, follow these steps:

1. Close all instances of Visual Studio.
2. Press the Windows key.
3. Enter "Programs."
4. Click "Add or Remove Programs" in the list that appears.
5. Type "Shell" in the search box that appears.
6. Click "Microsoft Visual Studio 20xx Shell (Isolated)" *
7. Click "Edit" (if grayed out, click "Delete").
8. In the window that appears, click "Restore."
9. Wait 30 minutes or so for the repair to complete.
10. Reboot the machine.

The Microsoft Visual Studio 20xx Shell (Isolated) will now be fixed and SQL Server Management Studio should open as usual.

* If several versions of "Microsoft Visual Studio 20xx Shell (Isolated)" are installed, first restore the latest version, working in reverse order until the correct program is repaired. Be sure to write down the version that fixed your version of SQL Server for future reference, as it will not change until smss or vs. is updated.

Answer 11

I have the same problem after using the custom VS2015 uninstall tool and installing VS2017. Repairing or reinstalling SSMS 17.3 does not solve the problem.

To solve this problem, open the Windows Control Panel, select "Programs and Features." Select Microsoft Visual Studio 2015 Shell (Isolated) from the list and click the "Edit" button. Then click Restore in the VS settings window. After installation is complete, ignore warnings about some already installed new components. Click Close and there it is! SSMS starts great! Hope this saves someone time.

Answer 12

Installing a Visual Studio 2010 shell helped me ...

https://www.microsoft.com/en-us/download/details.aspx?id=1366

Answer 13

I downloaded VSIsoShell.exe but could not install it. When I dive deep into error logs, the reason is that there is a newer version of visual studio in the system. I uninstalled the vs2017 community, after which the installation of VSIsoShell failed

Answer 14

Download and install the isolated shell of Visual Studio 2015.

You can also read the details of this Redistributable Package from Microsoft Visual Studio Redistributable Package 2015

You can download this package from this link.

After installing this package, start SSMS for SQL SERVER 2016. It really works for me!

Answer 15

Just in case, none of the registry changes or reinstallations of the software mentioned in other answers work for you, I had this problem because of the antivirus. In this case, it was Crowdstrike, but others can also cause it.

Try disabling your AV test, and if this culprit includes an exception for SSMS 2014/2016.

Answer 16

None of the above solutions worked for me, the link in the accepted answer does not work.

Therefore, I tried to restore MSSQL 2014 from the installer, this will install the Visual Studio shell on which it depends.

 SQL Server Installation Center -> Maintenance -> Repair -> Select the Instance 

Then you can start ssms without problems.

Hope this works,

Answer 17

I finally made it work - open "C: \ Program Files (x86) \ Microsoft SQL Server \ 120 \ Tools \ Binn \ RSConfigTool.exe", then use the recovery tools, and not from the installer installation panel (repair).
It seemed that this was happening through the reinstallation of the files, and then everything worked perfectly! I tore my hair!

Answer 18

I uninstalled the existing Microsoft Visual Studio 2010 (isolated) -ENU shell. Then I made the repair. To perform the recovery, follow the path below: SQL Server Installation Center → Maintenance → Recovery

Note: None of the above worked for me. It only worked