You are on page 1of 27

SQL Server AlwaysOn errors (related to Availability Groups)

error severitydescription
Database '%.*ls' is enabled for database
mirroring or has joined an availability group.
957 17 The name of the database cannot be changed.
 If
dm_hadr_availability_replica_states.role_desc=3(INVALID),
The target database, '%.*ls', is participating in then check service broker. Because Availability group is
an availability group and is currently not using Service Broker to communicate between SQL Server
accessible for queries. Either data movement is then need to check Service Broker first. Open
suspended or the availability replica is not SSMS>“Server Objects” > “Endpoints”, there are two
enabled for read access. To allow read-only “Service Broker” folder>Expand both, and if the state is
976 14 access to this and other Stopped or Disabled, then can change the state to Started.
The target database ('%.*ls') is in an availability
group and is currently accessible for
connections when the application intent is set
to read only. For more information about
application intent, see SQL Server Books
978 14 Online.
The target database ('%.*ls') is in an availability
group and currently does not allow read only
connections. For more information about
application intent, see SQL Server Books
979 14 Online.
Unable to access the '%.*ls' database because
no online secondary replicas are enabled for
read-only access. Check the availability group
configuration to verify that at least one
secondary replica is configured for read-only
982 14 access. Wait for an enabled r
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
1408 16 backups from the principal/prim
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
1409 16 current log backups from
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
1465 16 or in an availability group.
Database "%.*ls" is read-only on one of the
server instances which is incompatible with
participating in database mirroring or in an
availability group. Set the database to read-
1466 16 write mode, and retry the operation.
Database "%.*ls" database is in emergency or
suspect mode on one of the partners which is
incompatible with participating in database
1467 16 mirroring or in an availability group.
The operation cannot be performed on
database "%.*ls" because it is involved in a
database mirroring session or an availability
group. Some operations are not allowed on a
database that is participating in a database
1468 16 mirroring session or in an availabilit
Database "%.*ls" is an auto-close database on
1469 16 one of the partnerswhich is incompatible with
participating in database mirroring or in an
availability group.
The %S_MSG database "%.*ls" is changing
roles from "%ls" to "%ls" because the mirroring
session or availability group failed over due to
%S_MSG. This is an informational message
1480 10 only. No user action is required.
Database "%.*ls" database is in single user
mode which is incompatible with participating
in database mirroring or in an availability
group. Set database to multi-user mode, and
1488 16 retry the operation.
File '%ls' cannot be reused until after the next
BACKUP LOG operation. If the database is
participating in an availability group, a dropped
file can be reused only after the truncation LSN
of the primary availability replica has passed
1833 16 the drop LSN of the
RESTORE cannot operate on database '%ls'
because it is configured for database mirroring
or has joined an availability group. If you
intend to restore the database, use ALTER
DATABASE to remove mirroring or to remove
3104 16 the database from its availability gro
 Before you can drop the database, you need to remove it
from the availability group. If AG exists, try ALTER
AVAILABILITY GROUP [AGname] REMOVE DATABASE
[DbName]. If AG does not exist, try removing with ALTER
DATABASE [DbName] SET HADR OFF.
 If replica_id and group_database_id in sys.databases show
