SQL Server Errors or Failures from Error: 35003 to Error: 35210

SQLServerF1

Error: 35003, Severity: 16, Cannot move node to one of its children

Error: 35004, Severity: 16, Could not find server group
Error: 35005, Severity: 16, An invalid value NULL was passed in for @server_group_id.
Error: 35006, Severity: 16, An invalid value NULL was passed in for @server_id.
Error: 35007, Severity: 16, Could not find shared registered server.
Error: 35008, Severity: 16, Cannot delete system shared server groups.
Error: 35009, Severity: 16, An invalid value NULL was passed in for @server_type.

Error: 35010, Severity: 16, An invalid value %d was passed in for parameter @server_type.
Error: 35011, Severity: 16, The @server_name parameter cannot be a relative name.
Error: 35012, Severity: 16, You cannot add a shared registered server with the same name as the Configuration Server.
Error: 35100, Severity: 16, Error number %d in the THROW statement is outside the valid range. Specify an error number in the valid range of 50000 to 2147483647.
Error: 35201, Severity: 10, A connection timeout has occurred while attempting to establish a connection to availability replica ‘%ls’ with id [%ls]. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint
Error: 35202, Severity: 10, A connection for availability group ‘%ls’ from availability replica ‘%ls’ with id [%ls] to ‘%ls’ with id [%ls] has been successfully established. This is an informational message only. No user action is required.

Error: 35203, Severity: 16, Unable to establish a connection between instance ‘%ls’ with id [%ls] and ‘%ls’ with id [%ls] due to a transport version mismatch.
Error: 35204, Severity: 10, The connection between server instances ‘%ls’ with id [%ls] and ‘%ls’ with id [%ls] has been disabled because the database mirroring endpoint was either disabled or stopped. Restart the endpoint by using the ALTER ENDPOINT Transact-SQL statement with STAT
Error: 35205, Severity: 16, Could not start the AlwaysOn Availability Groups transport manager. This failure probably occurred because a low memory condition existed when the message dispatcher started up. If so, other internal tasks might also have experienced errors. Check the SQL
Error: 35206, Severity: 10, A connection timeout has occurred on a previously established connection to availability replica ‘%ls’ with id [%ls]. Either a networking or a firewall issue exists or the availability replica has transitioned to the resolving role.
Error: 35207, Severity: 16, Connection attempt on availability group id ‘%ls’ from replica id ‘%ls’ to replica id ‘%ls’ failed because of error %d, severity %d, state %d.
Error: 35208, Severity: 16, Availability-group DDL operations are permitted only when you are using the master database. Run the USE MASTER command, and retry your availability-group DDL command.
Error: 35209, Severity: 16, The %ls operation failed for availability replica ‘%.*ls’, because the backup priority value is outside the valid range. The valid range is between %d and %d, inclusive. Set the backup priority to a value within this range, and retry the operation.

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.

 

SQL Server Errors or Failures from Error: 14153 to Error: 14172

SQLServerF1

 

Error: 14153, Severity: 10, Replication-%s: agent %s warning. %s
Error: 14154, Severity: 16, The Distributor parameter must be ‘@heartbeat_interval’.
Error: 14155, Severity: 16, Invalid article ID specified for procedure script generation.
Error: 14156, Severity: 16, The custom stored procedure calling the format for the %s command specified in the article definition does not match the %s format.
Error: 14157, Severity: 10, The subscription created by Subscriber ‘%s’ to publication ‘%s’ has expired and has been dropped.

Error: 14158, Severity: 10, Replication-%s: agent %s: %s.
Error: 14159, Severity: 16, Could not change property ‘%s’ for article ‘%s’ because there is an existing subscription to the article.
Error: 14160, Severity: 10, One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and change the expiration threshold value if necessary.
Error: 14161, Severity: 10, The threshold [%s:%s] for the publication [%s] has been set. Make sure that the logreader and distribution agents are running and can match the latency requirement.

Error: 14162, Severity: 10, One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
Error: 14163, Severity: 10, One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
Error: 14164, Severity: 10, One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
Error: 14165, Severity: 10, One or more subscriptions has exceeded the threshold [%s:%s] for the publication [%s]. Check the status of subscriptions to this publication and adjust the threshold value if necessary.
Error: 14166, Severity: 10, Disable publishing ignored error msg %d, severity %d, state %d: %s.
Error: 14167, Severity: 10, Subscription expiration
Error: 14168, Severity: 10, Transactional replication latency
Error: 14169, Severity: 10, Long merge over dialup connection
Error: 14170, Severity: 10, Long merge over LAN connection
Error: 14171, Severity: 10, Slow merge over LAN connection
Error: 14172, Severity: 10, Slow merge over dialup connection

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.

 

SQL Server Errors or Failures from Error: 8975 to Error: 8994

SQLServerF1

 

Error: 8975, Severity: 10, DBCC cross-rowset check failed for object ‘%.*ls’ (object ID %d) due to internal query error %d, severity %d, state %d. Refer to Books Online for more information on this error.
Error: 8976, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID was not seen in the scan although its parent %S_PGID and previous %S_PGID refer to it. Check any previous errors.
Error: 8977, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Parent node for page %S_PGID was not encountered.

