SQL Server Errors or Failures from Error: 11109 to Error: 11219

SQLServerF1

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

Error: 11109, Severity: 16,
The provider does not support an index scan on this data source.

Error: 11201, Severity: 16,
This message could not be delivered because the FROM service name is missing. The message origin is: ‘%ls’.

Error: 11202, Severity: 16,
This message has been dropped because the FROM service name exceeds the maximum size of %d bytes. Service name: “%.*ls”. Message origin: “%ls”.

Error: 11203, Severity: 16,
This message has been dropped because the FROM broker instance is missing. The message origin is ‘%ls’.

Error: 11204, Severity: 16,
This message has been dropped because the FROM broker instance exceeds the maximum size of %d bytes. Broker instance: “%.*ls”. Message origin: “%ls”.

Error: 11205, Severity: 16,
This message has been dropped because the TO service name is missing. The message origin is “%ls”.

Error: 11206, Severity: 16,
This message has been dropped because the TO service name exceeds the maximum size of %d bytes. Service name: “%.*ls”. Message origin: “%ls”.

Error: 11207, Severity: 16,
This message has been dropped because the service contract name is missing. The message origin is “%ls”.

Error: 11208, Severity: 16,
This message has been dropped because the service contract name exceeds the maximum size of %d bytes. Contract name “%.*ls”. Message origin: “%ls”.

Error: 11209, Severity: 16,
This message could not be delivered because the conversation ID could not be associated with an active conversation. The message origin is: ‘%ls’.

Error: 11210, Severity: 16,
This message has been dropped because the TO service could not be found. Service name: “%.*ls”. Message origin: “%ls”.

Error: 11211, Severity: 16,
This message has been dropped because the user does not have permission to access the target database. Database ID: %d. Message origin: "%ls".

Error: 11212, Severity: 16,
This message could not be delivered because the conversation endpoint has already been closed.

Error: 11213, Severity: 16,
This message could not be delivered because this is not the first message in the conversation.

Error: 11214, Severity: 16,
This message could not be delivered because the ‘%.*ls’ contract could not be found or the service does not accept conversations for the contract.

Error: 11215, Severity: 16,
This message could not be delivered because the user with ID %i in database ID %i does not have permission to send to the service. Service name: ‘%.*ls’.

Error: 11216, Severity: 16,
This message could not be delivered because there is already another task processing this message.

Error: 11217, Severity: 16,
This message could not be delivered because it is out of sequence with respect to the conversation. Conversation receive sequence number: %I64d, Message sequence number: %I64d.

Error: 11218, Severity: 16,
This message could not be delivered because it is a duplicate.

Error: 11219, Severity: 16,
This message could not be delivered because the destination queue has been disabled. Queue ID: %d.

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 *