The database '%.*ls' is currently joined to an as null, then this may be due to earlier meta-data when
availability group. Before you can drop the database was part of an AG so stop SQL Server, rename
database, you need to remove it from the the database files and start SQL Server. Then you should
3752 16 availatility group. be able to remove the database.
Failed to remove a FILESTREAM file. The
database is a primary database in an
availability group. Wait for the FILESTREAM
data files to be hardened on every secondary
availability replica. Then retry the drop file
5529 16 operation.
The ALTER AVAILABILITY GROUP command
failed because it contained multiple MODIFY
REPLICA options: %ls. Enter a separate ALTER
AVAILABILITY GROUP ... MODIFY REPLICA
command for each replica option that you
10786 16 want to modify.
13251 10 availability group
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
19401 16 CREATE AVAILABILITY GROUP docum
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
19403 16 the names of ava
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
19405 16 possible owners and try ag
The state of the local availability replica in
availability group '%.*ls' has changed from '%ls'
19406 10 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
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
19407 16 the availability group is fail
The 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
19452 16 related network configuration, then retry
The availability group listener (network name)
with Windows Server Failover Clustering
resource ID '%s', DNS name '%s', port %hu
failed to start with this error: %u. Verify
19453 16 network and cluster configuration and logs.
The availability group listener (network name)
with Windows Server Failover Clustering
resource ID '%s', DNS name '%s', port %hu
failed to stop with this error: %u. Verify
19454 16 network and cluster configuration and logs.
The 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
19455 16 create the listener.
None of the IP addresses configured for the  Added a new IP address (with different subnet) manually
availability group listener can be hosted by the to the existing Listener [to be tested].
server '%.*ls'. Either configure a public cluster
network on which one of the specified IP
addresses can be hosted, or add another
19456 16 listener IP address which can b
The 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
19458 16 to configure the availability group listener.
The 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
19460 16 create it again config
The 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
19468 16 correct the problem
The specified listener with DNS name, '%.*ls',
does not exist for the Availability Group '%.*ls'.
Use an existing listener, or create a new
19469 16 listener.
The 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
19477 16 and create a new one.
The 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
19486 16 availability group listener
The availability group associated with Virtual
21872 16 Network Name '%s' has no replicas.
The virtual network name '%s' has been used
to identify the redirected publisher for original
publisher '%s' and database '%s'. The
availability group associated with this virtual
network name, however, does not include the
21880 16 publisher database.
The database '%s' at the redirected publisher
'%s' for original publisher '%s' and database
'%s' belongs to a HADRon availability group
and must be redirected to its associated
21882 16 HADRon Virtual Network Name.
The query at the redirected publisher '%s' to
determine whether the publisher database
'%s' belonged to an availability group failed
21883 16 with error '%d', error message '%s'.
The query at the redirected publisher '%s' to
determine the health of the availability group
associated with publisher database '%s' failed
21884 16 with error '%d', error message '%s'.
The query at the redirected publisher '%s' to
determine whether the publisher database
'%s' belonged to an availability group failed
21887 16 with error '%d', error message '%s'.
Unable to query sys.availability_replicas at the
availability group primary associated with
21892 16 virtual network name '%s' for the server names
of the member replicas: error = %d, error
message = %s.',

The database '%.*s' is a readable secondary


