I have a Visual Basic .NET application located on a server in the network. When I run the application from a PC in the network it works fine. The login/password is checked and all information is loaded from the database. The only thing that is not working is opening a Crystal Report. I get the following popup:
When I install SSMS version 18.12.1 on the PC the problem is solved. I don't even have to open SSMS once. The question is: what part of SSMS makes it work? I tried to install only Microsoft® ODBC Driver 13.1 for SQL Server® but that didn't solve it.
Installed Microsoft® SQL Server® 2012 Native Client was the solution for my problem
I had visual studio 2010 on my VM and I Uninstalled it by visual studio 2010 uninstall utility which I downloaded from here :
https://aka.ms/vs2010uninstall
it also uninstalled visual studio 2010 shell...
Then I Installed Visual Studio 2015 Update 3. After that, I can't open sql server management studio 2012. It gives me this error :
Cannot find one or more component please reinstall the application.
also when I try to repair it, it gives me this error:
TITLE: SQL Server Setup failure.
SQL Server Setup has encountered the following error:
The required MSI package 'c:\6b55b72929daeb5953cfca72\1033_ENU_LP\redist\VisualStudioShell\VSIntSetup\vs_setup.msi' doesn't exist.
Error code 0x858C0038.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&EvtType=0xFDC38F1F%25400xE62C46B1%25401420%254056
what should I do?!
SQL server management is sharing a lot of components with visual studio, in order to use it on the same machine the painless and best option is to keep them aligned as much as possible.
Except in case you are going to connect to a newer (Azure) version of SQL-SERVER you can easily solve the situation by uninstalling the current version of SQL Server Management and installing MS-SQL Server Management 2016.
Likely also installing even a newer version will not gave issues, but using an older one will be a source of troubles and also a no-sense since the Management Studio is backward compatible with older SQL Server versions.
Start regedit.exe
Go to HKEY_CURRENT_USER\Software\Microsoft\SQL Server Management Studio
Delete 11.0_Config
Restart ssms.exe
I have Visual Studio 2013 Community and I have installed SQL Server 2014 LocalDB (not complete SQL Server). During installation of Visual Studio I had already checked data tools. When I want to add a data connection using data source:(localdb)\MSSQLlocaldb it displays an error
Could not load file or assembly Microsoft.SqlServer.Management.Sdk.Sfc version v11.0.0.0 ..... bala bala".
I checked my assembly folder it already has Microsoft.SqlServer.Management.Sdk.Sfc version v11.0.0.0. So what's the problem here? And I also installed SharedManagementObject.msi for SQL Server 2014 - any help?
I am using Visual Studio 2013 with SQL Server 2012.
When I try to add a SQL Server project (*.sqlproj) to my solution, I receive the following error:
Could not load file or assembly
'Microsoft.Data.Tools.Schema.Utilities.Sql.12, Version=12.0.0.0,
Culture=neutral, PublicKeyToken=etc...' or or one of its
dependencies. The system cannot find the file specified.
According to Microsoft, SQL Server Data Tools comes installed as part of the default installation with Visual Studio 2013.
Anyone else had this problem?
I've the same problem and found some decision possible it is suitable : http://sdksdotnetfunda.blogspot.com/2012/08/could-not-load-file-or-assembly.html
I have an error message that occurs every time I use SQL Server 2012 Management Studio to open or create a new database diagram, followed by an automatic restart of SSMS.
The error message is
Attempted to read or write protected memory. This is often an
indication that other memory is corrupt.
(Microsoft.VisualStudio.OLE.Interop)
Here's what I did to produce this problem:
Earlier, I had installed SQL Server 2008: via an option available when I downloaded Visual Basic Express 2010. No errors yet. I could create and edit database diagrams without problems. Then I uninstalled VB Express 2010, and installed Visual Studio 2012, only to find out that it was a trial version, which I didn't like, so I uninstalled Visual Studio 2012. I launched SSMS 2008 and tried to open a database diagram in one of my databases. I received an error that said
Specified Module cannot be Found. (MS Visual Database Tools)
I installed SQL Server 2012 with Management Studio, and then used the SSMS 2012 to try opening the database diagram. And instead of Specified module error, I got the error about attempting to read or write protected memory.
I am running Windows 7, SQL Server 2012 Express and I didn't uninstall SQL Sever 2008 Express (yet), Visual C# 2010 Express, Visual Basic 2010 Express.
EDIT: I attempted to fix this problem by applying a hotfix named SQLServer2012_RTM_CU1_kb2679368_11_0_2316_x64. It did not fix the problem. The hotfix was suggested by a user in an MSDN forum at this link: http://social.msdn.microsoft.com/Forums/en/sqlexpress/thread/1753d7ba-f6ec-4a8e-a1c9-ded2a5b7c607
I bumped into the same issue. Mine is SQL 2012 in windows7. I was trying connect to a sql server 2014 in Windows 2012 R2.
The problem was resolved after I upgraded my SQL 2012 client to 2014.
It is interesting that it was fine to work with SQL2014 with Windows 2012 but not windows 2012 R2.
For the sake of completeness I added this answer with all steps
required to solve this issue
It is a stupid error, which can occur in nearly all sersion of SQL Server Management Studio.
Look for a machine that had SSMS installed which ist still working without any error.
Copy all files of the folder from the working machine to the faulting machine
Folder 1: C:\Program Files (x86)\Common Files\microsoft shared\Visual Database Tools\
Folder 2: C:\Program Files (x86)\Common Files\microsoft shared\MSDesigners8\
Start SSMS again and the error is gone
verified for 2008R2, 2012, 2014
I was used to get this message and to get the management closed ALL-THE-TIME
when I notice a pattern in the bug ( and given the message I guessed the bug was isolated when trying to deal with the diagram database objects in the memory), if I create the diagram, place a table, put the first column with pk, save, close and open the diagram again it started working...
I used to repeat this for every new table added in the diagram without saving in disk
somehow, it stopped happening maybe after some updates in the host
I hope it works for you too
I figured out the answer, thanks to another post located here. Basically, even though my visual studio 2012 install was the trial version, it seemed to cause the same problem as the visual studio described in the link. Check it for a workaround.