[Company Logo Image] 

Home Contents Coffee Break Credits Glossary Links Search

 
Troubleshooting

 

 

Home
Analysis Services
Azure
CLR Integration
High Availability
Open Source
Security
SQL Server 2008
SQL Server 2012
SQL Server 2014
SQL Server 2016
SQL Server 2017
SQL Server 2019
Tips
Troubleshooting
Tuning

Troubleshooting.

 

 

Troubleshooting Microsoft SQL Server 2022.


SSMS This backend version is not supported to design.
Error while using table designer on SSMS. Error: This backend version is not supported to design database diagrams or tables.

 

Troubleshooting Microsoft SQL Server 2019.


Alter Database not allowed within multi-statement transaction.
Msg 226, Level 16, State 6, Line 81. ALTER DATABASE statement not allowed within multi-statement transaction.

Component error code 0x84BB0001 System Error.
SQL Server 2019 Developer edition fails to install. Exit code (Decimal): -2061527940. Component error code: 0x84BB0001. Component error code: -2147467261. Component error code: 0x851F947C.

Exit code (Decimal): -2068119551 Cannot find registry key.
Overall Summary. Exit code (Decimal): -2068119551. Exit facility code: 1211. Exit error code: 1. Exit message: Cannot find registry key 'SOFTWARE\Microsoft\Microsoft SQL Server\150\ConfigurationState'.

MDF is not a Primary Database File Error 5171.
Error received from SQL Server Management Studio (SSMS) when you try to attach a database to a SQL Server instance: MDF is not a Primary Database File Error 5171.

Msg 10061 TCP Provider No connection could be made.
Msg 10061 received when trying to create a Polybase external data source to an Azure SQL Database. TCP Provider: No connection could be made because the target machine actively refused it.

Msg 15517 Execute as User.
Msg 15517, Level 16, State 1. Cannot execute as the database principal because the principal X does not exist.

Msg 46530 External data sources are not supported.
Msg 46530 received when trying to create a Polybase external data source to an Azure SQL Database. External data sources are not supported with type GENERIC.

Msg 46721 Create External Data Login Failed.
Msg 46721 Login failed while trying to create external data source. The login is from an untrusted domain and cannot be used with integrated authentication. Polybase, SQL Server 2019 CU1.

Msg 6586 Assembly could not be installed.
Msg 6586, Level 16, State 1. Assembly 'System.Drawing' could not be installed because existing policy would keep it from being used.

SQL Server 2019 scalar function generates dump.
SQL Server 2019 execution of scalar function generates SQL Server stack dump and restart the SQL Server service. Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION.

Wait on the Database Engine recovery handle failed.
SQL Server service cannot start after installing SQL Server 2019 on Windows 10/11. Error: Wait on the Database Engine recovery handle failed.
 

Troubleshooting Microsoft SQL Server 2017.


Error SQL72014 .Net SqlClient Data Provider Msg 12824.
Unable to import a SQL Azure Database bacpac to a SQL Server on-promise instance. Error SQL72014: .Net SqlClient Data Provider: Msg 12824, level 16, State 1.

Error SQL72016 Execution Timeout Expired.
Unable to import a SQL Azure Database bacpac to a SQL Server on-promise instance. Error SQL72016: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

SQL Server 2017 Dump RaiseInconsistencyError 0x5ed.
System drive running out of space due to SQL Server 2017 generating dump files consuming hundreds of gigabytes.

 

Troubleshooting Microsoft SQL Server 2016.


Backup to URL SQLSTATE 42000 Error 3271 Error 3013.
A nonrecoverable I/O error occurred on file backup. Backup to URL received an exception from the remote endpoint. Exception Message: The remote name could not be resolved.

Error 0x80070570 Failed to extract all files from container.
SQL Server Management Studio 2016 (SSMS 2016) failed to install, e000: Error 0x80070570: Failed to extract all files from container, erf: 1:4:0.

Error 5149 while attempting expand physical file.
We got Error 5149 while attempting to increase the size of a database secondary file with SSMS despite having 700 GB of free disk space.

Error installing Microsoft Visual C++ 2015 Redistributable.
VS Shell installation has failed with exit code 1638. Error code: 1638.

Method not found Void.
Cannot connect to SQL Server after installing SSMS 2016 july Update. Error. Method not found: 'Void.

Microsoft.SqlServer.Configuration.SetupExtension.
Could not load file or assembly 'Microsoft.SqlServer.Configuration.SetupExtension, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies.

Oracle JRE 7 Update 51 (64-Bit) or higher is required.
Oracle Java SE RunTime Environment (JRE) version 7.51 or higher (64-bit) is a software requirement for installing the PolyBase Query Service for External Data feature of SQL Server 2016.

Prerequisites of SQL Server 2016 MDS Add-in not installed.
Error installing Microsoft SQL Server 2016 MDS Add-in for Excel. The prerequisites are not installed: Visual Studio 2010 Tools for Office Runtime.

Report models cannot be uploaded to SSRS 2016.
Trying to upload a Report Model on the Web portal of SQL Server 2016 Reporting Services resulted on the error 'Feature not supported'.

Request couldn't be performed because of an IO device error.
Trying to backup a big database to URL, the user received error: The Request could not be performed because of an IO device error. Azure SQL VM.

SQL Backup to URL A nonrecoverable I/O error occurred.
Backup to URL on an Azure SQL Server 2016 VM started to fail intermittently with error: A nonrecoverable I/O error occurred.

SQL Server 2016 Bcp SQLState IM002 NativeError 0.
Received error SQLState = IM002, NativeError = 0 using bpc to export a table from SQL Server 2016.

