SQL Server Errors or Failures from Error: 11260 to Error: 11279

SQLServerF1

You may receive various errors in SQL Server while working. Below are some of the SQL Server Errors from Error: 11260 to Error: 11279

Error: 11260, Severity: 16,
A corrupted message has been received. The certificate issuer name size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11261, Severity: 16,
A corrupted message has been received. The destination certificate serial number size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64

Error: 11262, Severity: 16,
A corrupted message has been received. The destination certificate issuer name size is %d, however it must be no greater than %d bytes in length. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11263, Severity: 16,
A corrupted message has been received. The service pair security header size is %d, however it must be between %d and %d bytes. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11264, Severity: 16,
A corrupted message has been received. The key exchange key size is %d, however it must be between %d and %d bytes. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11265, Severity: 16,
A corrupted message has been received. The key exchange key ID is invalid. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11266, Severity: 16,
A corrupted message has been received. The encrypted session key size is %d, however it must be %d bytes. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11267, Severity: 16,
A corrupted message has been received. The session key ID size is %d, however it must be %d bytes. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11268, Severity: 16,
A corrupted message has been received. The salt size is %d, however it must be %d bytes. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11269, Severity: 16,
A corrupted message has been received. A UNICODE string is not two byte aligned within the message. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11270, Severity: 16,
A corrupted message has been received. A UNICODE string is greater than the maximum allowed size of %d bytes. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11271, Severity: 16,
A corrupted message has been received. The conversation ID must not be NULL. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11272, Severity: 16,
A corrupted message has been received. The message ID must not be NULL.

Error: 11273, Severity: 16,
A corrupted message has been received. The message body is not properly padded for encryption. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11274, Severity: 16,
A corrupted message has been received. A sequence number is larger than allowed. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11275, Severity: 16,
A corrupted message has been received. The End of Conversation and Error flags are both set. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11276, Severity: 16,
A corrupted message has been received. The End of Conversation flag has been set on an unsequenced message. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11277, Severity: 16,
A corrupted message has been received. The End of Conversation and Error flags may not be set in the first sequenced message. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11278, Severity: 16,
A corrupted message has been received. The message type is missing for this message. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

Error: 11279, Severity: 16,
A corrupted message has been received. The message type must not be set in this message. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

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 *