Error: 8978, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID is missing a reference from previous page %S_PGID. Possible chain linkage problem.
Error: 8979, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID is missing references from parent (unknown) and previous (page %S_PGID) nodes. Possible bad root entry in system catalog.
Error: 8980, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Index node page %S_PGID, slot %d refers to child page %S_PGID and previous child %S_PGID, but they were not encountered.
Error: 8981, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The next pointer of %S_PGID refers to page %S_PGID. Neither %S_PGID nor its parent were encountered. Possible bad chain linkage.

Error: 8982, Severity: 16, Table error: Cross object linkage. Page %S_PGID->next in object ID %d, index ID %d, partition ID %I64d, AU ID %I64d (type %.*ls) refers to page %S_PGID in object ID %d, index ID %d, partition ID %I64d, AU ID %I64d (type %.*ls) but is not in the same index
Error: 8983, Severity: 10, File %d. Extents %I64d, used pages %I64d, reserved pages %I64d, mixed extents %I64d, mixed pages %I64d.
Error: 8984, Severity: 16, Table error: object ID %d, index ID %d, partition ID %I64d. A row should be on partition number %d but was found in partition number %d. Possible extra or invalid keys for:
Error: 8985, Severity: 16, Could not locate file ‘%.*ls’ for database ‘%.*ls’ in sys.database_files. The file either does not exist, or was dropped.
Error: 8986, Severity: 16, Too many errors found (%d) for object ID %d. To see all error messages rerun the statement using “WITH ALL_ERRORMSGS”.
Error: 8987, Severity: 16, No help available for DBCC statement ‘%.*ls’.
Error: 8988, Severity: 16, Row (%d:%d:%d) identified by (%ls).
Error: 8989, Severity: 10, %.*ls found %d allocation errors and %d consistency errors in database ‘%ls’.
Error: 8990, Severity: 10, %.*ls found %d allocation errors and %d consistency errors in table ‘%ls’ (object ID %d).
Error: 8991, Severity: 16, 0x%p to 0x%p is not a valid address range.
Error: 8992, Severity: 16, Check Catalog Msg %d, State %d: %.*ls
Error: 8993, Severity: 16, Object ID %d, forwarding row page %S_PGID, slot %d points to page %S_PGID, slot %d. Did not encounter forwarded row. Possible allocation error.
Error: 8994, Severity: 16, Object ID %d, forwarded row page %S_PGID, slot %d should be pointed to by forwarding row page %S_PGID, slot %d. Did not encounter forwarding row. Possible allocation error.

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.

 

SQL Server Errors or Failures Error: 924 to Error: 947

SQLServerF1

 

Error: 924, Severity: 14,
Database ‘%.*ls’ is already open and can only have one user at a time.

Error: 925, Severity: 19,
Maximum number of databases used for each query has been exceeded. The maximum allowed is %d.

Error: 926, Severity: 14,
Database ‘%.*ls’ cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.

Error: 927, Severity: 14,
Database ‘%.*ls’ cannot be opened. It is in the middle of a restore.

Error: 928, Severity: 20,
During upgrade, database raised exception %d, severity %d, state %d, address %p. Use the exception number to determine the cause.

Error: 929, Severity: 20,
Unable to close a database that is not currently open. The application should reconnect and try again. If this action does not correct the problem, contact your primary support provider.

Error: 930, Severity: 21,
Attempting to reference recovery unit %d in database ‘%ls’ which does not exist. Contact Technical Support.

Error: 932, Severity: 21,
SQL Server cannot load database ‘%.*ls’ because change tracking is enabled. The currently installed edition of SQL Server does not support change tracking. Either disable change tracking in the database by using a supported edition of SQL Server, or upgra

Error: 933, Severity: 21,
Database ‘%.*ls’ cannot be started because some of the database functionality is not available in the current edition of SQL Server.

Error: 934, Severity: 21,
SQL Server cannot load database ‘%.*ls’ because Change Data Capture is enabled. The currently installed edition of SQL Server does not support Change Data Capture. Either disable Change Data Capture in the database by using a supported edition of SQL Serv

Error: 935, Severity: 21,
The script level for ‘%.*ls’ in database ‘%.*ls’ cannot be downgraded from %d to %d, which is supported by this server. This usually implies that a future database was attached and the downgrade path is not supported by the current installation. Install

Error: 936, Severity: 16,
Database ‘%.*ls’ can not be used in this edition of SQL Server.

Error: 937, Severity: 21,
Database ‘%.*ls’ cannot be upgraded because ‘%.*ls’ functionality is not available in the current edition of SQL Server.

Error: 941, Severity: 16,
Database ‘%.*ls’ cannot be opened because it is not started. Retry when the database is started.

Error: 942, Severity: 14,
Database ‘%.*ls’ cannot be opened because it is offline.

Error: 943, Severity: 14,
Database ‘%.*ls’ cannot be opened because its version (%d) is later than the current server version (%d).

Error: 944, Severity: 10,
Converting database ‘%.*ls’ from version %d to the current version %d.

Error: 945, Severity: 16,
Database ‘%.*ls’ cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.

Error: 946, Severity: 14,
Cannot open database ‘%.*ls’ version %d. Upgrade the database to the latest version.

Error: 947, Severity: 16,
Error while closing database ‘%.*ls’. Check for previous additional errors and retry the operation.

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.