SQL Server installation failed with Exit code -2068054016.
SQL Server 2016 Installation Error : A newer version of Microsoft SQL Server Data-Tier Application Framework is already installed.

SQL Server Notification - Low Virtual Memory.
RESOURCE_MEMVIRTUAL_LOW. Event ID 2004 Warning Microsoft-Windows-Resource-Exhaustion-Detector.

The account for PolyBase Engine service is not allowed.
The specified account for SQL Server PolyBase Engine (same error for PolyBase Data Movement) service is not allowed.

Unable to get information from SQL Server.
Received error [Unable to get information from SQL Server: YourServerName] while installing a third-party java application.

Warning Setup Limited to Reporting Services for SharePoint.
Unable to install database engine on SQL Server 2016, only Reporting Services (SharePoint) and Reporting Services Add-in for SharePoint products are allowed to install.





 

Troubleshooting Microsoft SQL Server 2014 (Hekaton).


Could not load schema model from package.
Microsoft SQL Server Management Studio: Could not load schema model from package. (Microsoft.SqlServer.Dac). Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider is not valid.

Error 29569 when trying to uninstall SQL Server 2014.
SQL Server Setup: "The following error has occurred: SQL Server Setup failed to restore the instance id".

Error Applying the Filestream Settings.
There was an unknown error applying the filestream settings. Check the parameters are valid. (0x80041001).

Error SQL71564 Extract Data-tier Application.
Microsoft SQL Server Management Studio. Error SQL71564: Error validating element [xxx]: The element [xxx] has been orphaned from its login and cannot be deployed.

Log Shipping [SQLSTATE 42000] (Error 14421).
 [SQLSTATE 42000] (Error 14420) The log shipping secondary database KEVINR\KEVINR2.AdventureWorksDW2008 has restore threshold of 45 minutes and is out of sync. No restore was performed for 898 minutes.

Long Path Names to Files on SQL Server Media.
Global Rules. Long path names to files on SQL Server installation media (failed).

Not a Valid Database File Header.
The header for file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\AdventureWorks_Log.ldf' is not a valid database file header. The FILEID property is incorrect. (Microsoft SQL Server, Error: 5172)

RsFxConfiguration service rsfx0310.
SQL Server 2014 installation may fail with error message 'RsFxConfiguration service rsfx0310'.

Rule Same Architecture Installation failed.
Rule failed trying to install SQL Server Data Tools Business Intelligence for Visual Studio 2013 (SSDT-BI).

SQL Server Data Tools package did not load correctly.
**The 'Microsoft SQL Server Data Tools' package did not load correctly. The problem may have been caused by a configuration change or by the installation of another extension.

Using dbghelp.dll version 4.0.5.
SQL Server Error Log message: Using 'dbghelp.dll' version '4.0.5'. Message originated by Database Performance Metric Provider (SharePoint 2013).





 

Troubleshooting Microsoft SQL Server 2012 (Denali).


Attempted to perform an unauthorized operation.
HResult : 0x84bb0001. FacilityCode : 1211 (4bb). ErrorCode : 1 (0001). Inner exception type: System.UnauthorizedAccessException Message: Attempted to perform an unauthorized operation. HResult : 0x80070005.

Cannot alter a computed column on a table.
Cannot alter a computed column on a table in Microsoft SQL Server.

Computer does not meet the minimum requirements.
The operating system on this computer does not meet the minimum requirements for SQL Server "Denali".

Database Mirroring Disconnected.
Learn how to reconnect a configured database mirroring when the principal server says "disconnected".

Database mssqlsystemresource is being recovered.
Error: Command execution failed: Failed to retrieve data for this request. Error: Database 'mssqlsystemresource' is being recovered. Waiting until recovery is finished.

Error 1406 installing SQL Server Setup Support Files.
Error 1406. Error installing SQL Server Setup Support Files. Could not write value SupportFiles to key \Products \A62E4FB87F4B748409BC2E46CF2C3268\Features

Error 1935 Microsoft.VC90.MFCLOC.
Error 1935. An error occurred during the installation of assembly 'Microsoft.VC90.MFCLOC, version="9.0.30729.4974", publicKeyToken="1fc8b3b9a1e18e3b", processorArchitecture="x86", type="win32".

Error SQL72014.
Error: SQL72014: .NET SqlClient Data Provider: Msg 9982, level 16, State 100, Line 1 Cannot use full-text search in user instance.

Error while enabling Windows feature NetFx3.
Error while enabling Windows feature: NetFx3, Error Code: -2146498298, Please try enabling
Windows feature: NetFx3 from Windows management tools and then run setup again.

I/O is frozen on database.
Information messages appear on SQL Server Error Log with Event ID: 3197 and description 'I/O is frozen on database test'.

Illegal use of outer join operator.
Non-ANSI outer join operators like *= and =* are not supported in SQL Server 2012 and SQL Server 2014.

License agreement cannot be located.
The SQL Server license agreement cannot be located for the selected edition, EVAL. This could be a result of corrupted media or the edition being unsupported by the media. Error code 0x858C001B.

Linked Server Msg -2146893044.
Received - Msg -2146893044, Level 16, State 1 - trying to execute a query to a SQL Server linked server using the OPENQUERY function.

LocalDB not supported on this OS.
Installation of this product failed because it is not supported on this operating system.

Microsoft.ACE.OLEDB.12.0 is not registered.
The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not registered. If the 32-bit driver is not installed, run the package in 64-bit mode.

Microsoft SQL Server Error 950.
Database 'Northwind' cannot be upgraded because its non-release version (539) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe.
 
Msg 7399 Msg 7303 OPENROWSET.
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" reported an error. Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)".

