SQL Server Management Studio (SSMS) 2014 System.EnterpriseServices.Wrapper.dll Error - sql-server

SSMS 2014 SP1 recently started throwing an error around a mismatch of the System.EnterpriseServices.Wrapper.dll when trying to connect to any database.
I had recently installed LinqPad 5 which required installing.Net 4.6.
Trying to repair SSMS did not fix the issue. Various resources online, suggesting updating the GAC and C:\Windows\winsxs\x86_System.EnterpriseServices_b03f5f7f11d50a3a_2.0.0.0_x-ww_7d5f3790 assemblies from the .Net 2.0 folder and the also did not fix the issue.

This was my solution to get my dev environment back to working as normal. Obviously it isn't ideal, so if anyone has a better solution, please share.
As an interim measure:
Uninstall .Net 4.6 from Add/Remove Programs
Reinstall .Net 4.5.1
from: https://msdn.microsoft.com/en-us/vstudio/hh487283.aspx
Restart SSMS, possibly you may need to restart your computer
If you subsequently recieve an error in Visual Studio:
Open the VS developer command prompt (C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\Shortcuts for Visual Studio 2013)
Run devenv /setup
Alternatively you could run a repair from the VS installer
I believe this is because .Net 4.6 overwrites the files in the C:\Windows\Microsoft.NET\Framework\v4.0.30319 folder, as .Net 4.x all share this folder, SSMS doesn't seem to be able to handle the updgrade. .Net 2.0 uses a different folder, hence why alot of the solutions around presumably didn't help.

Related

Microsoft SQL Server Management Studio error at startup

I get this error when I try to run Microsoft SQL Server Management Studio:
The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.
SxSTrace detail:
1, 2
What I did for solving the problem:
reinstalled SQL Server
reinstalled Microsoft SQL Server Management Studio
updated at recent version of .NET Framework
reinstalled Visual C++ Redistributable
And I still get that same error.
What should I do?
you should install an earlier version. I had the same error and I installed version 18.5 and it worked just fine.
https://learn.microsoft.com/pt-br/sql/ssms/release-notes-ssms?view=sql-server-ver15#185
I had the same error with version 18.9.2. I don't know if it's related to the problem, but I firstly installed SSMS in Program Files and not in Program Files (x86).
First I have tried to repair the installation, with no success.
Then I have uninstalled SSMS, rebooted by PC, re-installed SSMS (this time in the default Program Files (x86) folder) and rebooted my PC again.
After these steps, I was able to start SSMS without errors.
I did the following to solve this error.
Copied all the files and folders from the folder C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\ from a working machine and pasted on the server which was having issue.
Once the copying was completed, I it started appearing in Add or remove programs # control panel.
Post copy SSMS started working normally.
I removed the following Sql related ones from the control panel.
Then i followed these steps
https://stackoverflow.com/a/66085979/16391774
I reinstalled the same version (at present latest version v18.12.1 and i used it version) and my problem was solved.
Uninstalling did not work.
Upgrading (Installing newer version or same version) did not work.
What worked:
delete or rename “C:\Program Files (x86)\Microsoft SQL Server Management Studio 18”
delete registry manually or via .reg file
reg DELETE “HKLM\SOFTWARE\WOW6432Node\Microsoft\Microsoft SQL Server Management Studio” /reg:32)
Afterwards, installing SSMS worked without a flaw and it started.
Found at https://social.msdn.microsoft.com/forums/en-US/7ab37d2b-6bac-4221-b827-d274b00b9a56/ssms-18-how-to-uninstall?forum=sqlkjmanageability&prof=required, similar to https://superuser.com/a/1440276/146668 .

Error deploying Microsoft System CLR Types per SQL Server witch ClickOnce

