SQL Server Errors or Failures from Error: 19232 to Error: 19407

SQLServerF1

 

Error: 19232, Severity: 10, Failed to initialize an object to perform a cryptographic handshake.
Error: 19233, Severity: 10, A token from a cryptographic handshake was larger than allowed by SSPI.
Error: 19234, Severity: 10, The connection was closed while waiting for network IO during a cryptographic handshake.
Error: 19235, Severity: 10, An unexpected exception was thrown while processing a cryptographic handshake.

Error: 19236, Severity: 10, Negotiated security context is missing an integrity flag.
Error: 19238, Severity: 10, Negotiated security context is missing a confidentiality flag.
Error: 19239, Severity: 10, Negotiated security context has confidentiality flag present.
Error: 19240, Severity: 10, Negotiated security context is missing a sequence detection flag.
Error: 19241, Severity: 10, Negotiated security context is missing a replay detection flag.
Error: 19242, Severity: 10, Global credentials handle required for inbound connections.

Error: 19243, Severity: 10, SSPI structures too large for encryption.
Error: 19244, Severity: 10, SSPI structures too large for signature.
Error: 19245, Severity: 10, Empty output token is returned by SSPI during security context negotiation. Check for network packet corruption or other networking issues.
Error: 19401, Severity: 16, The READ_ONLY_ROUTING_URL ‘%.*ls’ specified for availability replica ‘%.*ls’ is not valid. It does not follow the required format of ‘TCP://system-address:port’. For information about the correct routing URL format, see the CREATE AVAILABILITY GROUP docum
Error: 19402, Severity: 16, A duplicate availability replica ‘%.*ls’ was specified in the READ_ONLY_ROUTING_LIST for availability replica ‘%.*ls’. Inspect the replica list that you specified in your command, and remove the duplicate replica name or names from the list. Then retry th
Error: 19403, Severity: 16, The availability replica ‘%.*ls’ specified in the READ_ONLY_ROUTING_LIST for availability replica ‘%.*ls’ does not exist. Only availability replicas that belong to the specified availability group ‘%.*ls’ can be added to this list. To get the names of ava
Error: 19404, Severity: 16, An availability replica ‘%.*ls’ that is specified in the READ_ONLY_ROUTING_LIST for availability replica ‘%.*ls’ does not have a value set for READ_ONLY_ROUTING_URL. Ensure a READ_ONLY_ROUTING_URL is set for each availability replica in the availability g
Error: 19405, Severity: 16, Failed to create, join or add replica to availability group ‘%.*ls’, because node ‘%.*ls’ is a possible owner for both replica ‘%.*ls’ and ‘%.*ls’. If one replica is failover cluster instance, remove the overlapped node from its possible owners and try ag
Error: 19406, Severity: 10, The state of the local availability replica in availability group ‘%.*ls’ has changed from ‘%ls’ to ‘%ls’. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more information, see the availabi
Error: 19407, Severity: 16, The lease between availability group ‘%.*ls’ and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is fail

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 *