I need to get the Microsoft.SQLServer.DTS.Design.DLL in the C:\Program Files (x86)\Microsoft SQL Server\110\SDK\Assemblies folder installed somehow.
I installed almost everything possible, like Data Tools for Visual Studio 2012, SQL Server BI, Client SDK etc. but it is still missing.
What do I need to install?
Have you looked at this link ? http://arcanecode.com/2015/01/07/sql-server-ssis-ssdt-error-method-not-found-microsoft-sqlserver-dts-design-visualstudio2012utils-isvisualstudio2012proinstalled/
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 am more an end-user of SQL Server 2012. When I right click on a table name and select "Edit top 200 rows" menu item. I get this message:
Exception has been thrown by the target of an invocation. (mscorlib)
Additional information:
Attempted to read or write protected memory. This is often an indication that
other memory is corrupt. (Microsoft.VisualStudio.OLE.Interop)
If I try to do the right click again, SQL server will stop working and close. I still can use SQL commands to insert or update database. I have been searching around for a solution, and found this link: http://social.msdn.microsoft.com/Forums/vstudio/en-US/42b79da5-6f1e-4122-a2cb-00def87a1ae2/microsoftvisualstudiooleinterop-attempted-to-read-or-write-protected-memory-this-is-often-an?forum=visualstudiogeneral
But it still does not help me to understand clearly the cause or find the solution to the issue. Any help to resolve this problem is highly appreciated. Thanks.
Are you attempting to edit a SQL 2014 database with the 2012 version (or earlier) of SQL Management Studio?
You can determine the SQL version of your database by running this query against your master database:
SELECT ##VERSION
I had the same problem and I was able to direct edit tables ('Edit Top 200') by installing and using SQL Server Management Studio 2014. Even if both your DB and Management Studio are version 2012, it might not hurt to upgrade Management Studio.
I have also faced the same issue. And I noticed one thing that if you are using SQL database newer then the SQL management studio version, You will received that message. To overcome this issue just install SQL management studio equal or greater then version of database. i.e if you have SQL 2012 then you need to install SQL management studio 2012 or 2014.
If anyone experiences the same issue in MS SQL SERVER from a different scenario ( eg - creating new database diagram )
And if this happened after fully uninstalling MS VISUAL STUDIO
Follow the Steps Below;
Delete Folders MSDesigners8 and Visual Database Tools from the paths below.
C:\Program Files (x86)\Common Files\Microsoft Shared\MSDesigners8
C:\Program Files (x86)\Common Files\Microsoft Shared\Visual Database
Tools
Reinstall Visual Studio and Run Repair Tools from the Visual Studio Installer.
This Will Regenerate the folders we removed above and will repair partial fragments.
Now your SQL SERVER Database Diagrams should be working fine. Cheers :)
I have found a solution which does not require restart. Go to:
C:\Users\<User Name>\AppData\Local\Temp
and delete all the files. Before deleting, close the SSMS window.
I am using the SSIS Script Component editor interface and I am unable to get the references to work.
Microsoft.SqlServer.DTSPipelineWrap
Microsoft.SqlServer.DTSRuntimeWrap
Microsoft.SqlServer.PipelineHost
The DLLs exist and I can navigate to them here-- C:\Program Files (x86)\Microsoft SQL Server\110\SDK\Assemblies
I've tried deleting and re-adding the references (through the .NET tab and by browsing directly), but it hasn't helped. The error states "The referenced component... cannot be found."
What do I need to do?
I've had this problem today whilst maintaining legacy work in BIDS 2008.
The DLLs were in the GAC on my install, so my case might have been slightly different.
BIDS 2008 refused to acknowledge them, I think because I had Sql Server 2012 installed on my machine.
As it was small job I renamed the dlls for sql server 2012 and then renamed them once I'd finished the work
So I temporarily renamed the files in
C:\Program Files (x86)\Microsoft SQL Server\110\SDK\Assemblies
Not a long term fix!
You're working in BIDS 2008 but are trying to reference the DLLs for SQL Server 2012. See Using SSIS BIDS with Visual Studio 2012 for ways to work with SSIS for SQL Server 2012, if that's what you're trying to do.
In BIDS 2008, you want the SQL Server 2008R2 DLLs, located by default in C:\Program Files (x86)\Microsoft SQL Server\100\SDK\Assemblies. (Note that the VSTA project should have those references set automatically when you edit the script for the first time.)
I had installed SQL Server 2008 R2, the installation was succesful. But I can't open the Management Studio because this error is shown:
Package 'Microsoft SQL Management Studio Package' failed to load.
Any idea? Thanks.
You need to rename or delete the Registry Key for,
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server
Read in detail on :
http://blog.dotsmart.net/2012/01/04/solution-for-package-microsoft-sql-management-studio-package-failed-to-load/
Before re-installing software etc, you might just perform the following simple check.
Right click on the short-cut you use to launch SQL Server Management Studio, then ensure that Start in is set to the same PATH as Target
e.g. if Target is set to
C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe
then Start in should be set to the same path (minus the filename) i.e.
C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\
(On a PC which I was given at work, 'Start in' was blank and this gave the same error as reported in the above posts.)
From a first look at the log, your installation appears to be corrupt as Microsoft.VisualStudio.Shell.Interop.dll is failing to load.
Can you please check to see if Microsoft.VisualStudio.Shell.Interop.dll is in the GAC?
If it is, please run the fusion log (you should find this under C:\Program Files\Microsoft SDKs\Windows\<sdk version>\bin). Go to settings and turn on "log bind errors to disk" and then try running VS. The log file should tell you where the assembly binding failure.
Had the same issues, started to happen to me out of the blue.
Tried probably everything I could find on the network without success.
I am running Windows 7, and what finally helped was installing Service Pack 1
(I hadn't had it before).
I used the 'Repair' feature of the 'SQL Server Installation Center' to repair <Shared Tools>, rather than an instance. Worked a treat.
I had this problem on a Windows 2008 r2 server. The solution was to right-click on the icon and select 'Run as Administrator'.
I used the 'Repair' feature of the 'SQL Server Installation Center' to repair the instance. It worked like a charm for me.
This error due to managment studio did not detect dot net framework hence uninstall dot net 4 and reinstall it.
I tried that , it's working.
I tried the following, I had same problem for sql server 2008 r2 release
Renamed HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server
Reinstall SQL server
Repairer SQL server
Reinstall management studio for 2008 r2
All above did not help but new fresh and latest management studio installation helped and works fine now.
It's worked for me after delete Local user profile. (Logoff and login as Admin delete user profile and re-login).