SQL Server Errors or Failures from Error: 28054 to Error: 28074

SQLServerF1

Error: 28054, Severity: 16, Service Broker needs to access the master key in the database ‘%.*ls’. Error code:%d. The master key has to exist and the service master key encryption is required.

Error: 28055, Severity: 16, The certificate ‘%.*ls’ is not valid for endpoint authentication. The certificate must have a private key encrypted with the database master key and current UTC date has to be between the certificate start date and the certificate expiration date.
Error: 28056, Severity: 16, This message could not be delivered because the user with ID %i in database ID %i does not have control permission on the service. Service name: ‘%.*ls’.
Error: 28057, Severity: 10, Service Broker in database ‘%.*ls’ has a pending conversation upgrade operation. A database master key in the database is required for this operation to complete.
Error: 28058, Severity: 16, Service Broker could not upgrade this conversation during a database upgrade operation.

Error: 28059, Severity: 16, Connection handshake failed. The received premaster secret of size %d does not have the expected size of %d. State %d.
Error: 28060, Severity: 16, The AES encryption algorithm is only supported on Windows XP, Windows Server 2003 or later versions.
Error: 28061, Severity: 16, A corrupted message has been received. The adjacent message integrity check signature could not be validated.
Error: 28062, Severity: 16, A corrupted message has been received. The signed dialog message header is invalid.
Error: 28063, Severity: 16, A corrupted message has been received. A required variable data field is not present: %S_MSG. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
Error: 28064, Severity: 16, A corrupted message has been received. A string variable data field is not a valid UNICODE string: %S_MSG. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 28065, Severity: 16, A corrupted message has been received. The unsigned dialog message header is invalid. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
Error: 28066, Severity: 16, A corrupted message has been received. The security dialog message header is invalid. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
Error: 28067, Severity: 16, A corrupted message has been received. The encrypted offset of the envelope does not match the payload encrypted offset. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
Error: 28068, Severity: 16, A corrupted message has been received. The envelope payload is bigger than the message. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
Error: 28069, Severity: 16, Unexpected session key when encrypting a dialog message.
Error: 28070, Severity: 10, Connection handshake failed. The received SSPI message Confirm status is unexpected. State %d.
Error: 28072, Severity: 16, A serious error occurred in the Service Broker message transmitter (operation %i): Error: %i, State: %i. Message transmission will resume in %i seconds.
Error: 28073, Severity: 16, An out of memory condition has occurred in the Service Broker message transmitter (operation %i). Message transmission will resume in %i seconds.
Error: 28074, Severity: 16, Service Broker could not upgrade conversation with conversation_handle ‘%ls’. Use END CONVERSATION … WITH CLEANUP to delete this conversation, then try again to enable the broker. Use ALTER DATABASE … SET ERROR_BROKER to error all conversations in thi

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 *