SQL Server Errors or Failures from Error: 9685 to Error: 9707

SQLServerF1

 

Error: 9685, Severity: 16, The service contract with ID %d has been dropped.
Error: 9686, Severity: 16, The conversation endpoint with handle ‘%ls’ has been dropped.
Error: 9687, Severity: 16, The conversation group ‘%ls’ has been dropped.
Error: 9688, Severity: 10, Service Broker manager has started.
Error: 9689, Severity: 10, Service Broker manager has shut down.
Error: 9690, Severity: 10, The %S_MSG endpoint is now listening for connections.
Error: 9691, Severity: 10, The %S_MSG endpoint has stopped listening for connections.

Error: 9692, Severity: 16, The %S_MSG endpoint cannot listen on port %d because it is in use by another process.
Error: 9693, Severity: 16, The %S_MSG endpoint cannot listen for connections due to the following error: ‘%.*ls’.
Error: 9694, Severity: 16, Could not start Service Broker manager. Check the SQL Server error log and the Windows error log for additional error messages.
Error: 9695, Severity: 16, Could not allocate enough memory to start the Service Broker task manager. This message is a symptom of another problem. Check the SQL Server error log for additional messages, and address the underlying problem.
Error: 9696, Severity: 16, Cannot start the Service Broker primary event handler. This error is a symptom of another problem. Check the SQL Server error log for additional messages, and address this underlying problem.

Error: 9697, Severity: 10, Could not start Service Broker for database id: %d. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.
Error: 9698, Severity: 16, Cannot start Service Broker security manager. This message is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages, and address the underlying problem.
Error: 9699, Severity: 16, Could not allocate memory for extra Service Broker tasks while adding CPUs.
Error: 9701, Severity: 16, Cannot start Service Broker activation manager. This message is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages and address the underlying problem.
Error: 9704, Severity: 16, This message could not be delivered because it failed XML validation. This failure occurred while the message was being delivered to the target service.
Error: 9705, Severity: 16, The messages in the queue with ID %d are referencing the invalid conversation handle ‘%ls’.
Error: 9706, Severity: 16, The stored procedure with ID %d is invalid but is referenced by the queue with ID %d.
Error: 9707, Severity: 16, The activation user with ID %d is invalid but is referenced by queue with 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 *