SSIS Error 0x80004005 Invalid object name.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Invalid object name 'dbo.FactCurrency'.".

SSIS Error 0x80004005 Violation of Primary Key Constraint.
SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. Hresult: 0x80004005 Description: "Violation of PRIMARY KEY constraint 'PK_FactCurrencyRate_CurrencyKey_DateKey'. Cannot insert duplicate key in object 'dbo.FactCurrencyRate'.

SQL Server installation Exit code -2068051667 Error 2349.
SQL Server 2012 installation failed with Error code 2349 (The installer has encountered an unexpected error). Summary.log file associated with the installation shows Exit code -2068051667.

SQL Server Setup Rules Failed.
RULE: There is an internet connection to Microsoft .NET Framework 4.0 download center (failed). RULE: Microsoft .NET Framework 3.5 Service Pack 1 is required (failed).

The AcquireConnection method failed 0xC001404.
SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "localhost.AdventureWorksDW2012" failed with error code 0xC0014041.

The Proactive Caching feature is not included.
Errors related to feature availability and configuration: the 'Proactive Caching feature' is not included in the '64 Bit Standard' edition of Analysis Services.

The Project Cannot Be Debugged.
Microsoft SQL Server Report Designer. The project cannot be debugged because no starting report is specified.

Try_convert is not a recognized function.
Msg 195, Level 15, State 10, Line 1. 'TRY_CONVERT' is not a recognized built-in function name.

Warning - The For Each File enumerator is empty.
Warning: The For Each File enumerator is empty. The For Each File enumerator did not find any files that matched the file pattern or specified directory was empty.





 

Troubleshooting Microsoft SQL Server 2008 R2 (Kilimanjaro).


Cannot create a linked server to Oracle
Cannot create an instance of OLE DB Provider "OraOLEDB.Oracle" for linked server "RH6I".
(Microsoft SQL Server, Error: 7302).

Change Pending State
Exit code (Decimal): -2068709375. Exit facility code: 1202. Exit error code: 1. The NT service 'SQLSERVERAGENT' could not be started.

Configuration system failed to initialize 0x84B10001
SQL Server Setup has encountered the following error. Configuration system failed to initialize. Error code 0x84B10001.

Conversion failed when converting date and/or time
Msg 241, Level 16, State 1, Line 10. Conversion failed when converting date and/or time from character string.

Error 2812 Could not find proc_ECM_CleanupChangeLog
Received Error: 2812, Severity: 16, State: 62. Could not find stored procedure proc_ECM_CleanupChangeLog.

Error 7202 - Could not find server in sys.servers
Error: 7202, Severity: 11, State: 2. Could not find server 'XXXX' in sys.servers.
 
Exit Message InstanceDir
SQL Server installation failed. Exit code (Decimal): -2068578304. Exit facility code: 1204. Exit error code: 0.

Linked Server Error ORA-01017
Error ORA-01017 while trying to query an Oracle linked server via the OPENQUERY function.

Msg 102 incorrect syntax near tempdev
Msg 102, Level 15, State 1, Line 2. Incorrect syntax near tempdev.

Msg 7411 Linked Server
Error trying to use EXEC() AT to run a pass-through query on a linked server. Msg 7411, Level 16, State 1, Line 1. Server 'servername' is not configured for RPC.
 
No Features Selected for Upgrade
There are no features selected for upgrade. Exit facility code: 1207. Exit error code: 1602. Exit message: User has cancelled.

