SQL Server Errors or Failures from Error: 28075 to Error: 28101

SQLServerF1

Error: 28075, Severity: 10, The broker in the sender’s database is in single user mode. Messages cannot be delivered while in single user mode.

Error: 28076, Severity: 10, Could not query the FIPS compliance mode flag from registry. Error %ls.
Error: 28077, Severity: 10, %S_MSG endpoint is running in FIPS compliance mode. This is an informational message only. No user action is required.
Error: 28078, Severity: 10, The RC4 encryption algorithm is not supported when running in FIPS compliance mode.
Error: 28079, Severity: 10, Connection handshake failed. The received SSPI packet is not of the expected direction. State %d.
Error: 28080, Severity: 10, Connection handshake failed. The %S_MSG endpoint is not configured. State %d.

Error: 28081, Severity: 10, Connection handshake failed. An unexpected status %d was returned when trying to send a handshake message. State %d.
Error: 28082, Severity: 10, Connection handshake failed. An unexpected internal failure occurred when trying to marshal a message. State %d.
Error: 28083, Severity: 16, The database principal ‘%.*ls’ cannot be used in a remote service binding because it cannot own certificates. Remote service bindings cannot be associated with 1) roles, 2) groups or 3) principals mapped to certificates or asymmetric keys.
Error: 28084, Severity: 10, An error occurred in Service Broker internal activation while trying to scan the user queue ‘%ls’ for its status. Error: %i, State: %i. %.*ls This is an informational message only. No user action is required.
Error: 28085, Severity: 16, The activated task was ended because the associated queue was dropped.

Error: 28086, Severity: 16, The activated task was ended because either the queue or activation was disabled.
Error: 28087, Severity: 16, The activated task was aborted because the invoked stored procedure ‘%ls’ did not execute RECEIVE.
Error: 28088, Severity: 16, The activated task was aborted due to an error (Error: %i, State %i). Check ERRORLOG or the previous “Broker:Activation” trace event for possible output from the activation stored procedure.
Error: 28089, Severity: 16, The database principal ‘%.*ls’ cannot be used in a remote service binding because it cannot own certificates. This is a special user for backward compatibility with implicitly connected user schemas.
Error: 28090, Severity: 16, An error occurred while deleting sent messages from the transmission queue, Error: %i, State: %i. Verify that no other operation is locking the transmission queue, and that the database is available.
Error: 28091, Severity: 10, Starting endpoint for %S_MSG with no authentication is not supported.
Error: 28098, Severity: 10, A previously existing connection with the same peer was found after DNS lookup. This connection will be closed. All traffic will be redirected to the previously existing connection. This is an informational message only. No user action is required. State
Error: 28099, Severity: 10, During the database upgrade process on database ‘%.*ls’, a user object ‘%S_MSG’ named ‘%.*ls’ was found to already exist. That object is now reserved by the system in this version of SQL Server. Because it already exists in the database, the upgrade proce
Error: 28101, Severity: 16, User ‘%.*ls\%.*ls’ does not have permission to debug the requested client 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: 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: 9623 to Error: 9642

SQLServerF1

 

Error: 9623, Severity: 16, The key passed in for this operation is in the wrong state.
Error: 9624, Severity: 16, The key size is unacceptable for this key object.
Error: 9625, Severity: 16, The key buffer size is inconsistent with the key modulus size.
Error: 9626, Severity: 16, An internal Service Broker error occurred: an object is in the wrong state for this operation. This error indicates a serious problem with SQL Server. Check the SQL Server error log and the Windows event logs for information pointing to possible hardware
Error: 9627, Severity: 16, The hash buffer size is not correct for initializing the hash object.

Error: 9628, Severity: 16, The encryption/decryption data buffer size is not 8 byte aligned.
Error: 9629, Severity: 16, The decrypted signature size is wrong.
Error: 9630, Severity: 16, The signature did not verify the internal hash.
Error: 9631, Severity: 16, The salt size is unacceptable for this key object.
Error: 9632, Severity: 16, The salt buffer size is too small.
Error: 9633, Severity: 16, The passed in name is too long.
Error: 9634, Severity: 16, Service Broker was unable to allocate memory for cryptographic operations. This message is a symptom of another problem. Check the SQL Server error log for additional messages, and address the underlying problem.

Error: 9635, Severity: 16, The certificate is not valid at this point in time.
Error: 9636, Severity: 16, The requested object was not found.
Error: 9637, Severity: 16, The passed in serialized object is incorrectly encoded.
Error: 9638, Severity: 16, The cer or pvk file size is too large.
Error: 9639, Severity: 16, A password was supplied and the pvk file is not encrypted.
Error: 9640, Severity: 16, The operation encountered an OS error.
Error: 9641, Severity: 16, A cryptographic operation failed. This error indicates a serious problem with SQL Server. Check the SQL Server error log and the Windows event logs for further information.
Error: 9642, Severity: 16, An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: %i, State: %i. (Near endpoint role: %S_MSG, far endpoint address: ‘%.*hs’)

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.