database in an availability group and cannot be
enabled for FILESTREAM non-transacted
33445 16 access.
The FILESTREAM database configuration
cannot be changed for database '%.*s'. The
database is either a mirror database in
Database Mirroring, or is in a secondary replica
of an AlwaysOn availability group. Connect to
33446 16 the server instance that hosts the pr
FILESTREAM File I/O access is enabled, but no
listener for the availability group is created. A
FILESTREAM PathName will be unable to refer
to a virtual network name (VNN) and, instead,
will need to refer to a physical Windows Server
33449 10 Failover Clustering (
FILESTREAM File I/O access is enabled. One or
more availability groups ('%ls') currently do not
have a listener. A FILESTREAM PathName will
be unable to refer to a virtual network name
(VNN) and, instead, will need to refer to a
33450 10 physical Windows Server F
A connection for availability group '%ls' from
availability replica '%ls' with id [%ls] to '%ls'
with id [%ls] has been successfully established.
This is an informational message only. No user
35202 10 action is required.
Could not start the AlwaysOn Availability
Groups transport manager. This failure
probably occurred because a low memory
condition existed when the message
dispatcher started up. If so, other internal
tasks might also have experienced errors.
35205 16 Check the SQL
 If there is a login failed for domain\node$ account around
same time, then it may be because NT
AUTHORITY\SYSTEM account lacked the required
permissions to failover the availability group. To failover
the group to the other node, NT AUTHORITY\SYSTEM must
have permission to connect to SQL (CONNECT SQL),
failover the availability group (ALTER ANY AVAILABILITY
GROUP) and execute sp_server_diagnostics (VIEW SERVER
STATE). The NT AUTHORITY\SYSTEM account is used to
automatically execute sp_server_diagnostics. Another
option is to add the account to sysadmin role in SQL
A connection timeout has occurred on a Server.
previously established connection to CREATE LOGIN [NT AUTHORITY\SYSTEM] FROM WINDOWS
availability replica '%ls' with id [%ls]. Either a WITH DEFAULT_DATABASE=[master],
networking or a firewall issue exists or the DEFAULT_LANGUAGE=[us_english];
availability replica has transitioned to the ALTER SERVER ROLE [sysadmin] ADD MEMBER [NT
35206 10 resolving role. AUTHORITY\system];
Connection attempt on availability group id
'%ls' from replica id '%ls' to replica id '%ls'
failed because of error %d, severity %d, state
35207 16 %d.
Failed to modify options for availability replica
'%.*ls' in availability group '%.*ls'. The
specified availability group does not contain an
availability replica with specified name. Verify
that availability group name and availability
35210 16 replica name are c
The %ls operation is not allowed by the current
availability-group configuration. This
operation would exceed the maximum number
of %d synchronous-commit availability replicas
in availability group '%.*ls'. Change one of the
35212 16 existing synchronous-commit
The %ls operation is not allowed by the current
availability-group configuration. This
operation would exceed the maximum number
of %d automatic failover targets in availability
group '%.*ls'. Change one of the existing
35213 16 synchronous-commit replicas to th
The thread pool for AlwaysOn Availability
Groups was unable to start a new worker
thread because there are not enough available
worker threads. This may degrade AlwaysOn
Availability Groups performance. Use the
35217 16 "max worker threads" configuration option
Could not process the operation. AlwaysOn
Availability Groups replica manager is waiting
for the host computer to start a Windows
Server Failover Clustering (WSFC) cluster and
join it. Either the local computer is not a
35220 16 cluster node, or the local cluster
Could not process the operation. AlwaysOn
Availability Groups replica manager is disabled
on this instance of SQL Server. Enable
AlwaysOn Availability Groups, by using the SQL
Server Configuration Manager. Then, restart
35221 16 the SQL Server service, and retry t
Could not process the operation. AlwaysOn
Availability Groups does not have permissions
to access the Windows Server Failover
35222 16 Clustering (WSFC) cluster. Disable and re-
enable AlwaysOn Availability Groups by using
the SQL Server Configuration Manager. The

Cannot add %d availability replica(s) to


availability group '%.*ls'. The availability group
already contains %d replica(s), and the
maximum number of replicas supported in an
35223 16 availability group is %d.
Could not process the operation. AlwaysOn
Availability Groups failed to load the required
Windows Server Failover Clustering (WSFC)
library. Verify that the computer is a node in a
WSFC cluster. You will need to restart the SQL
35224 16 Server instance to reload
Could not process the operation. The instance
of SQL Server is running under WOW64
(Windows 32-bit on Windows 64-bit), which
does not support AlwaysOn Availability
Groups. Reinstall SQL Server in the native 64-
35225 16 bit edition, and re-enable AlwaysOn Availab
Could not process the operation. AlwaysOn
Availability Groups has not started because the
instance of SQL Server is not running as a
service. Restart the server instance as a
35226 16 service, and retry the operation.
The attempt to set the failure condition level
for availability group '%.*ls' failed. The
specified level value is out of the valid range
[%u, %u]. Reenter the command specifying a
35228 16 valid failure condition level value.
The attempt to set the health check timeout
value for availability group '%.*ls' failed. The
specified timeout value is less than %u
milliseconds. Reenter the command specifying
35229 16 a valid health check timeout value.
Cannot create an availability group containing
35233 16 %d availability replica(s).
None of the specified replicas for availability
group %.*ls maps to the instance of SQL Server
to which you are connected. Reenter the
command, specifying this server instance to
host one of the replicas. This replica will be the
35237 16 initial primary replica.
Database '%.*ls' cannot be added to
availability group '%.*ls'. The database does
not exist on this SQL Server instance. Verify
that the database name is correct, then retry
35238 16 the operation.
The ALTER DATABASE <database-name> SET
HADR SUSPEND (or SET HADR RESUME)
statement failed on database '%.*ls' of
availability group '%.*ls''. Either the availability
group does not contain the specified database,
35239 16 or the database has not joined the availab
 TSQL to unjoin is “ALTER DATABASE db SET HADR OFF”.
Note that failing over thus making it a secondary, and then
retrying ALTER DATABASE HADR is not an option, because
the alter database will then give error 921 that database
has not been recovered yet.
Database '%.*ls' cannot be joined to or  If this replica can be made a secondary, then fail over thus
unjoined from availability group '%.*ls'. This making it a secondary, and then drop replica when in this
operation is not supported on the primary secondary role. TSQL is “ALTER AVAILABILITY GROUP
35240 16 replica of the availability group. AgName REMOVE REPLICA ON ‘ReplicaName’;”.
 If no secondary replica for failover and getting this error on
primary, then “DROP AVAILABILITY GROUP AgName”. This
will automatically drop listener. If do not want listener
dropped, then create a temporary AG adding same name,
then try the “DROP AVAILABILITY GROUP”.
Cannot complete this ALTER DATABASE
<database-name> SET HADR operation on
database '%.*ls'. The database is not joined to
an availability group. After the database has
joined the availability group, retry the
35242 16 command.
Failed to set resource property '%.*ls' for
availability group '%.*ls'. The operation
encountered SQL Server error %d. When the
cause of the error has been resolved, retry the
35243 16 ALTER AVAILABILITY GROUP command later.
Database '%.*ls' cannot be added to
availability group '%.*ls'. The database is
currently joined to another availability group.
Verify that the database name is correct and
that the database is not joined to an
35244 16 availability group, then retry the operati
Failed to create the availability group. A SQL
Server instance name could not be validated
because the dynamic link library (DLL) file '%ls'
could not be located (Windows System Error
%d). Verify that the specified server instance
35246 16 exists. If it exists, th
Failed to create the availability group. A SQL
Server instance name could not be validated
because the dynamic link library (DLL) file '%ls'
could not be loaded (Windows System Error
35247 16 %d).
An attempt to add or join a system database,
'%.*ls', to an availability group failed. Specify
35249 16 only user databases for this operation.
An error occurred while accessing the
availability group metadata. Remove this
database or replica from the availability group,
and reconfigure the availability group to add
the database or replica again. For more
35254 16 information, see the ALTER AVAILABILITY G
AlwaysOn Availability Groups Send Error (Error
code 0x%X, "NOT OK") was returned when
sending a message for database ID %d. If the
partner is running and visible over the
network, retry the command using correctly
35257 16 configured partner-connection parameters
Database '%.*ls' is already participating in a
35259 16 different availability group.
During an attempted database recovery, an
availability database manager was not found
for database id %d with availability group ID
%d and group database ID %ls. Recovery was
terminated. The most likely cause of this error
35260 16 is that the availability group
Attempt to perform an AlwaysOn Availability
Groups operation on a system database, '%ls',
failed. System databases are not supported by
35261 16 AlwaysOn Availability Groups.
Skipping the default startup of database '%.*ls'  Check SQL and Windows logs for additional messages if
because the database belongs to an availability expecting database to start.
group (Group ID: %d). The database will be
started by the availability group. This is an
informational message only. No user action is
35262 17 required.
AlwaysOn Availability Groups data movement  Link redirects to http://msdn.microsoft.com/en-
for database '%.*ls' has been suspended for us/library/ff877956.aspx and the mention steps should be
the following reason: "%S_MSG" (Source ID followed to resume data movement.
%d; Source string: '%.*ls'). To resume data
movement on the database, you will need to
35264 10 resume the database manually. For infor
AlwaysOn Availability Groups data movement
for database '%.*ls' has been resumed. This is
an informational message only. No user action
35265 10 is required.
AlwaysOn Availability Groups connection with
%S_MSG database established for %S_MSG
database '%.*ls' on the availability replica with
Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-
%.2x%.2x%.2x%.2x%.2x%.2x}. This is an
35266 10 informational message only. No user action is
AlwaysOn Availability Groups connection with
%S_MSG database terminated for %S_MSG
database '%.*ls' on the availability replica with
Replica ID: {%.8x-%.4x-%.4x-%.2x%.2x-
%.2x%.2x%.2x%.2x%.2x%.2x}. This is an
35267 10 informational message only. No user action is r
A previous RESTORE WITH
CONTINUE_AFTER_ERROR operation or being
removed while in the SUSPECT state from an
availability group left the '%.*ls' database in a
potentially damaged state. The database
cannot be joined while in this state. Restore
35275 16 the database
Failed to allocate and schedule an AlwaysOn
Availability Groups task for database '%ls'.
Manual intervention may be required to
35276 17 resume synchronization of the database. If the
problem persists, you might need to restart
the local instance of SQL Server.