Restore failed Microsoft.SqlServer.Management.RelationalEngineTasks
Restore of database [databasename] failed. (Microsoft.SqlServer.Management.RelationalEngineTasks. System.Data.SqlClient.SqlError: The database was backed up on a server running version 7.00.0623. That version is incompatible with this server.

Rule Windows PowerShell Failed
Error received while installing Microsoft SQL Server 2008 R2 with Advanced Services in the "Setup Support Rules" page.

Service Broker Error 28054
Error: 28054, Severity: 11, State: 1. Service Broker needs to access the master key in the database 'XXXX'.

SQL Server Agent error code 0x5 Error 15404
The job failed. Unable to determine if the owner (DOMAIN\userb) of job job_name has server access (reason: Could not obtain information about Windows NT group\user DOMAIN\userb, error code 0x5. [SQLSTATE 42000] (Error 15404))

SQL Server Setup Error code 0x84B20001
User received Error code 0x84B20001 from SQL Server 2012 setup. The patch file cannot be opened.

SQL Server setup media does not support the language
This SQL Server setup media does not support the language of the OS, or does not have the SQL Server English language version installation files.

Subscriber does not satisfy version compatibility
The selected Subscriber does not satisfy the minimum version compatibility level of the selected publication.

The automatically saved settings file cannot be found
Error 'The automatically saved settings file cannot be found' when opening SQL Server Management Studio.

The resource governor is not available
Alter failed for ResourceGovernor 'Microsoft.SqlServer.Management.Smo.ObjectKeyBase'. (Microsoft.SqlServer.Smo). 'ALTER RESOURCE GOVERNOR RECONFIGURE' failed.

The server version is not supported
JDBC connection error while trying to connect to a SQL Server 2008 R2 instance  from a Oracle server.

The specified DSN contains an architecture mismatch
IM014:[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and the Application.

Transient database snapshot has been marked suspect
Error Msg 5269, Level 16, State 1. The transient database snapshot for database X has been marked suspect due to an IO operation failure.

Unable to modify table
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Change of safety level not allowed
Msg 1473, Level 16, State 6, Line 1. This SQL Server edition does not allow changing the safety level. ALTER DATABASE command failed.






 

Troubleshooting Microsoft SQL Server 2008 (Katmai).


Cannot connect to WMI provider 0x8004100.
You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager. Invalid class [0x8004100]

Cannot Launch Activity Monitor for a SQL SQL Server 2000 Instance
The new Activity Monitor does not support SQL Server 2000.

Cannot Resolve the Collation Conflict.
(Microsoft.SqlServer.ConnectionInfo) Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the UNION operation. (Microsoft SQL Server, Error:468)

Could not connect to the report server.
Could not connect to the report server http://computername:8080/ReportServer. Verify that the TargetServerURL is valid and that you have the correct permissions to connect to the report server.

Detach Database Failed for Server. (Microsoft.SqlServer.Smo)
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo). Cannot execute 'sp_updatestats' because the database is in read-only access mode. Cannot DETACH a database snapshot. (Microsoft SQL Server, Error: 15635)

Error Code is 2337.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337.

Error Reverting a Database to a DB Snapshot.
Msg 5070, Level 16, State 2, Line 4. Database state cannot be changed while other users are using the database. Msg 3013, Level 16, State 1, Line 4. RESTORE DATABASE is terminating abnormally.

Evaluation Period Has Expired.
Learn how to upgrade an instance of SQL Server 2008 R2 Evaluation Edition (that has expired) to a licensed edition without losing any data or any configuration.

Invalid object name sys.dm_db_stats_properties.
Msg 208, Level 16, State 1, Line 12. Invalid object name 'sys.dm_db_stats_properties'.
 
Msg 6522, Level 16, State 1, Line 3  ... Aggregate 'geometry'
Msg 6522, Level 16, State 1, Line 3. A .NET Framework error occurred during execution of user defined routine or aggregate 'geometry': System.FormatException: 24141.
Msg 6522, Level 16, State 1, Line 3  ... Aggregate 'geometry' (2)
Msg 6522, Level 16, State 1, Line 3. A .NET Framework error occurred during execution of user defined routine or aggregate 'geometry': System.FormatException: 24119.

Reporting Services Catalog Error
Rules "Reporting Services Catalog Database File Existence" and "Reporting Services Catalog Temporary Database File Existence" failed after SQL Server 2008 ran a set of installation rules.

Restart Computer Failed
Trying to install SQL Server 2008 Developer edition setup fails at the Setup Support Rules page on the Rule "Restart Computer".

Saving Changes Is Not Permitted
Saving changes is not permitted. The changes you have made require the following tables to be dropped and re-created.

SQL Server 2008 setup requires .NET Framework
SQL Server 2008 setup requires Microsoft .NET Framework and an updated Windows Installer to be installed.

SQL Server encountered error 0x80070218
Msg 30046, Level 16, State 1, Line 1. SQL Server encountered error 0x80070218 while communicating with full-text filter daemon host (FDHost) process.

The conversion of a varchar data type to a datetime data type resulted in an out-of-range value
Error received when you try to store dates earlier than year 1753 on datetime fields.

There are validation  errors on this page
Click OK to close this dialog box. Review errors at the bottom Setup page, then provide valid parameters or click Help for more information.





 

Troubleshooting Microsoft SQL Server 2005 (Yukon).

A fatal error occurred while reading the input stream from the network. The session will be terminated
Event Type: Error. Event Source: MSSQLSERVER. Event Category: (2). Event ID: 4014.

Cannot access the specified path or file on the server.
Cannot access the specified path or file on the server. Verify that you have the necessary security privileges and that the path or file exists.
 
Cannot create new connection because in manual or distributed transaction mode.
Event Type: Error.  Event ID 3501.  Event Source:  MMArrayManager.

Cannot Kill Process with Status Suspended.
Killed process was present on the Activity Monitor with status “Suspended” and command “KILLED/ROLLBACK”.
 
Cannot show requested dialog (SqlMgmt)
An exception occurred while executing a Transact-SQL statement or batch.(Microsoft.SqlServer.ConnectionInfo). Lock request time out period exceeded. (Microsoft SQL Server, Error: 1222).

Cannot Start SQL Server Agent Service
[298] SQLServer Error: 22022, CryptUnprotectData() returned error -2146892987, 'The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.' [SQLSTATE 42000]. [442] ConnConnectAndSetCryptoForXpstar failed (0).
 
Class Not Registered (Microsoft.SqlServer.SqlTools.VSIntegration).
Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
(Microsoft.SqlServer.SqlTools.VSIntegration).
 
Could not connect because the Maximun Number of 1 DAC Already Exists
Could not connect because the maximum number of '1' dedicated administrator connections already exists.

Error 29503 Installing SQL Server 2005.
The SQL Server service failed to start. The error is (1053) The service did not respond to the start or control request in a timely fashion. Error Number : 29503.
 
Error Creating a New Job
Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey'
to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'.  (Microsoft.SqlServer.Smo)
 
How to rebuild system databases in SQL Server 2005
How to rebuild the master database for a corrupted installation of SQL Server.

Invalid attempt to GetBytes on column.
Error message is: Invalid attempt to GetBytes on column 'FECHA_GENERACION'. The GetBytes function can only be used on columns of type Text, NText, or Image.

KB955706 failed to install
We received the following error installing SP3 on a SQL Server 2005 Developer Edition: "A recently applied update, KB955706, failed to install".

Login Failed for User
Source Logon. Login failed for user 'DOMAIN\user account'. [CLIENT: 192.1681.1]

Login Failed for User Error 18452
Windows cannot query for the list of Group Policy objects. The kerberos subsystem encountered a PAC verification failure. The Security System could not establish a secured connection with the server. The kerberos client received a KRB_AP_ERR_MODIFIED error from the server.

Maintenance Plan Job Failed
The job failed. The Job was invoked by User Domain\user. The last step to run was step 1 (Monday).

MS DTC was unable to start
MS DTC was unable to start because the installation was not configured to run on a cluster.
 
MSSQLServerADHelper Event Id 100
Event Type: Error. Event Source: MSSQLServerADHelper. Event ID: 100.
MSSQLSERVER Event ID 3041
Event Type: Error. Event Source: MSSQLServer. Event ID: 3041. BACKUP failed to complete the command BACKUP DATABASE <DB Name>

ORA-12545 Connection failed because target host or object does not exist.
Error received while using SQL Server Migration Assistant (SSMA) 2005 for Oracle.

Property IsLocked is not available for login
This property may not exist for this object, or may not be retrievable due to insufficient access rights.
 
Restore failed for Server
Restore failed for Server <Instance Name>. (Microsoft.SqlServer.Smo). Additional information: System.Data.SqlClient.SqlError: The backup set holds a backup of a database other than the existing <Database Name>. (Microsoft.SqlServer.Smo).

Set property devices to accomplish this action
Backup failed for Server 'XXXX'. Set property Devices to accomplish this action. (Microsoft.SqlServer.Smo).

SQL Server has encountered occurrences of cachestore flush
SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.

SQL Server Resource Group Failed
Event Type: Error. Event Source: MSSQLSERVER. Event ID: 17187.  SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. Event Type: Error. Event Source: ClusSvc. Event ID: 1069. Cluster resource 'SQL Server' in Resource Group 'Resource_group_name' failed.

SQL Server Setup cannot install files
Event Type: Error. Event Source: MsiInstaller. Event ID: 10005. Product: Microsoft SQL Server 2005 -- Error 28062. SQL Server Setup cannot install files to the compressed or encrypted folder
 
SSPI handshake failed
SSPI handshake failed with error code 0x80090304 while establishing a connection
with integrated security; the connection has been closed. [CLIENT: <ip address>].

Successful Installation SP3 not Applied on Server
After a successful installation of SQL Server 2005 Sp3 the instance is still at SP2.

The Operating System Returned Error 21
The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00000000056000 in file 'XXXX'.
 
The SQLBrowser service was unable to establish Analysis Services discovery
Event Type: Warning. Event Source: SQLBrowser. Event Category: None. Event ID: 9.

The Transaction Manager is not available
Hotfix.log: MSP Error 29549 Failed to install and configure assemblies. Error: -2146233087. Error message: Unknown error 0x80131501. Error description: The Transaction Manager is not available. (Exception from HRESULT: 0x8004D01B).

Unspecified Error
Microsoft SQL Server Management Studio. Unspecified error (MS Visual Database Tools).
 
Warning SQLSERVERAGENT Event ID 208
SQL Server Scheduled Job <job name> - Status: Failed. Message: The job failed. Unable to determine if the owner <user name> of job <job name> has server access.
 
Warning SysmonLog Event ID 2059.
Invalid user name or password for the <Instance Name> log session. This session will not be started.
 





Troubleshooting Microsoft SQL Server 2005 Express Edition.

Attach Database Failed
Attach database failed for Server 'SERVERNAME\SQLEXPRESS'. (Microsoft.SqlServer.Express.Smo). Unable to open the physical file "filename.mdf". Operating system error 5: "5(error not found)".(Microsoft SQL Server, Error: 5120)

Backup failed for Server
Backup failed for Server 'servername'. (Microsoft.SqlServer.Smo). System.Data.SqlClient.SqlError:  Cannot open backup device.   Operating system error 5(Access is denied.). (Microsoft.SqlServer.Smo)

Error MsInstaller EventId 11706
An installation package for the product Microsoft SQL Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'.

Failed to Create Configuration Database
SharePoint Products Configuration Wizard. Configuration Failed. Failed to create the configuration database. An exception of type System.IO.FileNotFoundException was thrown.
 
SQLBrowser Event Id 3
The configuration of the AdminConnection\TCP protocol in the SQL instance SQLEXPRESS is not valid. Event Type: Warning. Event Source: SQLBrowser. Event Category: None. Event ID: 3.
 
SQL Server Express 4 GB Limit
Restore failed for Server <Instance Name>. (Microsoft.SqlServer.Smo)
Additional information: System.Data.SqlClient.SqlError: CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 4096 per database.

Starting Up Database
Examining the SQL Server error log of a Microsoft SQL Server 2005 Express Instance, we found the following record repeated many times:  Starting up database 'DatabaseName'.

The Media Family on Device is Incorrectly Formed
The media family on device 'Backupfile.bak' is incorrectly formed. SQL Server cannot process this media family.
RESTORE HEADERONLY is terminating abnormally. (Microsoft SQL Server, Error: 3241)
 

Troubleshooting Microsoft SQL Server 2000 (Shiloh / Liberty).


Backup Log is terminating abnormally.
'LogicalBackupDevice_Voice' failed, status = 112. See the SQL Server error log for more details. [SQLSTATE 42000] (Error 3202) BACKUP LOG is terminating abnormally.

Buffer Cache Hit Ratio Very Low.
Low readings for the buffer cache hit ratio.

Error 15457 Severity 0 State 1.
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.

Error 3205 Too Many Backup Devices Specified.
Too many backup devices specified for backup or restore; only 64 are allowed.  RESTORE HEADERONLY is terminating abnormally. (Microsoft SQL Server, Error: 3205).

Huge SQLAGENT.OUT log file.
The error log file for the SQL server Agent service is taking a huge amount of disk space.

Index Corruption.
Could not find the index entry for RID '160314a879010000' in index page (1:428288), index ID 3, database 'DATABASENAME'.

Invalid Input Trace File.
Microsoft.SqlServer.BestPracticesAnalyzer.UpgradeAdvisor
Invalid input trace file or the version of the trace file filename.trc is not supported.
 
Perflib Event Id 1023.
Event Type Error. Event Id 1023. Source Perflib.
 
Property Owner is not available for Database.
Cannot show requested dialog. (SqlMgmt). Property Owner is not available for Database ’[     ]’.  This property may not exist for this object, or may not be retrievable due to insufficient access rights.
(Microsoft.SqlServer.Smo)

Purge job history failed for JobServer
Purge job history failed for JobServer 'SERVERNAME'.(Microsoft.SqlServer.Smo).  An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo). @oldest_date is not a parameter for procedure sp_purge_jobhistory. (Microsoft SQL Server, Error: 8145)

