SQL Server Errors or Failures from Error: 11240 to Error: 11259
You may receive various errors in SQL Server while working. Below are some of the SQL Server Errors from Error: 11240 to Error: 11259
Error: 11240, Severity: 16, A corrupted message has been received. The binary message preamble is malformed.
Error: 11241, Severity: 16, A corrupted message has been received. The conversation security version number is not %d.%d.
Error: 11242, Severity: 16, A corrupted message has been received. The maximum number of public variable data elements (%d) has been exceeded. Public variable data elements found: %d.
Error: 11243, Severity: 16, A corrupted message has been received. The public variable data element (%d) has been duplicated in this message.
Error: 11244, Severity: 16, A corrupted message has been received. The handshake validation header is malformed.
Error: 11245, Severity: 16, A corrupted message has been received. The maximum number of private variable data elements (%d) has been exceeded. Private variable data elements found: %d.
Error: 11246, Severity: 16, A corrupted message has been received. The private variable data element (%d) has been duplicated in this message.
Error: 11247, Severity: 16, A corrupted message has been received. The login negotiate header is invalid.
Error: 11248, Severity: 16, A corrupted message has been received. The SSPI login header is invalid.
Error: 11249, Severity: 16, A corrupted message has been received. The pre-master-secret is invalid.
Error: 11250, Severity: 16, A corrupted message has been received. The security certificate key fields must both be present or both be absent. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
Error: 11251, Severity: 16, A corrupted message has been received. The service pair security header source certificate and the signature must both be present or both be absent. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I6
Error: 11252, Severity: 16, A corrupted message has been received. The destination certificate serial number is missing. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
Error: 11253, Severity: 16, A corrupted message has been received. The service pair security header destination certificate, the key exchange key, the key exchange key ID, and the session key must all be present or all be absent. This occurred in the message with Conversation ID ‘%.
Error: 11254, Severity: 16, A corrupted message has been received. The session key ID is missing. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
Error: 11255, Severity: 16, A corrupted message has been received. The encryption flag is set, however the message body, MIC or salt is missing. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
Error: 11256, Severity: 16, A corrupted message has been received. The MIC is present, however the message body or encryption flag is missing. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
Error: 11257, Severity: 16, A corrupted message has been received. The MIC and session key ID are in an invalid state. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.
Error: 11258, Severity: 16, A corrupted message has been received. The MIC 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: 11259, Severity: 16, A corrupted message has been received. The 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: %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.