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.

 

Leave a Reply

Your email address will not be published. Required fields are marked *