The attempt to join database '%.*ls' to the


availability group was rejected by the primary
database with error '%d'. For more
information, see the SQL Server error log for
35279 16 the primary replica.
Database '%.*ls' cannot be added to
availability group '%.*ls'. The database is
already joined to the specified availability
group. Verify that the database name is
correct and that the database is not joined to
35280 16 an availability group, then retry the ope
Database '%.*ls' cannot be removed from
availability group '%.*ls'. The database is not
joined to the specified availability group.
Verify that the database name and the
availability group name are correct, then retry
35281 16 the operation.
Availability replica '%.*ls' cannot be added to
availability group '%.*ls'. The availability group
already contains an availability replica with the
specified name. Verify that the availability
replica name and the availability group name
35282 16 are correct, t
Availability replica '%.*ls' cannot be removed
from availability group '%.*ls'. The availability
group does not contain an availability replica
with the specified name. Verify that the
availability replica name is correct, then retry
35283 16 the operation.
Availability replica '%.*ls' cannot be removed
from availability group '%.*ls', because this
replica is on the local instance of SQL Server. If
the local availability replica is a secondary
replica, connect to the server instance that is
35284 16 currently hostin
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
35287 16 in
AlwaysOn Availability Groups log apply for
availability database "%.*ls" has received an
out-of-order log block. The expected LSN was
%S_LSN. The received LSN was %S_LSN. The
database replica has been put into the
35288 16 SUSPENDED state. Resume the availabil
Nonqualified transactions are being rolled back
in database %.*ls for an AlwaysOn Availability
Groups state change. Estimated rollback
completion: %d%%. This is an informational
35299 10 message only. No user action is required.
An availability group replica already exists on
the Windows Server Failover Clustering (WSFC)
node '%.*ls'. Each WSFC node can contain only
one replica of an availability group. Please
choose another WSFC node to host the new
41039 16 replica.
Failed to remove the availability group replica
'%.*ls' from availability group '%.*ls'. The
availability group does not contain a replica
41040 16 with the specified name. Verify the availability
group and replica names and then retry the
operation.

