SQL Server Errors or Failures from Error: 9731 to Error: 9751

SQLServerF1

 

Error: 9731, Severity: 16, Dialog security is unavailable for this conversation because there is no security certificate bound to the database principal (Id: %i). Either create a certificate for the principal, or specify ENCRYPTION = OFF when beginning the conversation.
Error: 9733, Severity: 16, There is no private key for the security certificate bound to database principal (Id: %i). The certificate may have been created or installed incorrectly. Reinstall the certificate, or create a new certificate.
Error: 9734, Severity: 16, The length of the private key for the security certificate bound to database principal (Id: %i) is incompatible with the Windows cryptographic service provider. The key length must be a multiple of 64 bytes.

Error: 9735, Severity: 16, The length of the public key for the security certificate bound to database principal (Id: %i) is incompatible with the Windows cryptographic service provider. The key length must be a multiple of 64 bytes.
Error: 9736, Severity: 16, An error occurred in dialog transmission: Error: %i, State: %i. %.*ls
Error: 9737, Severity: 16, The private key for the security certificate bound to the database principal (ID %i) is password protected. Password protected private keys are not supported for use with secure dialogs.
Error: 9738, Severity: 16, Cannot create task for Service Broker message dispatcher. This message is a symptom of another problem that is preventing SQL Server from creating tasks. Please check the SQL Server error log and the Windows event log for additional messages.
Error: 9739, Severity: 16, Message transmitter in service broker message dispatcher failed %d times

Error: 9740, Severity: 16, Cannot start the Service Broker message dispatcher. This error is a symptom of another problem. Check the SQL Server error log and the Windows event log for additional messages, and address this underlying problem.
Error: 9741, Severity: 10, The %S_MSG ‘%.*ls’ was dropped on upgrade because it referenced a system contract that was dropped.
Error: 9742, Severity: 16, The activation stored procedure ‘%.*ls’ is invalid. Temporary procedures may not be configured for activation.
Error: 9743, Severity: 16, The %s of route “%.*ls” must be an address when using mirroring.
Error: 9744, Severity: 16, The %s of route “%.*ls” is not a valid address.
Error: 9745, Severity: 16, The ADDRESS of route ‘%.*ls’ cannot be ‘TRANSPORT’ when SERVICE_NAME is specified.
Error: 9746, Severity: 16, The LIFETIME of route ‘%.*ls’ must be in the range %d to %d.
Error: 9747, Severity: 16, The ADDRESS and MIRROR_ADDRESS of route ‘%.*ls’ cannot be the same.
Error: 9748, Severity: 10, The %S_MSG protocol transport is not available.
Error: 9749, Severity: 10, Target queue is busy; message(s) queued for delivery.
Error: 9750, Severity: 10, No route matches the destination service name for this conversation. Create a route to the destination service name for messages in this conversation to be delivered.
Error: 9751, Severity: 10, Authentication failed with error: ‘%.*ls’.

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 *