SQL Server Management Studio (SSMS) Common Errors or Failures

SQL Server Management Studio (SSMS) by default gets installed on all servers where we install SQL Server database engine or related components. SQL Server DBA’s often use SSMS in order to manage the SQL Server instances for tasks like creating databases, creating logins, users and granting permissions, Creating maintenance plans or jobs, checking for any errors and troubleshoot various issues with SQL Server instance by running queries. SSMS has become one of the most important tool for a DBA to function their job. Most of the time, there wont be any errors with SQL Server Management Studio (SSMS), but at times, we may end up with some errors while using SSMS and we need to fix them quickly.

SQL Server Management Studio is dependent on many other components like Visual Studio, .Net Framework, etc, so changes to any of these components can also result in the failure or errors with SSMS.

Below are some of the common errors which we may see with SQL Server Management Studio (SSMS).
Error while trying to create new database diagram, which is crashing the SSMS with error
“Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (Microsoft.VisualStudio.OLE.Interop)”

You can resolve this issue by following below steps
– Copy and replace the DLL “dsref80.dll” in below path from a machine where SSMS is working fine in to the machine where the problem exists.
C:\Program Files (x86)\Common Files\microsoft shared\Visual Database Tools\dsref80.dll
– Replace all the files in below folder using the files from another server where SSMS is working fine.
C:\Program Files (x86)\Common Files\microsoft shared\MSDesigners8\
– Close and Open SSMS.

Error in SQL Server Management Studio: Failed to start debugger. Additional information: The EXECUTE permission was denied on the object ‘sp_enable_sql_debug’, database ‘mssqlsystemresource’, schema ‘sys’. (Microsoft SQL Server, Error: 229)
– You may receive above error message if you try to use the Debug button in SSMS, if it was by mistake, then no need to worry, but if you want to use the debug option in SSMS, then make sure below are true.
o SQL Server Management Studio must be running under a Windows account that is a member of the sysadmin fixed server roll.
o The Database Engine Query Editor window must be connected by using either a Windows Authentication or SQL Server Authentication login that is a member of the sysadmin fixed server role.
o The Database Engine Query Editor window must be connected to an instance of the SQL Server 2008 Database Engine. You cannot run the debugger when the Query Editor window is connected to an instance that is in single-user mode.

Error while trying to start SQL Server 2012 Management Studio (SSMS)
Cannot find one or more components. Please reinstall the application.
Exception has been thrown by the target of an invocation

– You may receive above errors while trying to open SSMS after you install Visual Studio 11. Visual studio might have been installed separately or may have been installed as part of some other software installation.
– To resolve this issue, follow the below steps
o Open registry editor from Start -> Run -> Type regedit
o In registry Editor navigate to HKEY_CURRENT_USER\Software\Microsoft\SQL Server Management Studio
o Backup and Delete the key 11.0_Config
o Start the SQL Server Management Studio and it should not open without any more errors.
– Restart ssms.exe

Operation not supported on SQL Server 2005
– You may received above error if you are using SQL Server 2005 Management Studio and connected to higher version of SQL instance like SQL 2012 or SQL 2008 R2 and then use a feature which was introduced in these higher versions. SSMS 2005 cannot be used to use features introduced in higher versions of SQL Server, you need to install and use higher version of SQL Server management Studio(SSMS)

microsoft .net framework error.unable to read the list of previously registered servers on this system.Re-register your servers in the registered servers windowvalue cannot be null.parameter name:viewinfo
(Microsoft.sqlserver.managment.sqlstudio.explorer)
Microsoft.SqlServer.Management.Sdk.Sfc.SfcSerializationException: Serialization operation on
ServerGroup[@Name=’SqlServerCompactEditionServerGroup’] has failed.
System.IO.DirectoryNotFoundException: Could not find a part of the path ‘c:\winnt\temp\qhn8zgxb.tmp’.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

– This error can occur if the user profile is corrupted. Normally we RDP to the server where SQL Server is installed using a domain account or local account and then open SSMS and then try to connect to SQL Server instance, if the profile of this domain or windows account is corrupt, then this error occurs.
– To resolve this error either create a new windows or domain account and login using the new account and connect to SSMS and then to SQL Server instance or repair the profile of the existing account.

The File %CommonDir%\dte80.olb could not be loaded. An attempt to repair this condition failed because the file could not be found. Please reinstall this program.”
The application cannot start

– This error can occur if one or more files related to SSMS is corrupt or missing. dte80.olb is a shared file used by the Visual Studio shell, Management Studio, Books Online, and the MSDN help viewer.
– To resolve this issue, either uninstall and reinstall the SSMS component or check if
C:\Program Files\Common Files\Microsoft Shared\MSEnv\dte80.olb file exists, if it does not exist, then copy this file from another server which has same SQL Server version and build, but better option is to reinstall the SSMS component.

Value cannot be null.
Parameter name: viewInfo (Microsoft.SqlServer.Management.SqlStudio.Explorer)

– There can be various reasons why you may see this error. Follow below to resolve this error
o Make sure that C:\ drive has enough free space.
o Launch SSMS by right click and choose run-as-administrator
o Create empty folder with name 2, if it does not exist in below path, so that you can navigate to below folders.
C:\Users\\AppData\Local\Temp\2
o Make sure from start>run>%temp% and start>run>%tmp% folders can be opened without any error, if it returns any error, contact your server administrator to fix the same.
o Apply latest Service pack or Cumulative Update
o Uninstall and reinstall SQL Server Management Studio

Evaluation Period has expired. For information how to upgrade your evaluation software please go to. Microsoft SQL Server Management Studio Complete (expires in x days)
– This error occurs, if you have installed SQL Server Management Studio or Database Engine using SQL Server Enterprise Evaluation Edition, which will expire after 180 days.
– You need to perform an Edition upgrade to an licensed version of SQL Server to fix the error.
– Sometimes, ever after successful edition upgrade, still you may receive this error, and to fix the error, set the CommonFiles registry key value to 3 under
HKLM\SOFTWARE\\Microsoft\Microsoft SQL Server\100\ConfigurationState and then rerun the edition upgrade.

Microsoft SQL Server Management Studio
Object reference not set to an instance of an object.
(Microsoft.VisualStudio.Platform.WindowManagement)

– Try below options to see if it resolves the error
o Repair the .net framework
o Open a command prompt by choosing run asa dministrator and then run below commands
C:\Program Files\Internet Explorer>regsvr32 /u ieproxy.dll
C:\Program Files\Internet Explorer>regsvr32 ieproxy.dll
C:\Program Files (x86)\Internet Explorer>regsvr32 /u ieproxy.dll
C:\Program Files (x86)\Internet Explorer>regsvr32 ieproxy.dll
regsvr32 actxprxy.dll
o Uninstall SSMS and reinstall SSMS

There are various other errors which cause failure of SSMS and will try to add as many as possible.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *