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: 14680 to Error: 14699

SQLServerF1

You may receive various errors in SQL Server while working. Below are some of the SQL Server Errors from Error: 14680 to Error: 14699

Error: 14680, Severity: 16,
Management Data Warehouse database can only be installed on an instance of SQL Server 2008 or higher.

Error: 14681, Severity: 16,
Cannot perform this procedure when the collector is disabled. Enable the collector and then try again.

Error: 14682, Severity: 16,
The state of the collection set has changed, but it will not start or stop until the collector is enabled.

Error: 14683, Severity: 16,
A collection set in cached mode requires a schedule.

Error: 14684, Severity: 16,
Caught error#: %d, Level: %d, State: %d, in Procedure: %s, Line: %d, with Message: %s

Error: 14685, Severity: 16,
Collection set: ‘%s’ does not contain any collection items, so starting the collection set will have no effect.

Error: 14686, Severity: 16,
The MDWInstance and MDWDatabase parameters of the configuration store cannot be null.

Error: 14687, Severity: 16,
Invalid value (%d) of the @cache_window parameter. Allowable values are: -1 (cache all upload data from previous upload failures), 0 (cache no upload data), N (cache data from N previous upload failures, where N >= 1)

Error: 14688, Severity: 16,
A collection set cannot start when SQL Server Agent is stopped. Start SQL Server Agent.

Error: 14689, Severity: 16,
A collection set cannot start if the management data warehouse is not configured. Run the instmdw.sql script to create and configure the management data warehouse.

Error: 14690, Severity: 16,
Cannot perform this procedure when the collector is enabled. Disable the collector and then try again.

Error: 14691, Severity: 16,
The status of the collector cannot be null. This may indicate an internal corruption in the collector configuration data.

Error: 14692, Severity: 16,
Insufficient priveleges to start collection set: ‘%s’. Only a member of the ‘sysadmin’ fixed server role can start a collection set without a SQL Server Agent proxy. Attach a SQL Server Agent proxy to the collection set before retrying.

Error: 14693, Severity: 16,
A collection set cannot start without a schedule. Specify a schedule for the collection set.

Error: 14694, Severity: 16,
Cannot upload data on-demand for the collection set ‘%s’ in non-cached mode.

Error: 14695, Severity: 16,
Cannot collect data on-demand for the collection set ‘%s’ in cached mode.

Error: 14696, Severity: 16,
Cannot update or delete a system collection set, or add new collection items to it.

Error: 14697, Severity: 16,
Unable to convert showplan to XML. Error #%d on Line %d: %s

Error: 14698, Severity: 10,
PowerShell Subsystem

Error: 14699, Severity: 16,
Data Collector cannot be enabled when SQL Server Agent is stopped. Start SQL Server Agent.

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: 11303 to Error: 11407

SQLServerF1

You may receive various errors in SQL Server while working. Below are some of the SQL Server Errors from Error: 11303 to Error: 11407

Error: 11303, Severity: 10,
Error releasing reserved log space: %ls space %I64d, code %d, state %d.

Error: 11304, Severity: 10,
Failed to record outcome of a local two-phase commit transaction. Taking database offline.

Error: 11306, Severity: 16,
Forward progress on this transaction is disallowed. Transaction has been rolled back.

Error: 11313, Severity: 16,
This operation must be executed within a parallel nested transaction.

Error: 11314, Severity: 16,
The stored procedure %.*ls must be executed within a user transaction.

Error: 11315, Severity: 16,
The isolation level specified for the PNT child transaction does not match the current isolation level for the parent.

Error: 11316, Severity: 16,
%ls statement cannot be used inside a parallel nested transaction.

Error: 11317, Severity: 16,
Parallel plan with updates is not supported inside a parallel nested transaction.

Error: 11318, Severity: 16,
The stored procedure ‘%.*ls’ cannot be executed through MARS connection.

Error: 11319, Severity: 16,
Bound sessions and user parallel nested transactions cannot be used in the same transaction.

Error: 11320, Severity: 16,
Cannot create a User Parallel Nested Transaction, the maximum number of parallel nested transactions is reached.

Error: 11321, Severity: 16,
This operation cannot be executed within an active transaction.

