SQL Server Errors or Failures from Error: 9708 to Error: 9730

SQLServerF1

 

Error: 9708, Severity: 16, The messages in the queue with ID %d are referencing the invalid conversation group ‘%ls’.
Error: 9709, Severity: 16, The messages in the queue with ID %d are referencing the invalid message type with ID %d.
Error: 9710, Severity: 16, The conversation endpoint with ID ‘%ls’ and is_initiator: %d is referencing the invalid conversation group ‘%ls’.
Error: 9711, Severity: 16, The transmission queue is referencing the invalid conversation ID ‘%ls’.
Error: 9712, Severity: 16, The remote service binding with ID %d is referencing the invalid service contract with ID %d.

Error: 9713, Severity: 16, The message type with ID %d is referencing the invalid XML schema collection ID %d.
Error: 9715, Severity: 16, The conversation endpoint with conversation handle ‘%ls’ is in an inconsistent state. Check the SQL Server error logs and the Windows event logs for information on possible hardware problems. To recover the database, restore the database from a clean back
Error: 9716, Severity: 16, The conversation group ‘%ls’ reports references to %d conversation handle(s), but actually references %d.
Error: 9717, Severity: 16, Cannot enable stored procedure activation on queue ‘%.*ls’. Event notification for queue_activation is already configured on this queue.
Error: 9718, Severity: 16, Cannot create event notification for queue_activation on queue “%.*ls”. Stored procedure activation is already configured on this queue.

Error: 9719, Severity: 16, The database for this conversation endpoint is attached or restored.
Error: 9720, Severity: 16, The database for the remote conversation endpoint is attached or restored.
Error: 9721, Severity: 10, Service broker failed to clean up conversation endpoints on database ‘%.*ls’. Another problem is preventing SQL Server from completing this operation. Check the SQL Server error log for additional messages.
Error: 9723, Severity: 10, The database “%i” will not be started as the broker due to duplication in the broker instance ID.
Error: 9724, Severity: 10, The activated proc ‘%ls’ running on queue ‘%ls’ output the following: ‘%.*ls’
Error: 9725, Severity: 16, The invalid schema has been dropped from the message type with ID %d.
Error: 9726, Severity: 16, The remote service binding with ID %d has been dropped.
Error: 9727, Severity: 16, Dialog security is not available for this conversation because there is no remote service binding for the target service. Create a remote service binding, or specify ENCRYPTION = OFF in the BEGIN DIALOG statement.
Error: 9728, Severity: 16, Cannot find the security certificate because the lookup database principal ID (%i) is not valid. The security principal may have been dropped after the conversation was created.
Error: 9730, Severity: 16, Cannot find the security certificate because the lookup database principal (Id: %i) does not correspond to a server principal. The security principal may have been dropped after the conversation was created.

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 *