Warning Server Agents Event Id 1123.
System Information Agent: Health: Post Errors were detected. One or more Power-On-Self-Test errors were detected during server startup. [SNMP TRAP: 6027 in CPQHLTH.MIB]


Troubleshooting Applications That Use Microsoft SQL Server.

An incompatible SQL Server version was detected.
Error "An incompatible SQL Server version was detected" while generating a DDL script for SQL Server from an Entity Framework model in Visual Studio 2013.

Backups with EMC Networker Finish with Error 3041.
Error: 3041, Severity: 16, State: 1. BACKUP failed to complete the command BACKUP LOG SharePoint_Config.

BusinessObjects: Connection or SQL sentence error: (DA0005)
Exception: DBD, [Microsoft OLE DB Provider for SQL Server]: [DBNETLIB] [ConnectionOpen (PreLoginHandshake()).] General network error. Check your network documentation. State: 08001.

Cannot Connect to Database Master.
Error received from SharePoint Products Configuration Wizard while installing SharePoint 2010.

Cannot insert the value NULL into column.
com.microsoft.sqlserver.jdbc.SQLServerException: Cannot insert the value NULL into column 'CustomerId', table 'XXXXX.XX.Customer'; column does not allow null.

Cannot install SSMS v17 on Windows 10 32-bit.
This installation package is not supported by this processor type. Contact your product vendor (0x80070661)

