SQL Server Errors or Failures from Error: 11220 to Error: 11239

SQLServerF1

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

Error: 11220, Severity: 16,
This message could not be delivered because the TO broker instance is missing.

Error: 11221, Severity: 16,
This message could not be delivered because there is an inconsistency in the message header.

Error: 11222, Severity: 16,
This message could not be delivered because the TO service name in the message does not match the name in the conversation endpoint. Message TO Service Name: ‘%.*ls’. Conversation Endpoint TO Service Name: ‘%.*ls’.

Error: 11223, Severity: 16,
This message could not be delivered because the service contract name in the message does not match the name in the conversation endpoint. Message service contract name: ‘%.*ls’. Conversation endpoint service contract name: ‘%.*ls’.

Error: 11224, Severity: 16,
This message could not be delivered because another instance of this service program has already started conversing with this endpoint.

Error: 11225, Severity: 16,
This message could not be delivered because the message type name could not be found. Message type name: ‘%.*ls’.

Error: 11226, Severity: 16,
This message could not be delivered because the message type is not part of the service contract. Message type name: ‘%.*ls’. Service contract name: ‘%.*ls’.

Error: 11227, Severity: 16,
This message could not be delivered because the initiator service has sent a message with a message type that can only be sent by the target. Message type name: ‘%.*ls’. Service contract name: ‘%.*ls’.

Error: 11228, Severity: 16,
This message could not be delivered because the target service has sent a message with a message type that can only be sent by the initiator. Message type name: ‘%.*ls’. Service contract name: ‘%.*ls’.

Error: 11229, Severity: 16,
This message could not be delivered because the security context could not be retrieved.

Error: 11230, Severity: 16,
This message could not be delivered because the message could not be decrypted and validated.

Error: 11231, Severity: 16,
This message could not be delivered because the conversation endpoint is not secured, however the message is secured.

Error: 11232, Severity: 16,
This message could not be delivered because the conversation endpoint is secured, however the message is not secured.

Error: 11233, Severity: 16,
This message has been dropped because the session key of the conversation endpoint does not match that of the message.

Error: 11234, Severity: 16,
This message could not be delivered because an internal error was encountered while processing it. Error code %d, state %d: %.*ls.

Error: 11235, Severity: 16,
Received a malformed message. The binary message class (%d:%d) is not defined. This may indicate network problems or that another application is connected to the Service Broker endpoint.

Error: 11236, Severity: 16,
A corrupted message has been received. The binary header size of %d is expected, however the header size received was %d.

Error: 11237, Severity: 16,
A %S_MSG message could not be processed due to insufficient memory. The message was dropped.

Error: 11238, Severity: 16,
A corrupted message has been received. The private variable data segment is malformed.

Error: 11239, Severity: 16,
A corrupted message has been received. The private variable data segment extends beyond the length of the message.

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 *