I'm trying to deploy an application that uses Microsoft ReportViewer 2012 that needs Microsoft® System CLR Types per SQL Server 2012 in order to work but I can't get to install it with ClickOnce.
I checked them in project's prerequisites but it seems they cannot be found
(I checked download from the web).
even if they're present in
C:\Program Files (x86)\Microsoft SDKs\ClickOnce Bootstrapper\Packages
When I deploy my setup installation fail because it can't download SqlClrTypes. If I install them using the same msi manually it works ok.
What can I do to make them install via ClickOnce ?
I'm using Visual Studio 2017, tried 2019 but the same thing happen.
EDIT: Fixed the issue with the prerequisites, my product.xml was referring to the wrong version for some reason. Now the setup is created without issue but when I try the installation it fails when downloading the msi. From the install.log it tries to download it from : http://go.microsoft.com/fwlink/?LinkID=221258

SQL Server Management Studio 2016: The application cannot start

I installed SQL Server Management Studio 2016. When I tried to open it gives this error. I tried uninstall and again install. Also I uninstall all Visual Studio and SQL Server and reinstall all of them but problem still continue.
How can I solve this issue?
In my case, the issue was with broken VS2015 isolated shell installation.
I resolved it by downloading and re-installing this shell from Visual Studio Isolated Shell page https://learn.microsoft.com/en-ca/visualstudio/extensibility/visual-studio-isolated-shell (which should eventually lead you to http://go.microsoft.com/fwlink/?LinkId=615451 - after filling out the survey).
Note:
I had following warnings after the VS1205 shell install. But that
did not matter, since the existing version of these components was
higher.
I had no VS IDEs installed on my computer prior to
installing SSMS 16.5.3 (or 17.1). Both had the same issue. For now I
am using only SSMS 16.5.3, since I do not have a need for 17.1
I completely remove all microsoft application and re install sql server 2016 and the reinstall ssms and ssms worked and finally I install vs17 now its working.
Problem is about to "Microsoft Visual Studio 2015 Shell(Isolated)"
We need to install vs after ssms.
Happened to me on SSMS v17.9.1.
I've repaired Microsoft Visual Studio 2015 Shell (Isolated) and the problem went away.
According to MSDN documentaion:-
An unexpected error has prevented Visual Studio from starting. This error appears when one of the following items occurs:
The integrated development environment (IDE) was not able to load Msxml3.dll.
The IDE was not able to load Mso.dll.
The IDE was not able to load DTE.olb.
The license key for Visual Studio was not created during setup.
Script blocking is turned on and not allowing scripting code to execute.
Setup for the .NET Framework, a component required by Visual Studio, failed to generate a valid native image for mscorlib.dll.
The Klez virus is present on your computer
And the article is introduced specific procedures to correct this error.
Hope helps.

Unable to open SSIS project in Visual Studio 2012 or 2013 (migration fails)