Cannot Open User Default Database.
Workflow Subscriber Configuration Utility
Cannot open user default database. Login failed. Login failed for user 'laserfiche'.

Connection Failed - Array 28000.
Connection Failed. Array ( [0] => Array ( [0] => 28000 [SQLSTATE] => 28000 [1] => 18456 [code] => 18456 [2] => [Microsoft][ODBC Driver 11 for SQL Server][SQL Server]Login failed for user.

Could not find stored procedure sp_dboption.
Error while attaching database on Microsoft Accounting 2009: Could not find stored procedure 'sp_dboption'.

Create Database Permission Denied.
Error has occurred while configuring Laserfiche Workflow 8.

Database <databasename> exists but it is unaccessible.
HP Data Protector is trying to backup databases that are "offline".

Error connecting BIRT report to SQL Server.
Learn how to troubleshoot errors received while connecting a BIRT report to SQL Server.

Error connecting to VMware vCenter Update Manager.
vSphere Client. There was an error connecting to VMware vCenter Update Manager - [computername:443]. Database temporarily unavailable or has network problems.

Error has occurred while opening database 'DBName'.
Check if the database exists on the server. See Data Protector debug.log and SQL Server error log for details.
 
Error Installing SCOM 2007 Database.
Setup cannot locate the SC database. Setup could not locate the SC database on the specified server. Invalid Microsoft Operations Manager Database Version
 
Error Number 7399 Linked Server Teradata.
Error Number 7399 received from SQL Server Management Studio (SSMS) when trying to expand tables and views on a Teradata linked server.

Error on Data Protector Manager.
Error has occurred while executing a SQL statement. Error message: '<Microsoft SQL-DMO (ODBC SQLState: 42000):bc5>. [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is terminating abnormally.'

Error ORA-01017 on Oracle Database Gateway dblink.
Error ORA-01017: invalid username/password; logon denied. Error received when testing an Oracle database link for Microsoft SQL Server.

Error Registering Laserfiche Repository.
Laserfiche Repository Wizard. Could not connect to SQL Server to verify that the database exists. Do you want to continue?

Error 51005: The row was not inserted in the alarm_history table.
Error: 51005, Severity: 10, State: 1. etalk Qfiniti 3.5.
 
Error Upgrading to VMM 2012 R2.
Setup cannot be completed. VMM management server. Virtual Machine Manager Setup cannot create a backup of the existing database. Verify that you have the necessary rights to backup the Virtual Machine Manager database, and then restart Setup.
 
Errors SQL72014 & SQL72045 migrating Azure SQL.
Errors SQL72014 and SQL72045 were received when using the Deploy Database dialog on SSMS to migrate a SQL Server database (bacpac) to Azure SQL Database.

Exception thrown while executing SQL script.
Error received while upgrading vCenter Server 4.0 to version 4.1

General Database Error 9008.
Error. Could not lock document for writing. General database error. [9008].

INSERT failed because the following SET options have incorrect settings.
This error message appeared on the screen while configuring ePolicy Orchestrator 4.0.

Invalid Operations Manager Database Version.
Setup found that the Microsoft Operations Manager database version on the specified database server is not the same as the current product version.

jTDS Exception Connection Refused.
java.sql.SQLException: Network error IOException: Connection refused: connect at net.sourceforge.jtds.jdbc.ConnectionJDBC2
 
jTDS Exception - Connection Timed Out.
SQLException while getting database connection. Check if database daemon is running java.sql.SQLException: Network error IOException: Connection timed out: connect at net.sourceforge.jtds.jdbc.ConnectionJDBC2.

ODBC Error Installing VMware vSphere.
VMware vCenter Server. The DSN, 'vcenter' does not exist or is not a 32 bit system DSN. vCenter Server requires a 32 bit system DSN.

ORA-00904 Invalid Identifier.
OLE DB provider "MSDAORA" for linked server "ODBCDataSource" returned message "ORA-00904: : invalid identifier".
 
ORA-00911 Invalid Character.
Error while trying to query a table on SQL Server via an Oracle DBLINK.

ORA-12704 character set mismatch.
Error creating a report in Business Objects that was using a query, joining tables from an Oracle server and a SQL Server 2005 instance.

ORA-28500 connection from ORACLE to non-Oracle system.
ORA-28500: connection from ORACLE to a non-Oracle system. Error received when testing an Oracle database link for Microsoft SQL Server.

Permissions needed to create new DB account.
The user "solarwind" does not have permission to create a new database account. You must select an existing SQL account.
 
Record Retrieval Error ConnectionRead.
Record Retrieval Error. Error: (Connection Read(recv()).(01000)) attempting to access a record from the MERCAN file. Returning to previous window.

Replica is inconsistent.
Error found on DPM 2010 Administrator Console saying “Replica is inconsistent”.

Report Server has encountered a SharePoint error.
rsSharePointError. The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317).

Required permissions needed to install vCenter Server.
VMware vCenter Server. The DB user entered does not have the required permissions needed to install and configure vCenter Server with the selected DB.

RollbackSnapshotTempDB.
Msg 823, Level 24, State 2, Procedure objects$, Line 2. The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x000000000ee000 in file '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy452\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content_XXXXXXX.mdf'.

SharePoint cannot connect to SQL Server - Event 3355.
Critical Event 3355 SharePoint Foundation. Cannot connect to SQL Server, XXX not found. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

SharePoint Out Of Memory.
Sessions remaining blocked on the ASPState database are creating blocking of sessions on SQL Server instance serving a SharePoint farm. SharePoint Out Of Memory 0x8007000e.

SQL Common Language Runtime is not enabled on the server.
The current user does not have privileges to enable CLR (needs to be a member of 'SysAdmin' role).

SQL Server security mode.
We received the following warning from System Center Configuration Manager setup: SQL Server security mode.

SQL Server version is not supported by SCOM 2012.
The installed version of SQL Server is not supported. Verify that the computer and installed version of SQL Server meet the minimum requirements for installation.

SSMS 17.0 crashes while installing Event Name CLR20r3.
While installing SQL Server Management Studio (SSMS) 17.0 you may find SSMS setup crashes with an error message mentioning Problem Event Name: CLR20r3.

SSMS Error 1321 Installer has insufficient privileges.
MainViewModel.OnPackageError: setup failed for packageId: sqlncli.msi, package: Microsoft SQL Server 2012 Native Client , errorCode: 1321, errorMessage: The Installer has insufficient privileges to modify this file: C:\WINDOWS\SysWOW64\1033\sqlnclir11.rll.

SSMS Error inserting data into table Error 4815.
Importing a CSV file to a SQL Server database using Import Flat File Wizard of SQL Server Management Studio (SSMS), a user got the following error message: Error inserting data into table.

TF254027: You must correct all errors.
Configuring TFS 2010 using standard configuration we received the following errors: TF254027, Error [ Reporting ] TF255344, Error [ Reporting ] TF255274, Error [Reporting ] TF255151 and Warning [Project Collection] TF255331.

The system cannot find the file specified.
EMC (Legato) Networker. The system cannot find the file specified. Cannot run nsrsqlsv: The system cannot find the file specified. InstanceName1:MSSQL:database1: retried 1 times.

The Visual Studio component cache is out o date.
When you try to open a new query window with SSMS you get error: The Visual Studio component cache is out of date (assembly: Microsoft.VisualStudio.Platform.VSEditor, Version=15.0.0.0, Culture=neutral,
PublicKeyToken=b033f5f7f11d50a3a).

This Recordset Is Not Updatable.
When you try to update, delete or insert a record on a table in an Access Project, Microsoft Access beeps, and you receive an error in the status bar.

Unable to connect to the VMM database.
Error (2605). Unable to connect to the VMM database because of a general database failure. SQL error code: 547.

VMM 2012 SP1 Setup Wizard closes unexpectedly.
Setup Wizard closes unexpectedly when we click the "Next" button on the Library Configuration page.

w3wp.exe (0x1B08).
w3wp.exe (0x1B08) 0x1AC8 SQL Server Reporting Services SOAP Client Proxy 0000 High Exception encountered for SOAP method GetSystemProperties: System.Net.WebException: Unable to connect to the remote server.
 
 

Troubleshooting Azure SQL Database, Azure Synapse Analytics, Azure SQL Managed Instance, SQL Data Sync and Azure Data Factory


.Net SqlClient Data Provider: Msg 0 Level 11 State 0.
The connection is broken and recovery is not possible. The client driver attempted to recover the connection one or more times and all attempts failed. Increase the value of ConnectRetryCount to increase the number of recovery attempts.

Azure Data Factory / Azure SQL SqlErrorNumber=64.
Error on Azure Data Factory SqlErrorNumber=64 when trying to connect to Azure SQL database or when running a Copy task.

Azure Data Factory ERROR [IM003] ODBC Connection.
Error received trying to create a linked service after installing Progress OpenEdge 11.7 ODBC Driver on the Azure Data Factory SHIR. ERROR [IM003] Specified driver could not be loaded due to system error 5: Access is denied.
 
Azure Data Migration Service Failed to Connect.
Azure Data Migration Service is unable to connect to source SQL Server instance by using the name of the instance. Error 53 - SQL connection failed.

Azure SQL - The semaphore timeout period has expired.
When using SSMS (SQL Server Management Studio) to connect to an Azure SQL Database you keep getting error - The semaphore timeout period has expired.

Azure SQL Database Msg 40197 Error code 40549.
Msg 40197 Level 20, State 1. The service has encountered an error processing your request. Please try again. Error code 40549.

Cannot Connect to SQL Azure.
Connect to Server. Cannot connect to hhkxxxxxxx.database.windows.net. An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo). Invalid object name ‘sys.configurations’. (Microsoft SQL Server, Error: 208).