The availability group '%.*ls' already exists.  If AG still exists, DROP AVAILABILITY GROUP.
This error could be caused by a previous failed  Open regedit, backup the entry from the old Availability
CREATE AVAILABILITY GROUP or DROP Group that starts with HADR_Ag_???? key, then delete this
AVAILABILITY GROUP operation. If the key [to be tested].
availability group name you specified is  Try with new name for Availability Group.
41042 16 correct, try dropping the availability group a
For availability group '%.*ls', the value of the
name-to-ID map entry is invalid. The binary
value should contain a Windows Server
Failover Clustering (WSFC) resource ID, a WSFC
group ID, and their corresponding lengths in
41043 16 characters. The availability g
Availability group name to ID map entry for
availability group '%.*ls' cannot be found in the
Windows Server Failover Clustering (WSFC)
store. The availability group name may be
incorrect, or the availability group may not
41044 16 exist in this Windows Server Fa
Cannot add database '%.*ls' to the availability
group '%.*ls', because there is already a
database with the same name in the
availability group. Please verify that the
database and availability group names
41045 16 specified are correct.
Cannot add replica '%.*ls' to the availability
group '%.*ls', because there is already a replica
with the same name in the availability group.
Please verify the replica and availability group
41046 16 names specified are correct.
AlwaysOn Availability Groups: Local Windows
41048 10 Server Failover Clustering service has become
unavailable. This is an informational message
only. No user action is required.
AlwaysOn Availability Groups: Local Windows
Server Failover Clustering node is no longer
online. This is an informational message only.
41049 10 No user action is required.
AlwaysOn Availability Groups: Waiting for local
Windows Server Failover Clustering service to
start. This is an informational message only. No
41050 10 user action is required.
AlwaysOn Availability Groups: Local Windows
Server Failover Clustering service started. This
is an informational message only. No user
41051 10 action is required.
AlwaysOn Availability Groups: Waiting for local
Windows Server Failover Clustering node to
start. This is an informational message only. No
41052 10 user action is required.
AlwaysOn Availability Groups: Local Windows
Server Failover Clustering node started. This is
an informational message only. No user action
41053 10 is required.
AlwaysOn Availability Groups: Waiting for local
Windows Server Failover Clustering node to
come online. This is an informational message
41054 10 only. No user action is required.
AlwaysOn Availability Groups: Local Windows
Server Failover Clustering node is online. This
is an informational message only. No user
41055 10 action is required.
Availability replica '%.*ls' of availability group
'%.*ls' cannot be brought online on this SQL
Server instance. Another replica of the same
41056 16 availability group is already online on the local
Windows Server Failover Clustering (WSFC)
node. Each WSFC node