Error: 11400, Severity: 16,
ALTR TABLE SWITCH statement failed. Index ‘%.*ls’ on indexed view ‘%.*ls’ uses partition function ‘%.*ls’, but table ‘%.*ls’ uses non-equivalent partition function ‘%.*ls’. Index on indexed view ‘%.*ls’ and table ‘%.*ls’ must use an equivalent partition

Error: 11401, Severity: 16,
ALTR TABLE SWITCH statement failed. Table ‘%.*ls’ is %S_MSG, but index ‘%.*ls’ on indexed view ‘%.*ls’ is %S_MSG.

Error: 11402, Severity: 16,
ALTR TABLE SWITCH statement failed. Target table ‘%.*ls’ is referenced by %d indexed view(s), but source table ‘%.*ls’ is only referenced by %d indexed view(s). Every indexed view on the target table must have at least one matching indexed view on the so

Error: 11403, Severity: 16,
ALTR TABLE SWITCH statement failed. Indexed view ‘%.*ls’ is not aligned with table ‘%.*ls’. The partitioning column ‘%.*ls’ from the indexed view calculates its value from one or more columns or an expression, rather than directly selecting from the tabl

Error: 11404, Severity: 16,
ALTR TABLE SWITCH statement failed. Target table ‘%.*ls’ is referenced by %d indexed view(s), but source table ‘%.*ls’ is only referenced by %d matching indexed view(s). Every indexed view on the target table must have at least one matching indexed view

Error: 11405, Severity: 16,
ALTR TABLE SWITCH statement failed. Table ‘%.*ls’ is not aligned with the index ‘%.*ls’ on indexed view ‘%.*ls’. The table is partitioned on column ‘%.*ls’, but the index on the indexed view is partitioned on column ‘%.*ls’, which is selected from a diff

Error: 11406, Severity: 16,
ALTR TABLE SWITCH statement failed. Source and target partitions have different values for the DATA_COMPRESSION option.

Error: 11407, Severity: 16,
Vardecimal storage format can not be enabled for ‘%.*ls’. Only Enterprise edition of SQL Server supports vardecimal.

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: 9539 to Error: 9622

SQLServerF1

 

Error: 9539, Severity: 16, Selective XML Index feature is not supported for the current database version
Error: 9601, Severity: 16, Cannot relate to %S_MSG %.*ls because it is %S_MSG.
Error: 9602, Severity: 16, Failed to start a system task with error code %d, state %d.
Error: 9605, Severity: 10, Conversation Priorities analyzed: %d.
Error: 9606, Severity: 16, The conversation priority with ID %d has been dropped.
Error: 9607, Severity: 16, The conversation priority with ID %d is referencing the missing service with ID %d.

Error: 9608, Severity: 16, The conversation priority with ID %d is referencing the missing service contract with ID %d.
Error: 9609, Severity: 16, The %S_MSG name ‘%.*ls’ contains more than the maximum number of prefixes. The maximum is %d.
Error: 9610, Severity: 16, The service ‘%.*ls’ in the FROM SERVICE clause must match the service ‘%.*ls’ referenced by %s = ‘%.*ls’.
Error: 9611, Severity: 16, Cannot find the specified user ‘%.*ls’.
Error: 9613, Severity: 16, The queue ‘%.*ls’ cannot be activated because the activation user is not specified.
Error: 9614, Severity: 16, The queue ‘%.*ls’ cannot be activated because the activation stored procedure is either not specified or is invalid.

Error: 9615, Severity: 16, A message of type ‘%.*ls’ failed XML validation on the target service. %.*ls This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
Error: 9616, Severity: 16, A message of type ‘%.*ls’ was received and failed XML validation. %.*ls This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
Error: 9617, Severity: 16, The service queue “%.*ls” is currently disabled.
Error: 9618, Severity: 16, The message cannot be sent because the service queue ‘%.*ls’ associated with the dialog is currently disabled and retention is on.
Error: 9619, Severity: 16, Failed to create remote service binding ‘%.*ls’. A remote service binding for service ‘%.*ls’ already exists.
Error: 9620, Severity: 16, The activation stored procedure ‘%.*ls’ is invalid. Functions are not allowed.
Error: 9621, Severity: 16, An error occurred while processing a message in the Service Broker and Database Mirroring transport: error %i, state %i.
Error: 9622, Severity: 16, The crypto provider context is not initialized.

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.