Cannot open server requested by the login.
Error encountered during the service operation. ; Exception Microsoft.SqlServer.Management.Dac.Services.ServiceException:Unable to authenticate request; Inner exception System.Data.SqlClient.SqlException:Cannot open server requested by the login.

Columnstore is not supported in this service tier.
Error SQL72014: .Net SqlClient Data Provider: Msg 40536, Level 16, State 32, Line 5 'COLUMNSTORE' is not supported in this service tier of the database.

Create Symmetric Key not supported for the targeted platform.
Received error SQL70015 (Statement 'CREATE SYMMETRIC KEY' is not supported for the targeted platform) trying to publish a database project to Azure SQL Database v12.

Database Export Error.
Error received while exporting a SQL Azure Database to a BLOB storage account using the new Azure portal GUI. Failed to export the database: AdventureWorksLT. ErrorCode: 400 ErrorMessage: There was an error that occurred during this operation.

Database provisioning failed with exception 18456 Login failed.
Sync Group page throws error message after configuring Azure SQL Data Sync. Database provisioning failed with the exception SqlException ID. Error Code: -2146232060 - SqlError Number:18456 Message: Login failed.

Error 102 Create Failed for Database.
Error message 102 received trying to create a new database using the GUI of SQL Server Management Studio.
 
Error 18456 Severity 14 State 123 Login Failed.
Error received while trying to authenticate to SQL Azure Database. Error: 18456, Severity: 14, State: 123. Login failed for user.