AlwaysOn: The local replica of availability


group '%.*ls' is starting. This is an
informational message only. No user action is
41058 10 required.
AlwaysOn: Availability group '%.*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
41059 10 required.
The Cyclic Redundancy Check (CRC) value
generated for the retrieved availability group
configuration data from the Windows Server
Failover Clustering (WSFC) store does not
match that stored with the data for the
41060 16 availability group with ID '%.*ls'. The av
AlwaysOn: The local replica of availability
group '%.*ls' is stopping. This is an
informational message only. No user action is
41061 10 required.
The ID of availability group '%.*ls' in local data
store is inconsistent with that in the Windows
Server Failover Clustering (WSFC) data store.
The availability group may have been dropped
and recreated while the SQL Server instance
41062 16 was offline, or while
Windows Server Failover Clustering (WSFC)
detected that the availability group resource
with ID '%.*ls' was online when the availability
41063 16 group was not actually online. The attempt to
synchronize the WSFC resource state with the
availability group state f

Cannot bring the Windows Server Failover  In DOS prompt, run “Net helpmsg” on the %d value, and
Clustering (WSFC) resource (ID '%.*ls') online proceed accordingly.
(Error code %d). The WSFC service may not be
running or may not be accessible in its current
state, or the WSFC resource may not be in a
41066 16 state that could accept the r
The existence of availability group data for the
availability group '%.*ls' in the Windows Server
Failover Clustering (WSFC) store could not be
determined. The local WSFC node may be
down, or a previous CREATE AVAILABILITY
41069 16 GROUP or DROP AVAILABILITY GROU
Configuration data for the availability group
with Windows Server Failover Clustering
(WSFC) resource ID '%.*ls' is not found in the
WSFC data store. The availability group may
have been dropped, or a previous CREATE
41070 16 AVAILABILITY GROUP or DROP AVAILABILI
Cannot read the persisted configuration of
AlwaysOn availability group with
corresponding Windows Server Failover
Clustering (WSFC) resource ID '%.*ls'. The
persisted configuration is written by a higher-
version SQL Server that hosts the primary
41071 16 availabi
The ID of availability group '%.*ls' in local data
store does not exist in the Windows Server
Failover Clustering (WSFC) data store. The
availability group may have been dropped but
the current WSFC node was not notified. To
41072 16 resolve this error, try to r
The database '%.*ls' cannot be removed from
availability group '%.*ls'. This database does
41073 16 not belong to the availability group.
AlwaysOn: The local replica of availability  This is an informational message only. No user action is
group '%.*ls' is preparing to transition to the required
primary role in response to a request from the
Windows Server Failover Clustering (WSFC)
cluster. This is an informational message only.
41074 10 No user action is required
AlwaysOn: The local replica of availability
group '%.*ls' is preparing to transition to the
resolving role in response to a request from
the Windows Server Failover Clustering (WSFC)
cluster. This is an informational message only.
41075 10 No user action is requir
AlwaysOn: Availability group '%.*ls' is going
offline because it is being removed. This is an
informational message only. No user action is
41076 10 required.
Failed to delete SQL Server instance name to
Windows Server Failover Clustering node name
map entry for the local availability replica of
availability group '%.*ls'. The operation
encountered SQL Server error %d and has
41080 16 been terminated. Refer to the SQL
Failed to destroy the Windows Server Failover
Clustering group corresponding to availability
group '%.*ls'. The operation encountered SQL
Server error %d and has been terminated.
Refer to the SQL Server error log for details
41081 16 about this SQL Server error
AlwaysOn Availability Groups startup has been
41089 10 cancelled, because SQL Server is shutting
down. This is an informational message only.
No user action is required.
AlwaysOn: The local replica of availability
group '%.*ls' is going offline because either the
lease expired or lease renewal failed. This is an
informational message only. No user action is
41091 10 required.
AlwaysOn: The availability replica manager is
going offline because %ls. This is an
informational message only. No user action is
41092 10 required.
AlwaysOn: The local replica of availability
group '%.*ls' is going offline because the
corresponding resource in the Windows Server
Failover Clustering (WSFC) cluster is no longer
online. This is an informational message only.
41093 10 No user action is required.
AlwaysOn: The local replica of availability
group '%.*ls' is restarting because the existing
primary replica restarted or the availability
group failed over to a new primary replica. This
is an informational message only. No user
41094 10 action is required.
AlwaysOn: Explicitly transitioning the state of
the Windows Server Failover Clustering (WSFC)
resource that corresponds to availability group
'%.*ls' to Failed. The resource state is not
consistent with the availability group state in
41095 10 the instance of SQL
AlwaysOn: The local replica of availability
group '%.*ls' is being removed. The instance of
SQL Server failed to validate the integrity of
41096 10 the availability group configuration in the
Windows Server Failover Clustering (WSFC)
store. This is expected if th

