SQL Server Errors or Failures from Error: 28033 to Error: 28053

Error: 28033, Severity: 10, A new connection was established with the same peer. This connection lost the arbitration and it will be closed. All traffic will be redirected to the newly opened connection. This is an informational message only. No user action is required. State %d.

Error: 28034, Severity: 10, Connection handshake failed. The login ‘%.*ls’ does not have CONNECT permission on the endpoint. State %d.
Error: 28035, Severity: 10, Connection handshake failed. The certificate used by the peer is invalid due to the following reason: %S_MSG. State %d.
Error: 28036, Severity: 10, Connection handshake failed. The certificate used by this endpoint was not found: %S_MSG. Use DBCC CHECKDB in master database to verify the metadata integrity of the endpoints. State %d.
Error: 28037, Severity: 10, Connection handshake failed. Error %d occurred while initializing the private key corresponding to the certificate. The SQL Server errorlog and the Windows event log may contain entries related to this error. State %d.
Error: 28038, Severity: 10, Connection handshake failed. The handshake verification failed. State %d.
Error: 28039, Severity: 10, Connection handshake failed. The receive SSPI packet is not of type of the negotiated package. State %d.

Error: 28040, Severity: 10, A corrupted message has been received. The adjacent error message header is invalid.
Error: 28041, Severity: 16, A corrupted message has been received. The encrypted payload offset is invalid (%d).
Error: 28042, Severity: 16, A corrupted message has been received. The arbitration request header is invalid.
Error: 28043, Severity: 16, A corrupted message has been received. The arbitration response header is invalid.
Error: 28044, Severity: 16, A corrupted message has been received. It is not encrypted and signed using the currently configured endpoint algorithm. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
Error: 28045, Severity: 10, Connection handshake failed. The certificate used by the peer does not match the one in MASTER database with same issuer name and serial number. State %d.

Error: 28046, Severity: 10, %S_MSG Login succeeded for user ‘%.*ls’. Authentication mode: %.*ls. %.*ls
Error: 28047, Severity: 10, %S_MSG login attempt failed with error: ‘%.*ls’. %.*ls
Error: 28048, Severity: 10, %S_MSG login attempt by user ‘%.*ls’ failed with error: ‘%.*ls’. %.*ls
Error: 28050, Severity: 10, The session keys for this conversation could not be created or accessed. The database master key is required for this operation.
Error: 28051, Severity: 10, Could not save a dialog session key. A master key is required in the database to save the session key.
Error: 28052, Severity: 16, Cannot decrypt session key while regenerating master key with FORCE option.
Error: 28053, Severity: 16, Service Broker could not upgrade conversation session keys in database ‘%.*ls’ to encrypted format (Error: %d). The Service Broker in this database was disabled. A master key is required to the database in order to enable the broker.

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.