I am trying to open a solution file in Visual Studio 2013 Ultimate that includes an Integration Services project (.dtproj). Unfortunately, the migration failed for reasons that are slightly baffling to me.
The migration report contains the following error:
RecommenderJobs.dtproj: The application which this project type is based on was not found. Please try this link for further information: http://go.microsoft.com/fwlink/?prd=12395&pver=11&sbp=ProjectTypeDeprecated&plcid=0x409&clcid=0x409&ar=MSDN&sar=ProjectCompatibility&o1=159641D6-6404-4A2A-AE62-294DE0FE8301
Unfortunately, the link appears to be dead, so that's no help.
I also received the following error message when I tried to open this in Visual Studio 2012:
I've tried opening this solution in both Visual Studio 2012 Ultimate and Visual Studio 2013 Premium (which is why I tagged both). Both are on Update 5. I already tried updating all of my extensions and updates, even ones that seem like they wouldn't be directly relevant to the problem (like Visual Studio's Office tools).
I found a similar question on Microsoft's forum. The suggestion there was to upgrade my version of SSIS to the latest version. I tried to install SSDT for VS2013 as suggested, but the install failed:
When I checked the logs, it had the following error:
Error 0x80070666: Cannot install a product when a newer version is installed.
I do, in fact, have a different version installed, but it's not actually newer as far as I can tell (in fact, it launches in the Visual Studio 2010 shell), so I'm a little confused by this. The version information is below:
Microsoft SQL Server Integration Services Designer
Version 11.0.5058.0
Microsoft SQL Server Reporting Services Designers
Version 11.0.5058.0
I do also have tools related to SQL Server 2012 installed.
Based on what I've read in other posts, I'd expect to see the SQL Server Data Tools in "Add/Remove Programs," but it's not. Does anyone know why that might be?
I've also seen related questions for other types of projects, such as for a PowerShell project. (Obviously, my question has nothing to do with Powershell, but the OP there was receiving the same exact error message for a different project type). Unfortunately, the suggestions on that post didn't seem all that helpful - for example, the accepted answer there involved completely uninstalling and reinstalling Visual Studio, which would be a major pain to say the least. I'm also not all that confident that that would work for me since this problem occurs in two separate versions of Visual Studio.
Does anyone have any suggestions on what else I could try?
You likely need to install both Integration services and Business Intelligence for Visual Studio (BIDS). You can do it launching SQL Server Setup and adding features to your current SQL Server Instance.
Have a look at this one: https://guruprasadv.wordpress.com/2009/06/17/opening-ssis-package-in-visual-studio/
BIDS is the IDE (integrated into Visual Studio) that allows you to drag and drop the components and create the SSIS packages. From SQL Server 2014 on wards you won't see BIDS anymore packaged in the SQL Server Setup, so you will have to install it independently. If you need it for VS 2013 here you have the link: https://www.microsoft.com/en-us/download/details.aspx?id=42313

Microsoft SQL Server Management Studio Opening Error

I installed SQL Server Management Studio and it worked fine. After that I updated my Visual Studio from 2010 to 2013 Express edition, now it is not working with this error message :
Cannot find one or more components. Please re install the application
I re-installed it but still same issue. Any suggestion?
The SQL Server 2014 Management Studio answer
SSMS 2014 relies upon the Microsoft Visual Studio 2010 Shell (Isolated) Redistributable Package. If this is uninstalled, SSMS will produce the error message 'Cannot find one or more components. Please re install the application'. This can be corrected by:
Reinstalling the VS 2010 Shell from here: https://visualstudio.microsoft.com/vs/older-downloads/isolated-shell/
Try opening SSMS again. If it still gives the error, then:
Run Repair in SQL Server (2014) Setup
The SQL Server 2016 Management Studio answer
SSMS 2016 relies upon the Microsoft Visual Studio 2015 Shell (Isolated) Redistributable Package. If this is uninstalled, SSMS will produce the error message 'Cannot find one or more components. Please re install the application'. This can be corrected by reinstalling VS 2015 or by installing the Microsoft Visual Studio 2015 Shell (Isolated) Redistributable Package.
I just solved the issue :
SSMS depends on VS 2010 and by uninstalling it this error occurred.
There is a folder named 1033_enu in my server installation pakage
Inside that i found a folder VSS i.e Visual studio shell
and inside that VVS setup.
i just run this setup and it solved the problem for me. Thank you
For SSMS 2016 (at least v16.5.3) delete the following folder from the registry and restart the app:
HKEY_CURRENT_USER\Software\Microsoft\SQL Server Management Studio\13.0_Config
The SQL Server 2017 Management Studio answer
SSMS 17.1 also depends on Visual Studio 2015 shell (isolated). I had to repair the Shell to get SSMS to work. In case someone is looking for VS 2015 Shell: LINK
If you cannot find the installer using the above link, the SSMS 17.x installer HERE includes the VS 2015 Shell.
Scott Hanselman has also conveniently included a link to every (>= 2008 R2) Express and SSMS version here: LINK
I had this same issue happen to me when I was stripping my machine of everything Microsoft to refresh my system with 2016-2017 versions of Microsoft products.. First time doing this so I deleted the Visual Studio shell and installed everything 2017 except the 2015 VS shell (not sure if 2017 is out), here was my mistake.
To solve.. first off, make sure you have the Visual Studio Isolated Shell installed. Certain versions of SSMS need a specific version of the shell. My situation called for VS Shell 2015 with my SSMS 2016..
Just installing and repairing the Shell didn't help me completely fix the error. What helped me was deleting a key from my Registry Editor. Run the command regedit from anywhere on your machine 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.. Right away I was able to open SSMS as usual.
In order to free up some space on my disk, I had uninstalled some programs after which I started getting this error.
I followed all the solutions here, but it didn't fix my problem.
For me, after installing the Visual Studio Shell, I had to delete a key from my registry by following the steps here. Then finally my SSMS started working again.
Quoting from the page:
Start regedit.exe
Go to HKEY_CURRENT_USER\Software\Microsoft\SQL Server Management Studio
Delete 13.0_Config
Restart ssms.exe
All the answers here didn't work for me (SQL Server 2014).
What worked was:
1) Uninstall the Visual Studio 2010 Shell using official installer (not via Programs and Features). The file VSIsoShell.exe can be downloaded here:
https://www.microsoft.com/en-us/download/details.aspx?id=1366
2) Once uninstalled, run SQL Server Installation and hit Repair
Try running SSMS as administrator! After repairing & re-installing multiple components, in the end it was just the security level of my account.
I resolved the problem with SQL Management Studio 2016 by running the VS setup, selecting "Modify" and then installing Extensibility Tools Update 3. After that I just ran SQL Management Studio 2016 and it reset VS Isolated Shell
For all versions of SQL Server, this can be fixed safely with no loss of data including any plugins that may be installed and their data.
This is a common bug, and the solution in all versions of SQL Server is to repair the 'Microsoft Visual Studio 20xx Shell (Isolated)' program installation, which takes about 30 minutes to run unattended.
To perform the repair, please complete the following steps:
Close all instances of Visual Studio.
Press the Windows key.
Type 'Programs'.
Click 'Add or Remove Programs' from the list that appears.
Type 'Shell' into the Search box that appears.
Click 'Microsoft Visual Studio 20xx Shell (Isolated)'*
Click Modify (If greyed out then click Uninstall).
In the window that appears, click 'Repair'.
Wait 30mins or so for repair to complete.
Restart machine.
'Microsoft Visual Studio 20xx Shell (Isolated)' will now be repaired and SQL Server Management Studio should open as normal.
* If there are multiple version(s) of 'Microsoft Visual Studio 20xx Shell (Isolated)' installed, then repair the latest one first, working backwards through versions until the correct program is repaired. Be sure to make a note of the version that fixed your version of SQL Server for future reference as it will not change until smss or vs is upgraded.
I have the same issue after using the custom VS2015 uninstallation tool and installing the VS2017. Repair or reinstall of the SSMS 17.3 does not solve the issue.
To resolve it open the Windows Control panel, select the Programs and Features. Select the Microsoft Visual Studio 2015 Shell (Isolated) from the list and click Change. Then click Repair in the VS setup window. On setup completed ignor the warnings about some newer components already installed. Click Close and thats it! SSMS starts perfect! Hope this save someone's time.
I downloaded VSIsoShell.exe but could not install it. When i deep dive in to error logs the reason is newer version of visual studio exists on the system. I uninstalled vs2017 community then installation of VSIsoShell is successful
Download and Install Visual Studio 2015 Isolated Shell.
You can further read the details of this Redistributable Package from Microsoft Visual Studio
2015 Redistributable Package
You can further Download this Package from this link
After Installing this package, Please run SSMS for SQL SERVER 2016. It actually works for me!
Just in case none of the registry edits or software reinstalls mentioned in the other answers work for you, I was having this issue due to anti-virus. In this case it was Crowdstrike, but others can cause it as well.
Try disabling your AV to test, and if that's the culprit, put an exception in for SSMS 2014/2016.
None of above solutions worked for me , Link in the accepted answer is not working.
So I tried repairing MSSQL 2014 from Setup , This will install Visual Studio Shell which it depends on.
SQL Server Installation Center -> Maintenance -> Repair -> Select the Instance
Next , You will be able to run ssms without an issue.
Hope that works,
I finally got this to work - open up
"C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\RSConfigTool.exe"
then used the repair tools in there, rather than from the control panel install programs (repair).
This seemed to run through reinstalling of files and afterwards everything worked great! I was tearing my hair out!
I uninstalled already existing microsoft visual studio 2010 Shell(isolated) -ENU
Then did repair
To do repair please follow below path : SQL Server Installation Center -> Maintenance -> Repair
Note: None of the above worked for me.This is only worked

Resources