I'm not sure what I've done recently to cause this, but now I cannot run some code that was previously working. I have a C# WPF app running in debug and it's attempting to create a new database in the local SQLExpress instance. I get an exception that it can't find/load Microsoft.SQLServer.BatchParserClient.dll. If I go to "C:\Windows\Assembly" it certainly is not there. However, if I use VS command prompt and execute "gacutil-l," it is listed as being in the GAC. I've tried re-installing SQLExpress 2016, 2017 and Management Studio. Nothing has worked.
Apparently there is a dependency on the 2008 SMO which had been removed. Reinstalling the feature pack from SQL 2008 has fixed it.
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.
I am trying to automate SSIS package deployment with only SSDT on my source computer. When I start the ISDeploymentWizard from SSDT for VS 2013 I can successfully deploy packages to a VM that I am running, but when I try to launch from the command line it fails with the following error:
To launch the Integration Services Deployment wizard, one of the Integration Services,
Management Tools - Basic or SQL Server Data Tools has to be installed by the
%SQL_PRODUCT_SHORT_NAME% Standard, Enterprise, Developer, or Evaluation Edition. To install
a component, run SQL Server Setup and select the component name.
I have SQL Server Data Tools for Visual Studio 2013 installed so I do not understand why I am receiving this error. The VM that I am running is a Windows Server 2012 R2 and has SQL 2014 installed on it. When I run the wizard from the command line on the VM it appears to work properly.
Has anyone run into the same issue? Any ideas on how to solve it?
Thanks!
edit 1: To get the package to deploy via SSDT I must launch SSDT using the "runas" command and run as the user on the VM.
Can you try running the command prompt as 'Run as Administrator'?
I solved the issue by updating my SSDT through Visual Studio 2015 extensions and updates panel.
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
I have been using SQL Server 2012 and Visual Studio 2013 on Windows 8.1. All working fine.
Recently I installed SQL Server 2014 Express LocalDB. After installing, I am not able to work with LocalDB. I get odd errors, one I get is LOCALDB_ERROR_AUTO_INSTANCE_CREATE_FAILED
And according to Technet I should find information in the event log, but there is nothing at all in the event log.
When sqllocaldb command works and I can check the LocalDB installed as this:
C:\> sqllocaldb v
Microsoft SQL Server 2014 (12.0.2000.8)
but whenever I try to work with my projects I get connection related errors. The underlying error mentions that automatic instance creation didn't work.
UPDATE: this is resolved by changing connection strings from (LocalDB)\v11.0 to (LocalDB)\v12.0
May be it's:
(localdb)\projectsv12
I have also encountered similar problem. Try it :D
use for SQLExpress 2014 (LocalDB)\MSSQLLocalDB
see also http://www.michael-whelan.net/sql-server-localdb-2014-connection-string/