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.

 

Leave a Reply

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