983 14 Unable to access database '%.*ls' because its replica role is RESOLVING does not allow connections. Try the operation again later. Check SQL ERRORLOGs, event logs, etc. for network, storage related messages etc. 1408 16 The remote copy of database "%.*ls" is not recovered far enough to enable database mirroring or to join it to the availability group. You need to apply missing log records to the remote database by restoring the current log backups from the principal/prim 1409 16 Database "%.*ls" requires database logs to be restored either on the future mirror database before you can enable database mirroring or on a secondary availability database before you can join it to the availability group. Restore current log backups from 1465 16 Database "%.*ls" database is not in full recovery mode on each of the server instances. The full recovery model is required for a database to participate in database mirroring or in an availability group. 1466 16 Database "%.*ls" is read-only on one of the server instances which is incompatible with participating in database mirroring or in an
19401 16 The READ_ONLY_ROUTING_URL '%.*ls' specified for availability replica '%.*ls' is not 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 19403 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 19405 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 May occur if AG involves two or more SQL failover instances. Check possible owners of SQL resource on both/more so as to verify no node name overlap. There should not be node-overlap. TSQL: SELECT * FROM sys.dm_os_cluster_nodes; Powershell: get-clusterownernode -resource "XXXBSQL" Powershell: set -clusterownernode -resource "XXXASQL" -owners 19406 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 If the changed is PRIMARY_PENDING, then check sys.dm_hadr_database_replica_states. If database_state_desc = RECOVERY_PENDING (synchronization_health_desc will be NOT_HEALTHY), then try “ALTER DATABASE db SET HADR RESUME;”. Else if this is the only replica (no secondary replica), then (consider first taking a database snapshot as a backup if required) try “ALTER DATABASE db SET HADR OFF;” to remove AlwaysOn so as to then
database '%s' belongs to a HADRon availability group and must be redirected to its associated HADRon Virtual Network Name. 16 The query at the redirected publisher '%s' to determine whether the publisher database '%s' belonged to an availability group failed with error '%d', error message '%s'. 21884 16 The at the redirected publisher '%s' to determine the health of the availability group associated with publisher database '%s' failed with error '%d', error message '%s'. 21887 16 The at the redirected publisher '%s' to determine whether the publisher database '%s' belonged to an availability group failed with error '%d', error message '%s'. 21892 16 Unable to query sys.availability_replicas at the availability group primary associated with virtual network name '%s' for the server names of the member replicas: error = %d, error message = %s.', 33445 16 The database '%.*s' is a readable secondary database in an availability and cannot be
16 AlwaysOn Availability Groups transport for availability database "%.*ls" failed to decompress the log block whose LSN is %S_LSN. This error can be caused by a corrupt network packet or a compression version mismatch. The database replica has been put in 35288 16 AlwaysOn Availability Groups log for availability database "%.*ls" has received an log block. The expected LSN was %S_LSN. The received LSN was %S_LSN. The database replica has been put into the SUSPENDED state. Resume the availabil 10 Nonqualified transactions are being rolled back in database %.*ls for an AlwaysOn Availability Groups state change. Estimated rollback completion: %d%%. This is an informational message only. No user action is required. This is an informational message only. If there is a problem, then look for additional messages. 41009 16 The Windows Server Failover Clustering (WSFC) resource control API returned error code %d. The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, Net helpmsg on the %d value, and proceed accordingly. May also be accompanied by Microsoft-Windows-FailoverClustering messages in event log. Check cluster log. If there error is in cluster in Windows Azure, then it may be because Windows Azure currently does not support more than one IP address per VM, which is required by the availability group listener to resolve to the availability group owner node. This is documented in (High Availability and Disaster Recovery for SQL Server in Windows Azure Virtual Machines). order
message only. No user action is required. 41055 10 AlwaysOn Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required. This is an informational message only. If there is a problem, then look for additional messages. 16 Availability replica '%.*ls' of availability '%.*ls' cannot be brought online on this SQL Server instance. Another replica of the same availability group is already online on the local Windows Server Failover Clustering (WSFC) node. Each WSFC node 41058 10 AlwaysOn: The local replica of availability group '%.*ls' is starting. This is an informational message only. No user action is required. This is an informational message only. If is a problem, then look for additional messages. 41059 10 AlwaysOn: Availability '%.*ls' was removed while the availability replica on this instance of SQL Server was offline. The local replica will be removed now. This is an informational message only. No user action is required. This is an informational message only. If there is a problem, then look for additional messages. 41060 16 The Cyclic Redundancy Check (CRC) value generated for the retrieved availability group configuration data from the Windows Server Failover Clustering (WSFC) store does not
informational message only. No user action is required. 16 A Windows Server Failover Clustering (WSFC) API required by availability groups has not been loaded. AlwaysOn Availability Groups replica manager is not enabled on the local instance SQL Server. If the server instance is running an edition of SQL Server t 41113 16 Cannot failover availability group '%.*ls' to this instance of SQL Server because a failover command is already pending on the local replica of this availability group. Wait for the pending failover command to complete before issuing another command on t 41114 16 Cannot create an availability group named '%.*ls' because it already exists in a system table. 41115 16 Cannot create the availability named '%.*ls' because its availability group ID (ID: '%.*ls') already exists in a system table. 41116 16 Cannot create an availability group named '%.*ls' with replica ID '%.*ls' because this ID already exists in a system table. 41117 16 Cannot map local database ID %d to the availability database ID '%.*ls' within availability group
exists. An attempt to rollback the operation failed. Check the SQL Server error log for more details. To manually clean 41199 16 The specified command is invalid because the AlwaysOn Availability Groups feature is not supported by this edition of SQL Server. For information about features supported by the editions of SQL Server, see SQL Server Books Online. 41402 16 The WSFC cluster is offline, and this availability group is not available. This issue can be caused by a cluster service issue or by the loss of quorum in the cluster. 41403 16 Availability is offline. 41404 16 The availability group is offline, and is unavailable. This issue can be caused by a failure in the server instance that hosts the primary replica or by the WSFC availability group resource going offline. 41405 16 Availability is not ready for automatic failover. 41406 16 The availability group is not ready for automatic failover. The primary replica and a secondary replica are configured for automatic failover, however, the secondary replica is not ready for