AlwaysOn: The local replica of availability


group '%.*ls' is going offline. This replica failed
to read the persisted configuration because of
a version mismatch. This is an informational
41097 10 message only. No user action is required.
AlwaysOn: The local replica of availability
group '%.*ls' is restarting, because it failed to
read the persisted configuration. This is an
informational message only. No user action is
41098 10 required.
AlwaysOn: The local replica of availability
group '%.*ls' is going offline. This replica failed
to read the persisted configuration, and it has
exhausted the maximum for restart attempts.
This is an informational message only. No user
41099 10 action is required.
The availability group '%.*ls' and/or its local
availability replica does not exist. Verify that
the specified availability group name is correct,
and that the local availability replica has joined
41100 16 the availability group, then retry the operation.
The availability group with Windows Server
Failover Clustering resource ID '%.*ls' and/or
its local availability replica does not exist.
Verify that the specified availability resource ID
is correct, and that the local availability replica
41101 16 has joined the
Failed to persist configuration data of
availability group '%.*ls' in the Windows Server
41102 10 Failover Clustering (WSFC) cluster. The local
availability replica either is not the primary
replica or is shutting down.

Startup of the AlwaysOn Availability Replica


Manager has been terminated, because the
'FixQuorum' property of Windows Server
Failover Clustering (WSFC) is not present. The
prerequisite QFE hotfix, KB 2494036, might not
41103 10 yet be installed on your Windows Ser
Failover of the availability group '%.*ls' to the
local replica failed because the availability
group resource did not come online due to a
previous error. To identify that error, check the
SQL Server error log and the Windows Server
41104 16 Failover Cluster logs
Cannot create an 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
41106 16 unique, the

You might also like