SQL Server Errors or Failures from Error: 37003 to Error: 40009

SQLServerF1

Error: 37003, Severity: 16, This operation is not allowed because a utility control point already exists on this instance of SQL Server.

Error: 37004, Severity: 16, The specified instance of SQL Server cannot be used as a utility control point because the feature is not enabled in SQL Server ‘%s’.
Error: 37005, Severity: 16, The specified instance of SQL Server cannot be managed by a utility control point because the feature is not enabled in SQL Server ‘%s’.

Error: 37006, Severity: 16, Cannot perform the operation because the specified instance of SQL Server is not enrolled in a SQL Server utility.
Error: 37007, Severity: 16, An error occurred during upload to the SQL Server utility control point.
Error: 37008, Severity: 16, The operation cannot continue. To remove the SQL Server utility control point, the user must be a member of the sysadmin role.
Error: 37009, Severity: 16, The operation cannot continue. The specified instance of SQL Server is not a SQL Server utility control point.

Error: 37010, Severity: 16, The operation cannot continue. The SQL Server utility control point has managed instances of SQL Server enrolled.
Error: 38001, Severity: 16, Cannot find the file id %d in the database ‘%s’.
Error: 38002, Severity: 16, Only users having %s permission can execute this stored procedure.
Error: 40000, Severity: 16, Replicated tables support only local (non-DTC) two-phase commit involving the master database.
Error: 40001, Severity: 16, Secondary kill was initiated during commit.
Error: 40002, Severity: 16, Replicated row is not found.
Error: 40003, Severity: 16, Unexpected operation in replicated message.
Error: 40004, Severity: 16, Column count does not match.
Error: 40005, Severity: 16, Duplicated transaction id.
Error: 40006, Severity: 16, Unknown transaction id.
Error: 40007, Severity: 16, Invalid nesting level.
Error: 40008, Severity: 16, Replication target database is not found.
Error: 40009, Severity: 16, Transaction state locally does not match the expected state.

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 *