Error 18456 State 1 Azure SQL Managed Instance.
Unable to connect to Azure SQL Managed Instance from SQL Server Management Studio (SSMS). Error 18456 Severity 14 State 1.

Error 25602 storing file of XEvent on Azure Storage.
The target, 'xxxxx.package0.event_file', encountered a configuration error during initialization. Object cannot be added to the event session. The operating system returned error 13: 'The data is invalid.' while creating the file 'https://myazurestorage10.blob.core.windows.net/extendedevent/FileName_0_131786915402130000.xel'. (Microsoft SQL Server, Error: 25602).

Error 19 - Physical connection is not usable.
A transport-level error has occurred when receiving results from the server. (provider: Session Provider, error: 19 - Physical connection is not useable).

Error SQL71562 Procedure has an unresolved reference.
Error SQL71562: Procedure: [dbo].[usp_Admin_SQLJob_GetAll] has an unresolved reference to an object. Either the object does not exist or the reference is ambiguous.
 
Login Failed Windows Azure SQL Database.
Cannot connect to xxxxxx.database.windows.net. Login failed for user 'morillo'. (Microsoft SQL Server, Error: 18456).

Msg 35321 rebuilding Columnstore Index on SQL Azure.
Unable to rebuild columnstore index of a table or use it on a SELECT statement after scaling down the tier of an Azure SQL Database.

Msg 40616 Could not import package.
Unable to move an on-premise database to Azure SQL Database using SSMS and its Deploy Database to SQL Azure Wizard or importing a bacpac from BLOB storage account.

Msg 40636 Cannot use reserved database master.
Msg 40636, Level 16, State 1, Line 1. Cannot change compatibility level master database on SQL Azure Database server.
 
Not a valid login name in this version of SQL Server.
Msg 40616, Level 16, State 1, Line 1. 'sa' is not a valid login name in this version of SQL Server.

Operation completed with provisioning state canceled.
Unable to create an Azure SQL Database. The resource operation completed with terminal provisioning state 'canceled'. The operation timed out and automatically rolled back.

Pause Database Error.
Received error message 'Pause database error' when trying to pause compute resources on Azure SQL Data Warehouse.

Scale database error.
Attempt to scale down an Azure SQL database failed with error 'Scale database error' (MODIFY MAXSIZE failed).

SQL Agent Data Sync cannot be removed.
This agent cannot be removed because one more more databases are still associated with it. Please remove the databases associated with the agent and then try again.

SQL Azure Data Sync Failed Error Code -2146232060.
GetStatus failed with exception:Sync worker failed, checked by GetStatus method. Failure details:SqlException Error Code: -2146232060 - SqlError Number:3952, Message: Snapshot isolation transaction failed accessing database 'SampleDB' because snapshot isolation is not allowed in this database.

Validation errors in the source server.
Microsoft Data Migration Assistant (DMA). There are validation errors in the source server. Please fix the issues and go to the next step.
 
 

Troubleshooting Microsoft SQL Server Migration Assistant.


ORA-12545 Connection failed because target host or object does not exist.
Error received while using SQL Server Migration Assistant (SSMA) 2005 for Oracle.

SQL Server Migration Assistant - Timeout Expired.
Microsoft SQL Server Migration Assistant (SSMA) timed out. The timeout period elapsed prior to completion of the operation or the server is not responding.



 

 

 

.Send mail to webmaster@sqlcoffee.com with questions or comments about this web site.