SQL Server Errors or Failures from Error: 9643 to Error: 9662

SQLServerF1

 

Error: 9643, Severity: 16, An error occurred in the Service Broker/Database Mirroring transport manager: Error: %i, State: %i.
Error: 9644, Severity: 16, An error occurred in the service broker message dispatcher. Error: %i, State: %i.
Error: 9645, Severity: 16, An error occurred in the service broker manager, Error: %i, State: %i.

Error: 9646, Severity: 16, An error occurred in the timer event cache. Error %i, state %i.
Error: 9647, Severity: 16, Received a malformed message from the network. Unable to retrieve a broker message attribute from a message destined for database ID %d. This may indicate a network problem or that another application connected to the Service Broker endpoint.
Error: 9648, Severity: 20, The queue ‘%.*ls’ has been enabled for activation, but the MAX_QUEUE_READERS is zero. No procedures will be activated. Consider increasing the number of MAX_QUEUE_READERS.
Error: 9649, Severity: 16, A security (SSPI) error occurred when connecting to another service broker: ‘%.*ls’. Check the Windows Event Log for more information.

Error: 9650, Severity: 16, A system cryptographic call failed during a Service Broker or Database Mirroring operation: system error ‘%ls’.
Error: 9651, Severity: 16, The system call failed during a Service Broker or Database Mirroring operation. System error: ‘%ls’.
Error: 9652, Severity: 16, Service Broker failed to retrieve the session key for encrypting a message.
Error: 9653, Severity: 16, The signature of activation stored procedure ‘%.*ls’ is invalid. Parameters are not allowed.
Error: 9654, Severity: 16, Attempting to use database and it doesn’t exist.
Error: 9655, Severity: 16, The transmission queue table structure in database is inconsistent. Possible database corruption.
Error: 9656, Severity: 16, An error occurred in the service broker multicast manager, Error: %i, State: %i.
Error: 9657, Severity: 23, The structure of the Service Broker transmission work-table in tempdb is incorrect or corrupt. This indicates possible database corruption or hardware problems. Check the SQL Server error log and the Windows event logs for information on possible hardware
Error: 9658, Severity: 16, Cannot access the transmission queue table in database.
Error: 9659, Severity: 16, The %s of route ‘%.*ls’ cannot be empty.
Error: 9660, Severity: 16, The %s of route ‘%.*ls’ must be less than %d characters long.
Error: 9661, Severity: 16, The SERVICE_NAME and BROKER_INSTANCE of route “%.*ls” must be specified when using mirroring.
Error: 9662, Severity: 16, Cannot specify BROKER_INSTANCE without SERVICE_NAME in route “%.*ls”.

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 from Error: 8391 to Error: 8413

SQLServerF1

 

Error: 8391, Severity: 10, The usage of 2-part names in DROP INDEX is deprecated. New-style syntax DROP INDEX ON { | }
Error: 8393, Severity: 10, The ability to not specify a column name when the datatype is timestamp will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.
Error: 8394, Severity: 10, Usage of deprecated index option syntax. The deprecated relational index option syntax structure will be removed in a future version of SQL Server. Avoid using this syntax structure in new development work, and plan to modify applications that currently u

Error: 8396, Severity: 10, %ls will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it. Use %ls instead.
Error: 8397, Severity: 10, The TEXT, NTEXT, and IMAGE data types will be removed in a future version of SQL Server. Avoid using them in new development work, and plan to modify applications that currently use them. Use the varchar(max), nvarchar(max), and varbinary(max) data types
Error: 8398, Severity: 10, The use of more than two-part column names will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.
Error: 8399, Severity: 10, %ls will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.

Error: 8401, Severity: 16, This message could not be delivered because the target user with ID %i in database ID %i does not have permission to receive from the queue ‘%.*ls’.
Error: 8402, Severity: 16, The data type of the ‘%S_MSG’ in the ‘%S_MSG’ statement must be %s. The %s data type is not allowed.
Error: 8403, Severity: 16, The message type ‘%.*ls’ is specified more than once. Remove the duplicate message type.
Error: 8404, Severity: 16, The service contract ‘%.*ls’ is specified more than once. Remove the duplicate service contract.
Error: 8405, Severity: 16, An error occurred in the service broker queue rollback handler, while trying to disable a queue. Database ID: %d, Queue ID: %d, Error: %i, State: %i.
Error: 8406, Severity: 16, The dialog lifetime can not be NULL. Specify a valid dialog lifetime value from %d to %d.
Error: 8407, Severity: 16, Received a message that contains invalid header fields. This may indicate a network problem or that another application is connected to the Service Broker endpoint.
Error: 8408, Severity: 16, Target service ‘%.*ls’ does not support contract ‘%.*ls’.
Error: 8409, Severity: 16, This message could not be delivered because the targeted service does not support the service contract. Targeted service: ‘%.*ls’, service contract: ‘%.*ls’.
Error: 8410, Severity: 16, The conversation timer cannot be set beyond the conversation’s lifetime.
Error: 8411, Severity: 16, The dialog lifetime value of %d is outside the allowable range of %d to %d. Specify a valid dialog lifetime value.
Error: 8412, Severity: 16, The syntax of the service name ‘%.*ls’ is invalid.
Error: 8413, Severity: 16, The syntax of the broker instance ‘%.*ls’ is invalid. The specified broker instance is too long, the maximum size is 256 bytes.

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.