Web.QHMIT.com

SQL Server System Errors: 19000 - 19999

List of error messages between 19000 and 19999 in SQL Server 2017.

These error messages are all available by querying the sys.messages catalog view on the master database.

message_id severity is_event_logged text
19030101SQL Trace ID %d was started by login "%s".
19031101SQL Trace stopped. Trace ID = '%d'. Login Name = '%s'.
19032101SQL Trace was stopped due to server shutdown. Trace ID = '%d'. This is an informational message only; no user action is required.
19033101Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
19034211Cannot start C2 audit trace. SQL Server is shutting down. Error = %ls
19035161OLE task allocator failed to initialize. Heterogeneous queries, distributed queries, and remote procedure calls are unavailable. Confirm that DCOM is properly installed and configured.
19036101The OLE DB initialization service failed to load. Reinstall Microsoft Data Access Components. If the problem persists, contact product support for the OLEDB provider.
19049160File '%.*ls' either does not exist or there was an error opening the file. Error = '%ls'.
19050160Trace file name '%.*ls' is invalid.
19051160Unknown error occurred in the trace.
19052160The active trace must be stopped before modification.
19053160The trace event ID is not valid.
19054160The trace column ID is not valid.
19055160Filters with the same event column ID must be grouped together.
19056160The comparison operator in the filter is not valid.
19057160The boolean operator in the filter is not valid.
19058160The trace status is not valid.
19059160Could not find the requested trace.
19060160The trace option is not valid.
19061160Cannot remove SPID trace column.
19062160Could not create a trace file.
19063160Not enough memory was available for trace.
19064160The requested trace stop time has been already passed.
19065160The parameter is not valid.
19066160Cannot modify a restricted trace.
19067160Cannot create a new trace because the trace file path is found in the existing traces.
19068160The trace file path is not valid or not supported.
19069160The trace file name is not valid because it contains a rollover file number (NNN in C:file_NNN) while the trace rollover option is enabled.
19070160The default trace cannot be stopped or modified. Use SP_CONFIGURE to turn it off.
19071160Stopping the trace because the current trace file is full and the rollover option is not specified.
19096160Fail to delete an old trace file '%ls'. Error = '%ls'.
19097100Operating system error occurred while running %s. Error = %s.
19098161An error occurred starting the default trace. Cause: %ls Use sp_configure to turn off and then turn on the 'default trace enabled' advanced server configuration option.
19099161Trace ID '%d' was stopped because of an error. Cause: %ls. Restart the trace after correcting the problem.
19100100Initialization succeeded.
19101100Initialization failed with an infrastructure error. Check for previous errors.
19102100Unable to create a node listener object. Check for memory-related errors.
19103100An error occurred while starting shared memory support.
19104100All protocols are disabled.
19105100Unable to create a node listener object for a special instance. Check for memory-related errors.
19106100Unable to trim spaces in an IP address. Check TCP/IP protocol settings.
19107100'TcpKeepAlive' registry setting is the wrong type. Check TCP/IP protocol settings.
19108100Unable to retrieve 'TcpKeepAlive' registry setting. Check TCP/IP protocol settings.
19109100Unable to configure MDAC-compatibility TCP/IP port in registry.
19110100Unable to initialize the TCP/IP listener.
19111100Unable to open TCP/IP protocol configuration key in registry.
19112100Unable to retrieve TCP/IP protocol 'Enabled' registry setting.
19113100Unable to retrieve 'ListenOnAllIPs' TCP/IP registry setting.
19114100Unable to open TCP/IP protocol's 'IPAll' configuration key in registry.
19115100Unable to retrieve registry settings from TCP/IP protocol's 'IPAll' configuration key.
19116100Unable to obtain list size for IP addresses configured for listening in registry.
19117100Failed to allocate memory for IP addresses configured for listening. Check for memory-related errors.
19118100Unable to obtain list of IP addresses configured for listening in registry.
19119100Unable to open TCP/IP protocol's registry key for a specific IP address.
19120100Unable to retrieve 'Enabled' setting for a specific IP address.
19121100Unable to retrieve 'Active' setting for a specific IP address.
19122100Unable to retrieve 'IpAddress' value for a specific IP address.
19123100'IpAddress' registry value is the wrong type.
19124100Unable to retrieve registry settings for a specific IP address.
19125100Unable to deallocate structures representing registry key for a specific IP address.
19126100Unable to retrieve registry settings for cluster environment.
19127100Server is configured to listen on a specific IP address in a cluster environment.
19128100The SQL Server Network Interface cannot check for a duplicate IP address in the SQL Server TCP listening settings.
19129100The SQL Server Network Interface found a duplicate IP address in the SQL Server TCP listening settings. Remove the duplicate IP address by using SQL Server Configuration Manager.
19130100Unable to open SQL Server Network Interface library configuration key in registry for Dedicated Administrator Connection settings.
19131100Unable to open Dedicated Administrator Connection configuration key in registry.
19132100Unable to open TCP/IP configuration key for Dedicated Administrator Connection in registry.
19133100Unable to retrieve dynamic TCP/IP ports registry settings for Dedicated Administrator Connection.
19134100No or more than one dynamic TCP/IP port is configured for Dedicated Administrator Connection in registry settings.
19135100Error starting Named Pipes support. Check protocol settings.
19137100Failed to allocate memory for SSL listening structures. Check for memory-related errors.
19138100An error occurred while obtaining or using the certificate for SSL. Check settings in Configuration Manager.
19139100Unable to add listener endpoints. Check for memory-related errors.
19140100Unable to initialize the communication listeners.
19141100Unable to retrieve SQL Server Network Interface library settings for a special instance.
19142100Unable to retrieve SQL Server Network Interface library settings; the instance name is too long.
19143100Unable to initialize the Shared Memory listener.
19144100Unable to initialize the Named Pipes listener.
19145100Unable to configure MDAC-compatibility Named Pipes protocol pipe name in registry.
19147100Unable to initialize the HTTP listener.
19148100Unable to initialize SSL support.
19149100Unable to configure MDAC-compatibility protocol list in registry.
19150100Unable to open SQL Server Network Interface library configuration key in registry.
19151100An error occurred while obtaining the Extended Protection setting. Check Network Configuration settings in SQL Server Configuration Manager.
19152100The configured value for Extended Protection is not valid. Check Network Configuration settings in SQL Server Configuration Manager.
19153100An error occurred while obtaining the Accepted SPNs list for Extended Protection. Check Network Configuration settings in SQL Server Configuration Manager.
19154100The configured value for the Accepted SPNs list is not valid. Check Network Configuration settings in SQL Server Configuration Manager.
19155100TDSSNIClient failed to allocate memory while loading Extended Protection configuration settings. Check for memory-related errors.
19156100Failed to allocate memory for SSPI listening structures. Check for memory-related errors.
19157100Unable to initialize the SSPI listener.
19158100Unable to create connectivity Ring Buffer. Check for memory-related errors.
19159100Unable to open 'Named Pipes' configuration key for Dedicated Administrator Connection in registry.
19160100Unable to retrieve 'Enabled' registry settings for Named-Pipe Dedicated Administrator Connection.
19161100No protocol is enabled for the Dedicated Administrator Connection.
19162100Unable to retrieve 'PipeName' registry settings for Named-Pipe Dedicated Administrator Connection.
19163100Error starting Named Pipes support for Dedicated Administrator Connection.
19164100Unable to retrieve 'GroupName' registry settings for Named-Pipe Dedicated Administrator Connection.
19165100Error starting Named Pipes support for Dedicated Administrator Connection.
19200100Authentication succeeded.
19201100The transport protocol does not provide an authentication context, and there is no authentication token in the TDS stream.
19202100An error occurred while calling CompleteAuthToken for this security context. The operating system error code indicates the cause of failure.
19203100The CompleteAuthToken API is not defined for the current Security Support Provider.
19204100AcceptSecurityContext failed. The operating system error code indicates the cause of failure.
19205100The operating system does not support Channel Bindings, but the server is configured to require Extended Protection. Update the operating system or disable Extended Protection.
19206100The Channel Bindings from this client do not match the established Transport Layer Security (TLS) Channel. The service might be under attack, or the data provider might need to be upgraded to support Extended Protection. Closing the connection.
19207100The Channel Bindings from this client are missing or do not match the established Transport Layer Security (TLS) Channel. The service might be under attack, or the data provider or client operating system might need to be upgraded to support Extended Protection. Closing the connection.
19208100The operating system does not support Service Bindings, but the server is configured to require Extended Protection. Update the operating system or disable Extended Protection.
19209100QueryContextAttributes could not retrieve Service Bindings. The operating system error code indicates the cause of failure.
19210100The server Extended Protection level is set to Allowed or Required, and the client did not provide a Service Principal Name (SPN). To connect, this client must support Extended Protection. You might have to install an operating system service pack that allows for Service Binding and Channel Binding.
19211100The server Extended Protection level is set to Allowed or Required, and the client did not provide a Service Principal Name (SPN). To connect, this client must support Extended Protection. You might have to update the SQL Server driver on the client.
19212100The Service Class element of the received Service Principal Name (SPN) is not valid.
19213100The IP Address element of the received Service Principal Name (SPN) is not valid.
19214100The Host element of the received Service Principal Name (SPN) is not valid.
19215100A memory allocation failed while validating the received Service Principal Name (SPN).
19216100QueryContextAttributes succeeded but did not retrieve the received Service Principal Name (SPN).
19217100WSAStringToAddress was unable to convert the IP Address element of the received Service Principal Name (SPN) to an address structure. The operating system error code indicates the cause of failure.
19218100Could not wait on an event signaling IO completion for a cryptographic handshake.
19219100A task to process a cryptographic handshake could not be enqueued.
19220100An attempt to read a buffer from the network failed during a cryptographic handshake.
19221100The connection was closed while attempting to process a read buffer during a cryptographic handshake.
19222100The connection was closed while attempting to process a write buffer during a cryptographic handshake.
19223100An attempt to write a buffer to the network failed during a cryptographic handshake.
19224100AcquireCredentialsHandle failed. The operating system error code indicates the cause of the failure.
19225100InitializeSecurityContext failed. The operating system error code indicates the cause of the failure.
19226100QueryContextAttributes could not retrieve stream sizes. The operating system error code indicates the cause of the failure.
19227100An attempt to resize a buffer failed.
19228100An unexpected error occurred during a cryptographic handshake.
19229100An invalid token was received during a cryptographic handshake.
19230100Failed to allocate a packet for a network write during a cryptographic handshake.
19231100Failed to allocate an object to perform a cryptographic handshake.
19232100Failed to initialize an object to perform a cryptographic handshake.
19233100A token from a cryptographic handshake was larger than allowed by SSPI.
19234100The connection was closed while waiting for network IO during a cryptographic handshake.
19235100An unexpected exception was thrown while processing a cryptographic handshake.
19236100Negotiated security context is missing an integrity flag.
19238100Negotiated security context is missing a confidentiality flag.
19239100Negotiated security context has confidentiality flag present.
19240100Negotiated security context is missing a sequence detection flag.
19241100Negotiated security context is missing a replay detection flag.
19242100Global credentials handle required for inbound connections.
19243100SSPI structures too large for encryption.
19244100SSPI structures too large for signature.
19245100Empty output token is returned by SSPI during security context negotiation. Check for network packet corruption or other networking issues.
19401160The 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 documentation in SQL Server Books Online.
19402160A 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 the command.
19403160The 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 availability replicas in a given availability group, select replica_server_name from sys.availability_replicas and name from sys.availability_groups. For more information, see SQL Server Books Online.
19404160An 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 group. Specify a valid READ_ONLY_ROUTING_URL for each replica that you want to added to the READ_ONLY_ROUTING_LIST. If you are altering availability replicas of an existing availability group, you can get the names of availability replicas in a given availability group, select replica_server_name from sys.availability_replicas and name from sys.availability_groups. For more information, see SQL Server Books Online.
19405160Failed 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 again.
19406100The state of the local availability replica in availability group '%.*ls' has changed from '%ls' to '%ls'. %ls. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console.
19407160The 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 failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster.
19408100The Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups has been changed to the remote WSFC cluster, '%.*ls'. An ALTER SERVER CONFIGURATION SET HADR CLUSTER CONTEXT = 'remote_wsfc_cluster_name' command switched the cluster context from the local WSFC cluster to this remote WSFC cluster. This is an informational message only. No user action is required.
19409100The Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups has been changed to the local WSFC cluster. An ALTER SERVER CONFIGURATION SET HADR CLUSTER LOCAL command switched the cluster context from the remote WSFC cluster, '%.*ls', to the local WSFC cluster. On this local WSFC cluster, availability databases no longer belong to any availability group, and they are transitioning to the RESTORING state. This is an informational message only. No user action is required.
19410160An attempt to switch the Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups to a remote WSFC cluster failed. This is because one or more availability replicas hosted by the local instance of SQL Server are currently joined to an availability group on the local WSFC cluster. Remove each of the joined replicas from its respective availability group. Then retry your ALTER SERVER CONFIGURATION SET HADR CLUSTER CONTEXT = '%.*ls' command.
19411160The specified Windows Server Failover Clustering (WSFC) cluster, '%.*ls', is not ready to become the cluster context of Always On Availability Groups (Windows error code: %d). The possible reason could be that the specified WSFC cluster is not up or that a security permissions issue was encountered. Fix the cause of the failure, and retry your ALTER SERVER CONFIGURATION SET HADR CLUSTER CONTEXT = 'remote_wsfc_cluster_name' command.
19412160The ALTER SERVER CONFIGURATION SET HADR CLUSTER CONTEXT = '%.*ls' command failed. The current Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups is already under a remote WSFC cluster. When Always On Availability Groups is running under a remote cluster context, switching to another remote WSFC cluster is not allowed. You can only switch to the local WSFC cluster.
19413160An attempt to switch Always On Availability Groups to the local Windows Server Failover Clustering (WSFC) cluster context failed. This attempt failed because switching the cluster context back to the local cluster at this time might cause data loss because one or more secondary databases on synchronous-commit replicas are not in the SYNCHRONIZED state. Wait until all synchronous-commit secondary databases are synchronized, and then retry the ALTER SERVER CONFIGURATION SET HADR CLUSTER LOCAL command.
19414160An attempt to switch the Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups to the specified WSFC cluster , '%ls', failed. The cluster context has been switched back to the local WSFC cluster. Check the SQL Server error log for more information. Correct the cause of the error, and repeat the steps for setting up the secondary replicas on the remote WSFC cluster from the beginning.
19415160Failed to process the registry key value '%.*ls' (Windows error code: %d), which holds the name of the remote Windows Server Failover Clustering (WSFC) cluster. For more information about this error code, see "System Error Codes" in the Windows Development documentation. Correct the cause of this error, and repeat the steps for setting up the secondary replicas on the remote WSFC cluster from the beginning.
19416160One or more databases in availability group '%.*ls' are not synchronized. On a synchronous-commit availability replica, ALTER AVAILABILITY GROUP <group_name> OFFLINE is not allowed when one or more databases are not synchronized. Wait for all databases to reach the SYNCHRONIZED state, and retry the command.
19417160An attempt to fail over or create an availability group failed. This operation is not supported when Always On Availability Groups is running under a remote Windows Server Failover Clustering (WSFC) cluster context. Under a remote cluster context, failing over or creating availability groups are not supported.
19418160The ALTER SERVER CONFIGURATION SET HADR CLUSTER CONTEXT = '%.*ls' command failed because the local Windows Server Failover Clustering (WSFC) cluster name,'%.*ls', was specified. Retry the command, specifying the name of a remote WSFC cluster.
19419160Windows Server Failover Cluster did not receive a process event signal from SQL Server hosting availability group '%.*ls' within the lease timeout period.
19420100The availability group '%.*ls' is being asked to stop the lease renewal because the availability group is going offline. This is an informational message only. No user action is required.
19421160SQL Server hosting availability group '%.*ls' did not receive a process event signal from the Windows Server Failover Cluster within the lease timeout period.
19422160The renewal of the lease between availability group '%.*ls' and the Windows Server Failover Cluster failed because SQL Server encountered Windows error with error code ('%d').
19423160The lease of availability group '%.*ls' lease is no longer valid to start the lease renewal process.
19424100The lease worker of availability group '%.*ls' is now sleeping the excess lease time (%u ms) supplied during online. This is an informational message only. No user action is required.
19431160Always On Availability Groups transport for availability database "%.*ls" has hit flow control boundary with log block whose LSN is %S_LSN. This error happens when secondary replica doesn't have buffer to receive a new message from primary. This is an informational message only. No user action is required.
19432160Always On Availability Groups transport has detected a missing log block for availability database "%.*ls". LSN of last applied log block is %S_LSN. Log scan will be restarted to fix the issue. This is an informational message only. No user action is required.
19433160Always On: AG integrity check failed to find AG name to ID map entry with matching group ID for AG '%.*ls' (expected: '%.*ls'; found '%.*ls').
19434160Always On: AG integrity check failed to find AG name to ID map entry with matching resource ID for AG '%.*ls' (expected: '%.*ls'; found '%.*ls').
19435160Always On: AG integrity check failed for AG '%.*ls' with error %d, severity %d, state %d.
19436160Always On: A failure [%d] was encountered while waiting for LSN %S_LSN to be hardened on the Commit Manager [%d] for database ID [%d] on partner ID [%s].
19450160Failed to open a cluster network interface object: '%ls'. The WSFC cluster control API returned error code %d. The WSFC service may not be running or may be inaccessible in its current state. For information about this error code, see "System Error Codes" in the Windows Development documentation.
19451160'%.*ls' and '%.*ls' belong to the same subnet. Only one IPv4 and/or one IPv6 address from each subnet is allowed. For an advanced configuration, see the Windows Server Failover Clustering (WSFC) administrator to create a customized configuration through the Cluster Manager.
19452160The availability group listener (network name) with Windows Server Failover Clustering resource ID '%s', DNS name '%s', port %hu failed to start with a permanent error: %u. Verify port numbers, DNS names and other related network configuration, then retry the operation.
19453160The availability group listener (network name) with resource ID '%s', DNS name '%s', port %hu failed to start with this error: %u. Verify network and cluster configuration and logs.
19454160The availability group listener (network name) with resource ID '%s', DNS name '%s', port %hu failed to stop with this error: %u. Verify network and cluster configuration and logs.
19455160The WSFC cluster does not have a public cluster network with an IPv4 subnet. This is a requirement to create an availability group DHCP listener. Configure a public network for the cluster with an IPv4 subnet, and try to create the listener.
19456160None of the IP addresses configured for the availability group listener can be hosted by the server '%.*ls'. Either configure a public cluster network on which one of the specified IP addresses can be hosted, or add another listener IP address which can be hosted on a public cluster network for this server.
19457160The specified IP Address '%.*ls' is not valid in the cluster-allowed IP range. Check with the network administrator to select values that are appropriate for the cluster-allowed IP range.
19458160The WSFC nodes that host the primary and secondary replicas belong to different subnets. DHCP across multiple subnets is not supported for availability replicas. Use the static IP option to configure the availability group listener.
19459160The listener with DNS name '%.*ls' does not conform to SQL Server listener guidelines, and cannot be configured through SQL Server. Reconfigure the listener through the WSFC Cluster Manager.
19460160The availability group listener with DNS name '%.*ls' is configured to use DHCP. For listeners with this configuration, IP addresses cannot be added through SQL Server. To add IP addresses to the listener, drop the DHCP listener and create it again configured to use static IP addresses.
19461160The WSFC node that hosts the primary replica belongs to multiple subnets. To use the DHCP option in a multi-subnet environment, supply an IPv4 IP address and subnet mask of the subnet for the listener.
19462160Failed to obtain the WSFC node enumeration handle. The error code is %d. The WSFC service may not be running or may be inaccessible in its current state, or the specified cluster resource handle is invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
19463160The WSFC cluster network interface control API returned error code %d. The WSFC service may not be running or may be inaccessible in its current state. For information about this error code, see "System Error Codes" in the Windows Development documentation.
19464160The WSFC cluster network control API returned an invalid IP address. The WSFC service might have invalid data in its database or it is a not supported version.
19465160The WSFC management API returned an unrecognizable dependency expression: '%.*ls'. The WSFC service might have invalid data in its database or it is a not supported version.
19466160Failed to obtain the WSFC resource dependency expression for cluster resource with name or ID '%ls' The error code is %d. The WSFC service may not be running or may be inaccessible in its current state. For information about this error code, see "System Error Codes" in the Windows Development documentation.
19467160Failed to remove the resource dependency in which resource '%.*ls' is depending on resource '%.*ls' in the WSFC cluster. The error code is %d. The WSFC service may not be running or may be inaccessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
19468160The listener with DNS name '%.*ls' for the availability group '%.*ls' is already listening on the TCP port %u. Please choose a different TCP port for the listener. If there is a problem with the listener, try restarting the listener to correct the problem.
19469160The specified listener with DNS name, '%.*ls', does not exist for the Availability Group '%.*ls'. Use an existing listener, or create a new listener.
19470160Failed to delete a resource in the WSFC cluster because the resource '%.*ls' is not offline. Delete the resource using the Failover Cluster Management tool (cluadmin.msc).
19471160The WSFC cluster could not bring the Network Name resource with DNS name '%ls' online. The DNS name may have been taken or have a conflict with existing name services, or the WSFC cluster service may not be running or may be inaccessible. Use a different DNS name to resolve name conflicts, or check the WSFC cluster log for more information.
19472160Failed to delete the WSFC cluster resource '%.*ls'. The error code is %d. The WSFC service may not be running or may be inaccessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
19473160Failed to add a resource dependency, making resource '%.*ls' depend on resource '%.*ls', in the WSFC cluster. The error code is %d. The WSFC service may not be running or may be inaccessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
19474160Failed to set the resource dependency expression '%ls' for the WSFC resource '%.*ls'. The error code is %d. The WSFC service may not be running or may be inaccessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
19475160Cannot take the WSFC resource with ID '%.*ls' offline. The error code is %d. The WSFC service may not be running or may be inaccessible in its current state. For information about this error code, see "System Error Codes" in the Windows Development documentation.
19476160The attempt to create the network name and IP address for the listener failed. If this is a WSFC availability group, the WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may be incorrect. Check the state of the WSFC cluster and validate the network name and IP address with the network administrator. Otherwise, contact your primary support provider.
19477160The availability group '%.*ls' already has a listener with DNS name '%.*ls'. Availability groups can have only one listener. Use the existing listener, or drop the existing listener and create a new one.
19478160Failed to find a multi-string property (property name '%ls') of the WSFC resource with name or ID '%.*ls'. The system error code is %d. The WSFC service may not be running or may be inaccessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
19479160The WSFC cluster network control API returned error code %d. The WSFC service may not be running or may be inaccessible in its current state. For information about this error code, see "System Error Codes" in the Windows Development documentation.
19480160Failed to open a cluster network object: '%ls'. The WSFC cluster control API returned error code %d. The WSFC service may not be running or may be inaccessible in its current state. For information about this error code, see "System Error Codes" in the Windows Development documentation.
19481160Failed to obtain the WSFC resource state for cluster resource with name or ID '%.*ls'. The WSFC resource state API returned error code %d. The WSFC service may not be running or may be inaccessible in its current state. For information about this error code, see "System Error Codes" in the Windows Development documentation.
19482160The port number, %u, that is specified is invalid. Valid port numbers range from 1 to 65535, inclusive. Select a port number in this range. If a port number is not provided, the default number 1433 is used.
19483160The format for the IP address, '%.*ls', is invalid. Please use a valid value for the IP address.
19484160The specified IP Address, '%.*ls', is duplicated in the IP address list. Each IP address included in the listener configuration must be unique. Change the statement to remove or replace the duplicated values.
19485160The specified DNS name, '%.*ls', is invalid. The length of the DNS name needs to be between 1 and 63 characters, inclusive. Change the value of the DNS name to meet this requirement.
19486160The configuration changes to the availability group listener were completed, but the TCP provider of the instance of SQL Server failed to listen on the specified port [%.*ls:%d]. This TCP port is already in use. Reconfigure the availability group listener, specifying an available TCP port. For information about altering an availability group listener, see the "ALTER AVAILABILITY GROUP (Transact-SQL)" topic in SQL Server Books Online.
19487160Listener configuration changes were completed but listening status of the corresponding TCP provider could not be determined because of the error code: %u. Check the system error log to determine if the TCP provider is listening or a listener restart is needed.
19488160The attempt to create the network name and IP address for the listener failed, and the attempt to roll back the resources for the Network Name and IP Address resources has also failed. If this is a WSFC availability group, the WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may be incorrect. Check the state of the WSFC cluster and validate the network name and IP address with the network administrator. Ensure that no Network Name or IP Address resource from this operation still exists in the cluster. Otherwise, contact your primary support provider.
19489160The attempt to create FILESTREAM RsFx endpoint failed with HRESULT 0x%x.
19490160The attempt to delete FILESTREAM RsFx endpoint failed with HRESULT 0x%x.
19491100Always On: The Windows Server Failover Clustering (WSFC) service was started using /forcequorum. This is an informational message only. No user action is required.
19492160The availability database %ls in availailability group %ls is in an invalid state to perform an internal operation. Refer to the error code for more details. If this condition persists, contact the system administrator.
19493160Corrupt secondary replica %ls causing start scan to fail for database with ID %d. Refer to the SQL Server error log for information about the errors that were encountered. If this condition persists, contact the system administrator.
19494100Automatic seeding of availability database '%ls' in availability group '%.*ls' failed with a transient error. The operation will be retried.
19495100Automatic seeding of availability database '%ls' in availability group '%.*ls' failed with an unrecoverable error. Correct the problem, then issue an ALTER AVAILABILITY GROUP command to set SEEDING_MODE = AUTOMATIC on the replica to restart seeding.
19496100Automatic seeding of availability database '%.*ls' in availability group '%.*ls' failed.
19497160Conflicting option spec provided. DISTRIBUTED option cannot be combined with any other availability group options.
19498160To create a distributed availability group, please specify the DISTRIBUTED option.
19499160The specified listener URL '%.*ls' is invalid. Reenter the command specifying the correct URL. For information about specifying the endpoint URL for an availability replica, see SQL Server Books Online.
19501160None of the specified availability groups exist locally. Please check your DDL and make sure there is one availability group exist locally.
19502160Cannot create a distributed availability replica for availability group '%.*ls'. An availability replica of the specified availability group already exists on this instance of SQL Server. Verify that the specified availability group name is correct and unique, then retry the operation. To remove the existing availability replica, run DROP AVAILABILITY GROUP command.
19503160Cannot create a distributed availability replica for availability group '%.*ls'. Local availability group is participating in a distributed availability group as secondary.
19504160Cannot failover a distributed availability replica for availability group '%.*ls'. Only force failover is supported in this version of SQL Server.
19505100Cannot initiate a target seeding operation on a non-secondary/forwarder replica for availability group '%.*ls'. Replica state may have changed since we submit the build task.
19506160Local availability replica for availability group '%.*ls' has not been granted permission to create databases, but has a SEEDING_MODE of AUTOMATIC. Use the ALTER AVAILABILITY GROUP ... GRANT CREATE ANY DATABASE command to allow the creation of databases seeded by the primary availability replica.
19507160Cannot create a distributed availability replica for availability group '%.*ls'. There is an already existing distributed availability group on top of the same replicas.
19508160'ALTER AVAILABILITY GROUP MODIFY AVAILABILITY GROUP' command failed. Participant availability replica '%.*ls' not found in the distributed availability group '%.*ls'.
19509160Cannot create a distributed availability group '%.*ls'. An availability group with the same name already exists.
19510160Distributed availability group '%.*ls' not found. Rerun the command with an existing distributed availbility group.
19511160Cannot join distributed availability group '%.*ls'. The local availability group '%.*ls' contains one or more databases. Remove all the databases or create an empty availability group to join a distributed availability group.
19512160The requested operation only applies to distributed availability group, and is not supported on the specified availability group '%.*ls'. Please make sure you are specifing the correct availability group name.