Microsoft SQL Server Management Studio closes in about five seconds after startup. The startup splash screen is displayed, but after that, nothing. No messages are being displayed (even in a console) and no logs occur in a Windows Event Viewer. I have tried to install different SSMS versions , i.e. 16.X, 17.Y, but it have not helped. I have also tried to repair VS 2017 and SSMS.
This problem occurred for the first time, when I uninstalled Visual Studio 2015 and its related components, like SSMS, and installed VS 2017 and newer version of SSMS (16.X).
What can I do to make SSMS not closing immediately after startup?
Step 1: Just delete this file:
C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\CommonExtensions\Platform\Microsoft.VisualStudio.MinShell.Interop.pkgdef
Alternatively, rename the file so it does not have the .pkgdef extension.
Step 2: Optionally, you can remove the following Windows Registry Key (created at SSMS 18 startup using the .pkgdef file mentioned above):
HKEY_CURRENT_USER\SOFTWARE\Microsoft\SQL Server Management Studio\18.0_IsoShell_Config\RuntimeConfiguration\dependentAssembly\bindingRedirection\{8BC7AF31-B6DA-4B97-8B36-F0500DECB147}
I had this same problem running SQL Server 2017 on Windows Server 2012 R2.
• After installing SSMS 18.0 General Availability release (GA), when started, it always closed immediately.
• So I installed Visual Studio 2019 Community Edition with the Data storage and Processing workload and somehow SSMS 18.0 (GA) ran fine without closing, but just once. The next times I tried to start SSMS 18.0 (GA) again, it always closed immediately.
• Having lost my trust on this GA release, I decided to uninstall it and try with a previous release.
• Using the Chocolatey package manager for Windows https://chocolatey.org/packages/sql-server-management-studio I installed SSMS v17.8.1 and everything is working fine now.
Can't believe, that the only solution was to install VS 2015 again. So I use VS 2017 in everyday work, but I must have VS 2015 installed as well, just to make SSMS work...
I took a look at this. Problem seems to be with SMSS installing Microsoft Visual C++ 2017 Redistributable. When that happens, Microsoft Visual C++ 2015 gets uninstalled. However, if you look at the System Requirements at this page:
Microsoft Visual Studio Tools for Applications 2017
you'll see that Microsoft Visual Studio Tools for Applications 2017, which is also installed by SMSS v18.0, requires Microsoft Visual C++ 2015 Redistributable.
So, it seems the crash is caused by Microsoft Visual Studio Tools for Applications 2017 when it tries to find Microsoft Visual C++ 2015 Redistributable and can't since Visual C++ 2017 Redistributable removed it.
Don't bother trying to install Microsoft Visual C++ 2015 Redistributable if 2017 is already there. Installer for 2015 won't do the install if it sees 2017 is already there. Uninstalling 2017 so 2015 will install works, but then, when you reinstall 2017, 2015 is removed.
I guess stay on SMSS v17.9.1 for now.
According to this article SMSS Immediately closes (a load of work....), it should work again:
1) Uninstalled Visual Studio 2015 with VisualStudioUninstaller (thanks Andrea)
2) Uninstalled Visual Studio 2017 (above uninstaller not help a lot for 2017)
3) Uninstalled Visual Studio 2015 Shell
4) Uninstalled all related SQL apps including (SSMSs).
4) Reinstalled Visual Studio 2017 and SSMS 16
SMS Release 18.0 has a repair option if you run the download. Try the repair option. It's new.
In my case, it was SqlServer Management Studio 18. and the solution was to
Copy the Microsoft.VisualStudio.Shell.Interop.8.0 file from
C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\PrivateAssemblies\Interop
and override the file in
C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\PublicAssemblies
Related
"Setup Failed" Recursion too deep; stack overflowed 0x800703E9.
I have windows 10 and newest visual studio version. I have tried rebooting to make sure I have as many resources as possible. I have 4g ram.
If the SSDT installer gives you multiple instances of Visual Studio to choose from, try the "new" option.
I ran into this problem trying to install SSDT 15.8.1 on Windows Server 2012 R2 with the latest version of Visual Studio 2017 (v15.8.6) already installed. The SSDT installer gave me 2 options in a dropdown box.
Install tools to this Visual Studio 2017 instance:
Visual Studio 2017
Install new SQL Server Data Tools for Visual Studio 2017
When I chose the first option: Visual Studio 2017 (presumably the existing instance), I ran into the cryptic "recursion too deep" error. I installed the SSRS extension for VS (as suggested by others on Stack Overflow) and tried running the SSDT installer again for the existing Visual Studio 2017 instance. I got the same "recursion" error.
I tried one more time, but this time chose the 'Install new SQL Server Data Tools for Visual Studio 2017' option. This time the install process completed!
Apparently there is an installer inconsistency between the latest versions of SSDT and Visual Studio. The suggested fix is to start with a previous installation of Visual Studio 2017, install the latest SSDT on top of that, and then upgrade Visual Studio. This is a very time consuming fix. It appears this is only necessary for the SSIS components - the SSAS and SSRS pieces are available as Extensions within VS, and I believe they still install successfully from there.
https://developercommunity.visualstudio.com/content/problem/258117/ssdt-failed-to-install-vs-2017-pro-1572.html
Please re-run the VS community 2017 installer or go to Control Panel-Programs and Features, uninstall the previous SSDT version for VS 2017, then re-install it, you can have a look at this similar issue.
If this issue persists, please use http://aka.ms/vscollect to gather the installation logs and find vslogs.zip under the %temp% folder, then upload the file to Onedrive and share the link here.
You should uninstall the current version of SSDT before install a new version.
If your computer have some pages blocked, you could download the specific version offline installer (Download the header, then use SSDT-Setup.exe /layout [Folder]) for the former version and new version of SSDT.
How I got past it:
Uninstall the Visual Studio extensions for Reporting Services (and Analysis Services) projects in case if you going to select them during SSDT set up. Note: remember to run VS as administrator to do the uninstall.
Reboot VS2017 (just out of general principle.)
Got a big problem with the Visual Studio 2017 Installer Projects Extension for Visual Studio 2017 Professional. I added a Visual Studio Installer Setup project to a solution and set it up the way it's basically supposed to be done (Primary Output in the Application Folder and an icon in the Desktop Folder is all that was needed). Then I right-clicked on the Setup project, clicked "Build" and then I get this:
Please wait while Windows configures Microsoft Visual Studio Professional 2013.
And then it stalls indefinitely. I have to close Visual Studio in Task Manager to stop everything. What's more, I'm Visual Studio Professional 2017, not 2013. I used to have Visual Studio 2013 Ultimate, but I uninstalled it. What could possibly be causing the confusion?
It appears that you have also got Visual Studio 2013 installed, and that there is as conflict between 2013 and 2017 because that message is a Windows Installer repair of VS 2013. Something is happening during your build that requires the VS 2013 installation to be repaired. The Windows Event Log (Application) will have an MsiInstaller log entry saying which component appears to be broken. If you post that information there may be a clue to the problem. If you (for example) have manually removed anything that may belong to the VS 2013 installed product then that would cause the same kind of problem.
You have this similar problem:
Rebuilding Visual Studio Installer project, launches Visual Studio 2013 seetup
Visual Studio 2015 msi build initiates another installation
When you say it stalls indefinitely, I would expect it to ask for the Visual Studio 2013 install image so that it can repair it. If you go to Programs&Features and manually repair VS 2013 it might fix the problem.
I also had Visual Studio 2013 installed as mentioned by #PhilDW.
Navigating to Event Viewer → Windows Logs → Application I found loads of warnings:
Detection of product '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}', feature 'Visual_Studio_Professional_x86_enu', component '{E3FF99AA-78B9-4A06-8A74-869E9F65E1FE}' failed. The resource 'C:\WINDOWS\Microsoft.NET\Framework\URTInstallPath_GAC\' does not exist.
The key here being that the folder C:\WINDOWS\Microsoft.NET\Framework\URTInstallPath_GAC\ did not exist thanks to an answer in the first link provided by #PhilDW.
Created the missing final folder URTInstallPath_GAC in the path mentioned and the installers now build really fast whereas before they used to take forever (sometimes literally!).
I have been trying to install Visual Studio 2010 Professional on my Windows 8.1 laptop and I am having problems. It seems to install and when I look at the applications list I see everything has installed except the Visual Studio 2010 (devenv.exe) application itself. Has anyone had this problem and found a solution for it? I have checked that .NET 2.0, 3.x and 4.x are all installed on the machine and active. The installer shows that it is installing the application but when it's completed the application is no where to be found.
I had the same thing happen to me, because I had SQL Server Data Tools installed, causing the shortcut to be named "sql server Data Tools". Try looking up the executable in C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe and manually creating the shortcut on the start screen:
Be sure to install the updates as well:
Visual Studio 2010 SP1
Visual Studio 2010 GDR for Team Foundation Server
Visual Studio 2010 Compatibility Update for Windows 8 and Visual Studio 2012
For an up to date list of patches and service packs see:
https://jessehouwing.net/vsts-tfs-connect-any-visual-studio-version/
I am using SSIS 2014 and Visual Studio 2013. When I click on Edit Script button of script task no error nothing happens but script editor doesn't open. Nothing happens I have installed on my machine:
Microsoft Visual Studio Tools for Applications 2012
Microsoft Visual Studio Tools for Applications x64 Runtime 3.0
I had the same problem with the following setup:
Visual Studio 2017 Community Edition (15.6.6)
SSDT 2017 (15.5.2)
SQL Server 2017 Developer Edition
I solved repairing the installation of Visual Studio Tools for Application 2017 from the control panel:
I've just had exactly the same problem. I've got both SSDT and SSDT BI installed for VS2012 and VS2013 but still couldn't get the Edit Script to open. I repaired my install of VSTA 2012 and also newly installed VSTA 2013 but still no luck.
Turns out I just had to run VS 2013 as administrator and it worked! Might not be the solution for all but worth a try if you've got all the correct applications installed.
I ran into this same exact issue. Try installing Sql Server Data Tools 2012 here as well as Sql Server Data Tools 2013 here. I am not sure why you would need both but for some reason the script task when only having SSDT 2013 installed still seemed to want to reference 2012 (see screen shot below).
Hopefully this helps.
I have the same setup VS 2013 Professional, with SQL 2014 Data Tools. My VstaProjects window would open, but the ScriptMain.vb window, with the framework, would not open.
Repair was not an option, so the tech removed and reinstalled SSDT 2014. It works now.
I have a number of macros written for Visual Studio 2005, but they have since stopped working once I installed Visual Studio 2008 on my computer. No error is returned by the macro when I try and run it, and the environment merely shows the hourglass for a second and then returns to the normal cursor. Currently uninstalling one or the other is not possible, and I am wondering if there is anyway to get the macros to work again?
You may need to install (reinstall) VS 2005 SP1, since a security update from Microsoft (KB928365) on July 10 may have caused the issue.