Troubleshooting SQL Server Alwayson v1 0

SQL Server AlwaysOn errors (related to Availability Groups)
error
957
severi
ty
17
976
14
978
979
14
14
description
Database '%.*ls' is enabled
for database mirroring or
has joined an availability
group. The name of the
database cannot be
changed.
The target database,
'%.*ls', is participating in
an availability group and is
currently not accessible for
queries. Either data
movement is suspended or
the availability replica is
not enabled for read
access. To allow read-only
access to this and other
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 Online.
The target database
('%.*ls') is in an availability
group and currently does
not allow read only
connections. For more
If
dm_hadr_availability_replica_states.role_desc=3(INVALID)
, then check service broker. Because Availability group is
using Service Broker to communicate between SQL Server
then need to check Service Broker first. Open
SSMS>Server Objects > Endpoints, there are two
Service Broker folder>Expand both, and if the state is
Stopped or Disabled, then can change the state to
Started.
982
1408
1409
information about
application intent, see SQL
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 access. Wait for
14 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 backups from
16 the principal/prim
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
1465
16
1466
16
1467
1468
16
16
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 or in an
availability group.
Database "%.*ls" is readonly on one of the server
instances which is
incompatible with
participating in database
mirroring or in an
availability group. Set the
database to read-write
mode, and retry the
operation.
is in emergency or suspect
mode on one of the
partners which is
incompatible with
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
1469
16
1480
10
1488
1833
16
16
availability group. Some

operations are not allowed
on a database that is
participating in a database
mirroring session or in an
availabilit
Database "%.*ls" is an
auto-close database on one
of the partnerswhich is
incompatible with
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
only. No user action is
required.
is in single user mode
which is incompatible with
mirroring or in an
availability group. Set
database to multi-user
mode, and retry the
operation.
File '%ls' cannot be reused
until after the next BACKUP
LOG operation. If the
database is participating in
3104
an availability group, a
dropped file can be reused
only after the truncation
LSN of the primary
availability replica has
passed 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 the
database from its
16 availability gro
3752
5529
The database '%.*ls' is

currently joined to an
availability group. Before
you can drop the database,
you need to remove it from
16 the availatility group.
16 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
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
as null, then this may be due to earlier meta-data when
database was part of an AG so stop SQL Server, rename
the database files and start SQL Server. Then you should
be able to remove the database.
10786
13251
16
10
19401
19403
16
16
file 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 want to modify.
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://systemaddress:port'. For
information about the
correct routing URL format,
see the 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'
19405
19406
19407
can be added to this list. To

get 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 possible
16 owners and try ag
The state of the local
availability replica in
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
10 availabi
The lease between
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
16 availability group is fail
19452
16
19453
16
19454
19455
16
16
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
related network
configuration, then retry
with Windows Server
port %hu failed to start
with this error: %u. Verify
network and cluster
configuration and logs.
with Windows Server
port %hu failed to stop with
this error: %u. Verify
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
19456
19458
19460
network for the cluster with

an IPv4 subnet, and try to
create the listener.
None 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
16 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 to configure the
16 availability group listener.
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
16 create it again config
Added a new IP address (with different subnet) manually

to the existing Listener [to be tested].
19468
16
19469
16
19477
16
19486
21872
16
16
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
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 listener.
'%.*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.
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
availability group listener
associated with Virtual
21880
16
21882
16
21883
21884
16
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
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
HADRon Virtual Network
Name.
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'.
the health of the
availability group
associated with publisher
database '%s' failed with
error '%d', error message
21887
16
21892
16
33445
16
33446
16
'%s'.
whether the publisher
database '%s' belonged to
an availability group failed
with error '%d', error
message '%s'.
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.',
The database '%.*s' is a
readable secondary
database in an availability
group and cannot be
enabled for FILESTREAM
non-transacted 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 the
server instance that hosts
the pr
33449
10
33450
10
35202
35205
10
16
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
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
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
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. Check the SQL
35206
35207
35210
A connection timeout has

occurred on a previously
established connection to
availability replica '%ls'
with id [%ls]. Either a
networking or a firewall
issue exists or the
availability replica has
transitioned to the
10 resolving role.
Connection attempt on
availability group id '%ls'
from replica id '%ls' to
replica id '%ls' failed
because of error %d,
16 severity %d, state %d.
16 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
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
Server.
CREATE LOGIN [NT AUTHORITY\SYSTEM] FROM WINDOWS
WITH DEFAULT_DATABASE=[master],
DEFAULT_LANGUAGE=[us_english];
ALTER SERVER ROLE [sysadmin] ADD MEMBER [NT
AUTHORITY\system];
35212
35213
35217
and availability 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
Change one of the existing
16 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
synchronous-commit
16 replicas to th
16 The thread pool for
Groups was unable to start
a new worker thread
because there are not
enough available worker
threads. This may degrade
Groups performance. Use
the "max worker threads"
35220
35221
35222
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 cluster
16 node, or the local cluster
operation. AlwaysOn
manager is disabled on this
instance of SQL Server.
Enable AlwaysOn
Availability Groups, by
using the SQL Server
Configuration Manager.
Then, restart the SQL
16 Server service, and retry t
16 Could not process the
operation. AlwaysOn
Availability Groups does not
have permissions to access
the Windows Server
Failover Clustering (WSFC)
cluster. Disable and reenable AlwaysOn
Availability Groups by using
the SQL Server
35223
35224
35225
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
16 availability group is %d.
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 Server
16 instance to reload
operation. The instance of
SQL Server is running
under WOW64 (Windows
32-bit on Windows 64-bit),
which does not support
Groups. Reinstall SQL
Server in the native 64-bit
edition, and re-enable
16 AlwaysOn Availab
35226
16
35228
16
35229
16
35233
35237
16
16

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 service, and retry the
operation.
The attempt to set the
failure condition level for
failed. The specified level
value is out of the valid
range [%u, %u]. Reenter
the command specifying a
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 a
valid health check timeout
value.
Cannot create an
availability group
containing %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.
35238
35239
35240
Reenter the command,

specifying this server
instance to host one of the
replicas. This replica will be
the 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,
16 then retry 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, or the
database has not joined
16 the availab
16 Database '%.*ls' cannot be
joined to or unjoined from
This operation is not
supported on the primary
replica of the availability
group.
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.
If this replica can be made a secondary, then fail over
thus making it a secondary, and then drop replica when in
this secondary role. TSQL is ALTER 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.
35242
35243
35244
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
16 command.
Failed to set resource
property '%.*ls' for
The operation encountered
SQL Server error %d.
When the cause of the
error has been resolved,
retry the ALTER
AVAILABILITY GROUP
16 command later.
'%.*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
availability group, then
16 retry the operati
35246
16
35247
16
35249
16
35254
16
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 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 %d).
An attempt to add or join a
system database, '%.*ls', to
an availability group failed.
Specify 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
information, see the ALTER
AVAILABILITY G
35257
16
35259
16
35260
16
35261
16
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
configured partnerconnection parameters
Database '%.*ls' is already
participating in a 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 is that the
availability group
Attempt to perform an
Groups operation on a
system database, '%ls',
failed. System databases
are not supported by
Groups.
35262
17
35264
10
35265
35266
10
10
Skipping the default

startup of database '%.*ls'
because the database
belongs to an availability
group (Group ID: %d). The
database will be started by
the availability group. This
is an informational
message only. No user
action is required.
Groups data movement for
database '%.*ls' has been
suspended for the following
reason: "%S_MSG" (Source
ID %d; Source string:
'%.*ls'). To resume data
movement on the
database, you will need to
resume the database
manually. For infor
Groups data movement for
database '%.*ls' has been
resumed. This is an
required.
Groups connection with
%S_MSG database
established for %S_MSG
database '%.*ls' on the
Replica ID: {%.8x-%.4x%.4x-%.2x%.2x-%.2x%.2x
Check SQL and Windows logs for additional messages if

expecting database to start.
Link redirects to http://msdn.microsoft.com/enus/library/ff877956.aspx and the mention steps should be

followed to resume data movement.
35267
35275
35276
%.2x%.2x%.2x%.2x}. This
is an informational
action is
Groups connection with
%S_MSG database
terminated for %S_MSG
database '%.*ls' on the
Replica ID: {%.8x-%.4x%.4x-%.2x%.2x-%.2x%.2x
%.2x%.2x%.2x%.2x}. This
is an informational
10 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.
16 Restore the database
17 Failed to allocate and
schedule an AlwaysOn
Availability Groups task for
database '%ls'. Manual
intervention may be
required to resume
synchronization of the
database. If the problem
35279
16
35280
16
35281
35282
16
16
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
the primary replica.
'%.*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 an availability group,
then retry the ope
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 the
operation.
Availability replica '%.*ls'
cannot be added to
35283
35284
35287

already contains an
availability replica with the
specified name. Verify that
the availability replica
name and the availability
group name are correct, t
cannot be removed from
The availability group does
not contain an availability
replica with the specified
name. Verify that the
availability replica name is
correct, then retry the
16 operation.
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
16 is currently hostin
16 AlwaysOn Availability
Groups transport for
"%.*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
35288
35299
41039
mismatch. The database

replica has been put in
Groups log apply for
"%.*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 SUSPENDED state.
16 Resume the availabil
Nonqualified transactions
are being rolled back in
database %.*ls for an
Groups state change.
Estimated rollback
completion: %d%%. This is
an informational message
10 required.
An availability group replica
already exists on the
Clustering (WSFC) node
'%.*ls'. Each WSFC node
can contain only one
replica of an availability
group. Please choose
another WSFC node to host
16 the new replica.
41040
41042
41043
Failed to remove the

availability group replica
'%.*ls' from availability
group '%.*ls'. The
availability group does not
contain a replica with the
specified name. Verify the
availability group and
replica names and then
16 retry the operation.
'%.*ls' already exists. This
error could be caused by
a previous failed
CREATE AVAILABILITY
GROUP or DROP
AVAILABILITY GROUP
operation. If the
availability group name you
specified is correct, try
dropping the availability
16 group a
For availability group
'%.*ls', the value of the
name-to-ID map entry is
invalid. The binary value
should contain a Windows
(WSFC) resource ID, a
WSFC group ID, and their
corresponding lengths in
characters. The availability
16 g
If AG still exists, DROP AVAILABILITY GROUP.

Open regedit, backup the entry from the old Availability
Group that starts with HADR_Ag_???? key, then delete this
key [to be tested].
Try with new name for Availability Group.
41044
16
41045
16
41046
41048
16
10
Availability group name to

ID map entry for
cannot be found in the
Clustering (WSFC) store.
The availability group name
may be incorrect, or the
availability group may not
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 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 names
specified are correct.
Groups: Local Windows
service has become
unavailable. This is an
41049
10
41050
10
41051
10
41052
41053
10
10

required.
node is no longer online.
This is an informational
action is required.
Groups: Waiting for local
Clustering service to start.
action is required.
service started. This is an
required.
Clustering node to start.
action is required.
node started. This is an
41054
10
41055
10
41056
16
41058
10

required.
Clustering node to come
online. This is an
required.
node is online. This is an
required.
Availability replica '%.*ls' of
cannot be brought online
on this SQL Server
instance. Another replica
of the same availability
group is already online on
the local Windows Server
node. Each WSFC node
AlwaysOn: The local replica
of availability group '%.*ls'
is starting. This is an
required.
41059
10
41060
16
41061
41062
10
16
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
required.
The Cyclic Redundancy
Check (CRC) value
generated for the retrieved
availability group
configuration data from the
Clustering (WSFC) store
does not match that stored
with the data for the
availability group with ID
'%.*ls'. The av
is stopping. This is an
required.
The ID of availability group
'%.*ls' in local data store is
inconsistent with that in
the Windows Server
data store. The availability
group may have been
dropped and recreated
while the SQL Server
41063
41066
41069
instance was offline, or

while
Clustering (WSFC) detected
that the availability group
resource with ID '%.*ls' was
online when the availability
group was not actually
online. The attempt to
synchronize the WSFC
resource state with the
16 availability group state f
Cannot bring the Windows
(WSFC) resource (ID '%.*ls')
online (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
state that could accept the
16 r
The existence of
availability group data for
'%.*ls' in the Windows
(WSFC) store could not be
determined. The local
WSFC node may be down,
or a previous CREATE
AVAILABILITY GROUP or
16 DROP AVAILABILITY GROU
In DOS prompt, run Net helpmsg on the %d value, and

proceed accordingly.
41070
16
41071
16
41072
41073
16
16
Configuration data for the

availability group with
Clustering (WSFC) resource
ID '%.*ls' is not found in the
WSFC data store. The
availability group may have
been dropped, or a
previous CREATE
AVAILABILITY GROUP or
DROP AVAILABILI
Cannot read the persisted
configuration of AlwaysOn
availability group with
corresponding Windows
(WSFC) resource ID '%.*ls'.
The persisted configuration
is written by a higherversion SQL Server that
hosts the primary availabi
The ID of availability group
'%.*ls' in local data store
does not exist in the
Clustering (WSFC) data
store. The availability
group may have been
dropped but the current
WSFC node was not
notified. To resolve this
error, try to r
The database '%.*ls' cannot
be removed from
This database does not
41074
41075
41076
belong to the availability

group.
is preparing to transition to
the primary role in
response to a request
from the Windows
Server Failover
Clustering (WSFC)
cluster. This is an
10 required
is preparing to transition to
the resolving role in
response to a request from
the Windows Server
cluster. This is an
10 requir
AlwaysOn: Availability
group '%.*ls' is going offline
because it is being
removed. This is an
10 required.
This is an informational message only. No user action is

required
41080
16
41081
16
41089
10
41091
10
Failed to delete SQL Server

instance name to Windows
node name map entry for
the local availability replica
of availability group '%.*ls'.
SQL Server error %d and
has been terminated.
Refer to the SQL
Failed to destroy the
Clustering group
corresponding to
Refer to the SQL Server
error log for details about
this SQL Server error
Groups startup has been
cancelled, because SQL
Server is shutting down.
action is required.
is going offline because
either the lease expired or
lease renewal failed. This is
required.
41092
10
41093
10
41094
10
41095
10
AlwaysOn: The availability

replica manager is going
offline because %ls. This is
required.
is going offline because the
corresponding resource in
the Windows Server
cluster is no longer online.
action is required.
is restarting because the
existing primary replica
restarted or the availability
group failed over to a new
primary replica. This is an
required.
AlwaysOn: Explicitly
transitioning the state of
the Windows Server
resource that corresponds
to availability group '%.*ls'
to Failed. The resource
state is not consistent with
the availability group state
in the instance of SQL
41096
10
41097
10
41098
41099
10
10

is being removed. The
failed to validate the
integrity of the availability
group configuration in the
Clustering (WSFC) store.
This is expected if th
is going offline. This replica
failed to read the persisted
configuration because of a
version mismatch. This is
required.
is restarting, because it
configuration. This is an
required.
is going offline. This replica
configuration, and it has
exhausted the maximum
for restart attempts. This is
41100
41101
41102
required.
'%.*ls' and/or its local
availability replica does not
exist. Verify that the
specified availability group
name is correct, and that
has joined the availability
group, then retry the
16 operation.
The availability group with
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
16 replica has joined the
Failed to persist
configuration data of
availability group '%.*ls' in
the Windows Server
cluster. The local
availability replica either is
not the primary replica or is
10 shutting down.
41103
10
41104
16
41106
41107
16
16
Startup of the AlwaysOn

Availability Replica
Manager has been
terminated, because the
'FixQuorum' property of
Clustering (WSFC) is not
present. The prerequisite
QFE hotfix, KB 2494036,
might not 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
Cluster logs
Cannot create an
availability replica for
An availability replica of the
already exists on this
Verify that the specified
availability group name is
correct and unique, the
Availability group '%.*ls'
failed to create necessary
events for the WSFC Lease
mechanism. Windows
returned error code (%d)
41108
41109
41110
when obtaining handles for

Lease events. Resolve the
windows error and retry the
availability group
operation.
removing availability group
'%.*ls'. The DROP
AVAILABILITY GROUP
command removed the
availability group
configuration from the local
metadata. However, the
attempt to remove this
configuration from the
16 Clust
Could not enqueue a task
(SQL OS error: 0x%x) for
process actions for the
Most likely, the instance of
SQL Server is low on
resources. Check the SQL
Server error log to
determine the cause of the
failure. Retry the operation
17 l
replica manager is starting.
10 action is required.
41111
10
41112
16
41113
16
41114
41115
16
16

replica manager is waiting
for the instance of SQL
Server to allow client
connections. This is an
required.
A Windows Server Failover
Clustering (WSFC) API
required by availability
groups has not been
loaded. AlwaysOn
manager is not enabled on
the local instance SQL
Server. If the server
instance is running an
edition of SQL Server t
Cannot failover availability
group '%.*ls' to this
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
Cannot create an
availability group named
'%.*ls' because it already
exists in a system table.
Cannot create the
41116
16
41117
16
41118
16
41119
16
41121
10
'%.*ls' because its

availability group ID (ID:
'%.*ls') already exists in a
system table.
Cannot create an
'%.*ls' with replica ID
'%.*ls' because this ID
already exists in a system
table.
Cannot map local database
ID %d to the availability
database ID '%.*ls' within
This database is already
mapped to an availability
group.
Cannot map database ID
%d to the availability
database ID '%.*ls' within
Another local database, (ID
%d). is already mapped to
this availability database.
Could not find the
availability group ID %d in
the system table.
The local availability replica
cannot accept signal '%s' in
its current replica role, '%s',
and state (configuration is
%s in Windows Server
Failover Clustering store,
local availability replica has
%s joined). The availabil
41122
16
41126
16
41127
16
41128
16

is already the primary
replica of the availability
group. To failover this
availability group to
another instance of SQL
Server, run the failover c
Operation on the local
availability replica of
failed. The local copy of
configuration does not exist
or has not been initialized.
Verify that the availability
group exists and that the
local copy of the
Attempt to set database
mapping state where the
local database id %d is not
mapped to any availability
group.
Failed to perform database
operation '%s' on database
'%.*ls' (ID %d) in
The database might be in
an incorrect state for the
operation. If the problem
persists, you may need to
restart the SQL Server
instance.
41129
16
41130
16
41131
41132
10
16
Failed to schedule or
execute database
operation '%s' on database
'%.*ls' (Database ID: %d) in
(SQL OS error: %d). The
instance of SQL Server may
have insufficient resources
to carry out the database
operation. If the problem p
Operation '%s' on a
database '%.*ls' (Database
ID: %d) in availability group
'%.*ls' failed with SQL
Server error %d (Error
details: "%.*ls"). The
operation has been rolled
back. See previous error
messages in the SQL
Server error log for more
details.
Failed to bring availability
group '%.*ls' online. The
operation timed out. Verify
that the local Windows
(WSFC) node is online.
Then verify that the
availability group resource
exists in the WSFC cluster.
If the problem persis
Cannot join database
'%.*ls' to availability group
'%.*ls'. The specified
database does not belong
to the availability group.
41133
41134
41135
Verify the names of the

database and the
availability group, and retry
the command specifying
the correct names.
Cannot remove database
'%.*ls' from availability
group '%.*ls'. Either the
database does not belong
to the availability group, or
the database has not
joined the group. Verify the
database and availability
group names, and retry the
10 command.
Cannot bring the
online. The local instance
was not the previous
primary replica when the
availability group went
offline, not all databases
are synchronized, and no
force failover command
was issued on the local
16 availability r
Startup of AlwaysOn
manager failed due to SQL
Server error %d. To
determine the cause of this
error, check the SQL Server
error log for the preceding
10 error.
41136
16
41137
10
41138
41139
17
10
Failed to join the

availability replica to
because the group is not
online. Either bring the
availability group online, or
drop and recreate it. Then
retry the join operation.
Abandoning a database
operation '%ls' on
availability database '%.*ls'
of availability group '%.*ls'.
The sequence number of
local availability replica has
changed (Previous
sequence number: %u,
current sequence number:
%u). This is an
informational mes
Cannot accept AlwaysOn
Availability Groups
operation operation on
database '%.*ls' of
The database is currently
processing another
operation that might
change the database state.
Retry the operation later. If
the condition per
Failed to set database
information for availability
group %.*ls. The local
availability replica is not
the primary replica, or it is
shutting down. This is an
41140
41141
41142
required.
cannot process the ALTER
AVAILABILITY GROUP
command, because the
local availability replica is
not the primary replica.
Connect to the server
instance that is currently
hosting the primary replica
16 of this availability group, an
Failed to set availability
group database information
for availability group %.*ls.
is not the primary, or is
shutting down. This is an
16 required.
16 The availability replica for
availability group '%.*ls' on
this instance of SQL Server
cannot become the primary
replica. One or more
databases are not
synchronized or have not
joined the availability
group, or the WSFC cluster
was started in Force
Quorum
Check if *_FailoverCluster_health_XeLogs confirm that the

cluster was started in forced_quorum mode
(forced_quorum True in
availability_replica_automatic_failover_validation event).
o When a cluster is started in forced_quorum mode
(net.exe start clussvc /forcequorum, OR Failover
Cluster Manager>left pane>right-click Windows
cluster>choose Force Cluster Start>Confirm by
clicking Yes.) on primary replica, the availability
group is required to be started by issuing command
ALTER AVAILABILITY GROUP <AGNAME>
FORCE_FAILOVER_ALLOW_DATA_LOSS;. Because
this is the original primary, despite issuing force
41143
41144
Cannot process the

operation. The local replica
of availability Group '%.*ls'
is in a failed state. A
previous operation to read
or update persisted
configuration data for the
availability group has
failed. To recover from this
16 failure, either restart
16 The local availability replica
is in a failed state. The
replica failed to read or
update the persisted
configuration data (SQL
Server error: %d). To
recover from this failure,
either restart the local
allow data loss, NO data loss occurs

When a cluster is started in forced_quorum mode
on secondary replica, first check
sys.dm_hadr_database_replica_cluster_states.is_fail
over_ready on secondary. If this value is 1, and be
assured no data loss will occur. If this value is not 1
(for example because its asynchronous commit),
then can check
sys.dm_hadr_database_replica_states.last_commit_
time, so as to know estimate start time of data
loss. The
sys.dm_hadr_database_replica_states.last_hardene
d_lsn value may be used to consider other
secondaries for failover. Then can initiate failover
with ALTER AVAILABILITY GROUP <AGNAME>
FORCE_FAILOVER_ALLOW_DATA_LOSS; on
secondary.
41145
10
41146
16
41147
41148
10
16
Windows Server Failov

'%.*ls'. The database has
already joined the
availability group. This is
an informational message.
No user action is required.
Failed to bring Availability
Group '%.*ls' online. The
Clustering (WSFC) service
may not be running, or it
may not be accessible in its
current state. Please verify
the local WSFC node is up
and then retry the
operation.
Groups was not started
because %ls. This is an
informational message. No
user action is required.
Cannot add or join
database '%.*ls' to
The database does not
exist on this instance of
SQL Server. Verify the
database name and that
the database exists on the
server instance. Then retry
the operation, specifying
41149
16
41150
16
41151
41152
16
16
the correc
Operation on the
has been cancelled or
terminated, either because
of a connection timeout or
cancellation by user. This
is an informational
message. No user action is
required.
Failed to take availability
group '%.*ls' offline. The
Clustering (WSFC) service
may not be running, or it
may not be accessible in its
current state. Verify the
local WSFC node is up and
then retry the operation.
Error accessing the
Availability Groups
manager. The local
Availability Groups
manager has not been
initialized. Wait until the
Availability Groups
manager is in a state that
allows access, and retry
the operation.
Failed to create availability
group '%.*ls'. The
operation encountered SQL
Server error %d and has
Check this document for error number mentioned in %d.
41153
41154
41155
been rolled back. Check

the SQL Server error log for
more details. When the
cause of the error has been
resolved, retry CREATE
AVAILABILITY GROUP
command
group '%.*ls'. The
Server error %d. An
attempt to roll back the
operation failed. Check the
SQL Server error log for
more details. Then execute
the DROP AVAILABILITY
GROUP command to clean
16 up any
group '%.*ls' to this SQL
Server instance. The
availability group is still
being created. Verify that
group name is correct.
Wait for CREATE
AVAILABILITY GROUP
command to finish, then
16 retry the op
16 Cannot failover availability
The availability group is
being dropped. Verify that
group name is correct. The
41156
41157
41158
availability group may need

to be recreated if the drop
operation was
Cannot drop availability
group '%.*ls' from this
either being dropped, or
is being removed from the
availability group. Verify
that the specified
16 availability group name is
Cannot remove the local
availability replica from
from this instance of SQL
Server. The availability
group is either being
dropped, or the local
availability replica is being
disjoined. Verify that the
16 specified availability g
Failed to join local
has been rolled back.
Check the SQL Server error
log for more details. When
the cause of the error has
16 been resolved, retry the A
Check for SQL/Windows messages around same time.
41159
16
41160
16
41161
41162
16
16
Failed to join local

SQL Server error %d. An
attempt to rollback the
operation failed. Check
more details. Run DROP
AVAILABILITY GROUP
command to cl
Failed to designate the
local availability replica of
availability group '%.*ls' as
the primary replica. The
Server error %d and has
been terminated. Check
the preceding error and the
more details about
Failed to validate the Cyclic
Redundancy Check (CRC)
of the configuration of
SQL Server error %d, and
the availability group has
been taken offline to
protect its configuration
and the consistency of
Failed to validate sequence
number of the
configuration of availability
group '%.*ls'. The inmemory sequence number
41163
41164
41165
does not match the

persisted sequence
number. The availability
group and/or the local
availability replica will be
restarted automatical
waiting for the local
availability group '%.*ls' to
transition to the primary
role. The operation
encountered SQL OS error
%d and has been
terminated. Verify that the
16 Clustering (WS
transition to the resolving
role. The operation
encountered SQL OS error
%d and has been
16 Clustering (
16 A timeout error occurred
while waiting to access the
local availability replica of
The availability replica is
currently being accessed
by another operation. Wait
for the in-progress
41166
41167
41168
operation to complete, and

then retry the
waiting to access the local
SQL OS error %d, and has
been terminated. Verify
that the local availability
replica is in the correct
16 state, and then retr
attempting to access
availability replica '%.*ls' in
The availability replica is
not found in the availability
group configuration. Verify
and availability replica
16 names are
attempting to access
availability replica with ID
'%.*ls' in availability group
'%.*ls'. The availability
replica is not found in the
availability group
configuration. Verify that
the availability group name
16 and availability repl
41169
41170
41171

attempting to access the
availability group database
with ID '%.*ls' in availability
group '%.*ls'. The
availability database is not
found in the availability
group configuration. Verify
16 name and avail
Post-online processing for
Either post-online
processing has already
completed, the local
availability replica is no
longer the primary replica,
or the availability group is
being dropped. This is an
10 infor
group '%.*ls', because a
Cluster (WSFC) group with
the specified name already
exists. The operation has
been rolled back
successfully. To retry
creating an availability
group, either remove or
16 rename
41172
16
41173
16
41176
10
41177
16

dropping availability group
'%.*ls' from Windows
(WSFC) cluster and from
the local metadata. The
OS error %d, and has been
specified availability gr
removing the local
SQL OS error %d, and has
that the specified
correct, and then retry the
command
Failed to acquire exclusive
access to local availability
group configuration data
(SQL OS error: %d). If the
problem persists, you
might need to restart the
The availability replica of
group '%.*ls' is being
dropped. Wait for the
completion of the drop
command and retry the
operation later.
In DOS prompt, run Net helpmsg on the %d value, and

41178
16
41179
16
41180
41181
16
16
Cannot drop availability

group '%.*ls' from this SQL
Server instance. The
availability group is
currently being created.
Verify that the specified
correct. Wait for the
current operation to
complete, then retry the
command if
Cannot remove the local
from this instance of SQL
Server. The availability
group is currently being
created. Verify that the
name is correct. Wait for
the current operati
Attempt to access nonexistent or uninitialized
availability group with ID
'%.*ls'. This is usually an
internal condition, such as
the availability group is
being dropped or the local
WSFC node has lost
quorum. In such cases, and
no user action is requir
did not become primary. A
concurrent operation may
have changed the state of
41182
41183
41184
the availability group in

Cluster. Verify that the
availability group state in
Windows Serv
Failed to set the local
availability group '%.*ls' as
joined in Windows Server
database. Either the local
availability replica is no
longer the primary, or the
WSFC service is not
16 accessible. Verify tha
Failed to modify availability
replica options for
Before the availability
group configuration could
be updated, the operation
encountered SQL Server
error %d. The operation
has been rolled back. Refer
16 to the SQL Server error
Failed to modify availability
replica options for
configuration has been
updated. However, the
Server error %d while
applying the new
configuration to the local
16 availability re
41185
10
41186
16
41187
41188
16
16
Replica option specified in

ALTER AVAILABILITY GROUP
'%.*ls' MODIFY DDL is same
is cached availability group
configuration.
cannot process an ALTER
AVAILABILITY GROUP
command at this time. The
availability group is still
being created. Verify that
group name is correct.
Wait for CREATE
AVAILABILITY GROUP
command to finis
cannot process an ALTER
AVAILABILITY GROUP
command at this time. The
availability group is being
dropped. Verify that the
name is correct. The
availability group may need
to be recreated if it was
failed to process %s-%s
command. The operation
encountered SQL Server
error %d before the
availability group
configuration could be
updated, and has been
rolled back. Refer to the
41189
41190
41191
details. Verify that

failed to process the %s-%s
command. The availability
group configuration has
been updated. However,
the operation encountered
SQL Server error %d while
applying the new
configuration to the local
16 availability replica, and has
failed to process %s-%s
command. The local
availability replica is not in
a state that could process
the command. Verify that
the availability group is
online and that the local
availability replica is the
16 primary replica, the
cannot become the primary
replica. The last-known
primary availability replica
is of a higher version than
the local availability
replica. Upgrade the local
instance of SQL Server to
16 the same
41192
17
41193
10
41194
41195
16
16
Creating and scheduling a

worker task for AlwaysOn
Availability Groups failed
due to lack of resources
(SQL OS error %d).
Processing of new actions
might be delayed or stalled
until the resource limits are
resolved. Reduce the
memory or thread count on
'%.*ls'. The database is in
the process of being
removed from the
availability group. When
the remove-database
operation completes, the
database will no longer be
joined to the availability
group. Then
availability replica for
complet post-online work.
SQL OS error %d and has
that the Windows Server
c
failed to process the WSFC
lease-renewal command.
41196
16
41199
16
41402
41403
16
16
lease is no longer valid to

process the lease renewal
command. Availability
replica lease expired. This
is an informational
message only. No user a
group '%.*ls', because a
Cluster (WSFC) group with
the specified name already
exists. An attempt to
rollback the operation
failed. Check the SQL
Server error log for more
details. To manually clean
The specified command is
invalid because the
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.
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.
Availability group is offline.
41404
16
41405
16
41406
16
41408
16
41410
16

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.
Availability group is not
ready for automatic
failover.
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 an
automatic failover. Possibly
the secondary replica is
unavail
In this availability group, at
least one secondary replica
has a NOT SYNCHRONIZING
synchronization state and
is not receiving data from
the primary replica.
least one synchronous
replica is not currently
synchronized. The replica
synchronization state could
be either SYNCHONIZING or
NOT SYNCHRONIZING.
41412
16
41414
16
41424
16
41428
16

least one availability
replica does not currently
have the primary or
secondary role.
least one secondary replica
is not connected to the
primary replica. The
connected state is
DISCONNECTED.
This secondary database is
not joined to the
availability group. The
configuration of this
secondary database is
incomplete. For information
about how to join a
secondary database to an
availability group, see SQL
This secondary replica is
not joined to the
availability group. For an
availability replica to be
successfully joined to the
availability group, the join
state must be Joined
Standalone Instance (1) or
Joined Failover Cluster (2).
For information about ho
SQL Server AlwaysOn (SQL Server Configuration Manager)

An error occurred while loading the
AlwaysOn High Availability properties
[return code: 0x80070005].
The AlwaysOn Availability Groups feature
requires the x86(non-WOW) or x64
Enterprise Edition of SQL Server 2012 (or
later version) running on Windows Server
2008 (or later version) with WSFC hotfix KB
2494036 installed. This SQL Server edition
and/or Windows Server System does not
meet one or more of the requirements
You may receive this error if you don't

have the appropriate permission. Try
right click SQL Server Configuration
Manager and select Run as
Administrator.
Verify OS is Windows 2008 or later
version.
If OS is Windows 2008 or Windows 2008
R2, install Windows hotfix KB 2494036, if
not already installed.
SQL Server AlwaysOn (New Availability Group wizard errors)
The current WSFC cluster

quorum vote configuration
is not recommended for this
availability group.
For more information, see
the following topic in SQL
Server Books Online:
http://go.microsoft.com/fwli
nk/?LinkId=224159.
When validating WSFC quorum vote configuration, the

AlwaysOn Availability Group Wizard shows a warning if
any of the following conditions are true:
o The cluster node that hosts the primary replica
does not have a vote. If this vote is not required
for that environment, then this message may be
ignored. Powershell command to check vote is
Get-ClusterNode | f1 Name, Nodeweight.
o A secondary replica is configured for automatic
failover and its cluster node does not have a vote.
If this vote is not required for that environment,
then this message may be ignored.
o KB2494036 is not installed on all cluster nodes
that host availability replicas. This patch is
required to add or remove votes for cluster nodes
in multi-site deployments. However, in single-site
deployments, it is usually not required and you
may safely ignore the warning.
o While setting up the availability group in the
wizard, you configured a replica to asynchronous
availability mode. This warning is only reported in
SQL 2012 RTM, not in SP1 of SQL 2012 RTM.
o While setting up the availability group in the
wizard, you configured a replica for manual
failover mode. This warning is only reported in SQL
2012 RTM, not in SP1 of SQL 2012 RTM.
Check the link. Redirects to
http://msdn.microsoft.com/en-us/library/hh270280.aspx
Checking for the database

files on the secondary
replica resulted in an error.
(Microsoft.SqlServer.Manage
ment.HadrTasks)
-----------------------------Program Location:
at
Microsoft.SqlServer.Manage
ment.Hadr.TestDatabaseFile
Existing.DoWork()
at
ment.TaskForms.SimpleWor
kItem.Run()
=================
=================
=
The following database files
already exist on the server
instance that hosts
secondary replica HAVM3\TEST1:
\\path\file.mdf
\\path\file_log.ldf
(Microsoft.SqlServer.Manage
ment.HadrTasks)
-----------------------------Program Location:
at
ment.Hadr.TestDatabaseFile
Existing.DoWork()
Check if database-file paths are identical on source and

on destination servers. If different, manual (rather than
using AG wizard) restore may be required with WITH
MOVE syntax.
SQL Server AlwaysOn (performance issues)
983
14
Unable to access database '%.*ls' because

its replica role is RESOLVING which does not
allow connections. Try the operation again
later.
3402
10
The database '%ls' is marked %ls and is in

a state that does not allow recovery to be
run.
Check SQL ERRORLOGs, event logs, etc.

for network, storage related messages
etc.
If the second %ls is RESTORING, then one

option is below.
1) Asked the customer to stop the SQL Server
Service.
2) Had the customer rename the actual files on
disk with a "_old" suffix so that the sql server
would not find them and have the db come up
suspect.
3) Asked the customer to start the SQL Server
Service.
Once the server came back up we were able to
delete the database.
4) Had the customer create a new database
with the same name and location as the original
database. Used the output from sysaltfiles to
verify this.
5) Had the customer stop the SQL Server
Service.
6) Had the customer rename these new
database files by appending a "_new" on the
end of the file.
7) Had the customer take the old database files
with the "_old" suffix and changed them back to
the original name.
8) Had the customer start the SQL Server
Service.
If KB2723814 not applied, then try the KB

workaround of suspend secondary replica
and then resume, so that AlwaysOn
knows that availability mode has
changed back to synchronous commit.
Check for associated errors like error

19476.
Check for associated errors like error

41009.
Net helpmsg on the %d value, and

May also be accompanied by MicrosoftWindows-FailoverClustering messages in
event log.
Check cluster log.
If there error is in cluster in Windows
Slow synchronization. Waittime for

HADR_SYNC_COMMIT grows anywhere from
500ms to 900ms (compared to less than
15-20 ms).
SQL Server AlwaysOn errors (other)
19471
19476
41009
16
16
16
The 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
The attempt to create the network name
and IP address for the listener failed. 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 WFSC cluster and validate the
network name and IP address with the
network administrator.
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,
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
http://msdn.microsoft.com/enus/library/jj870962.aspx (High Availability
and Disaster Recovery for SQL Server in
Windows Azure Virtual Machines).
41015
16
Failed to obtain the Windows Server

Failover Clustering (WSFC) node handle
(Error code %d). The WSFC service may
not be running or may not be accessible in
its current state, or the specified cluster
node name is invalid. For information
about this erro
Check if Windows cluster service is

running.
Net helpmsg on the %d value, and
SQL Server AlwaysOn errors (network)
TCP Provider, error: 0 - An operation on a

socket could not be performed because the
system lacked sufficient buffer space or
because a queue was full.
NetStat output may show hundreds of

entries in TIME_WAIT state leading to
buffer/port exhaustion
Add registry setting for MaxUserPort
http://support.microsoft.com/kb/196271
Add registry setting for
TCPTIMEWAITDELAY.
App/IIS restart, machine reboot are
additional options.
SQL Server AlwaysOn errors (Windows)
5057
Checked if IP is already in use

Check permission for cluster network
object CNO.
Depending on the resource type, this

generally requires involvement of
Windows team.
If this is a network name or an IP address
resource, then try creating a Client
Access Point with same name and IP if
possible, and see it comes online. If it
does not come online, then this requires
investigation by Windows team.
The cluster IP address is already in use.
5942
The resource failed to come online due to

the failure of one or more provider
resources.
Application errors
SQL Server AlwaysOn errors (cluster log)

[RES] Network Name <SPEPD_Tier2>:
Unable to update password for
computer account DCR-SPEPD on DC \\
DC-04.xxxx.org, status 5.
Status 5 is Access Denied

In Windows AD, check for CNO (cluster
network object) permissions.
For example, below to grant the "create
[RHS] Online for resource SPEPD_Tier2

failed.
computer objects" to the cluster virtual

host (virtual cluster name) for the OU in
Active Directory on "Computers" and
"DomainServer" OU that was created. [To
be tested]
Instructions [to be tested]
1) Log into the Domain Controller machine.
2) Select Start - Administrative Tools - Active
Directory users and computer.
--> Active Directory users and computer screen
displays.
3) Display-select advanced features.
4) Select the appropriate domain - Computers.
5) Verify that the cluster virtual hosts.
6) Select the appropriate domain - Computers right click - Properties.
--> Computers Properties screen appears.
7) Security tab-click the Advanced button.
--> Advanced Security for Computers "screen
appears.
8) If you have access permissions tab - cluster
virtual host registration registration no "Edit"
button if you choose the "add" button.
+ Case "add": conducted a check in the
"computer", click the "object type" button,
search for cluster virtual hosts.
--> [Permission entries on Computers] screen is
displayed.
9) Target: Select this object and all child objects
check the permission "create computer objects"
and click the "OK" button.
--> Returns to the advanced security for
Computers "screen.
10) Click "OK" button after clicking "the apply"
button.
--> Returns to the Computers Properties screen.

11) And click the "OK" button and exit the
Active Directory users and computer screen.
INFO [RES] Network Name: [NNLIB]

NetUserAdd object aglisten11 on DC:
\\DC.contoso.com, result: 8557
ERR [RES] Network Name: [NNLIB] Failed
to create Computer Object aglisten11 in
the Active Directory, error 8557
net helpmsg 8557 says "Your computer

could not be joined to the domain. You
have exceeded the maximum number of
computer accounts you are allowed to
create in this domain. Contact your
system administrator to have this limit
reset or increased."
SQL Server AlwaysOn (patching/updates in SQL 2012)

AG on Standalone Instance
Patching steps:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Patch the secondary replica (B)

Bring the secondary replica online (will be new version)
Log the original synchronization configurations for each replica. Change the secondary replica and primary
replica to Synchronous Commit mode, waiting for the secondary replica (B) to be synchronized.
a. This will ensure there is no data loss during failover.
b. You can check dashboard or dmv: dm_hadr_database_replica_states for the status
Issue a failover through SSMS or T-SQL to failover the AG to the secondary replica. So now the new primary
is B, the new secondary is A
Patch the original primary replica (A)
Bring the original primary replica (A) online (will be new version )
Wait for A to become Synchronized
Failover the AG back to A
Change each replicas synchronization mode to the original configurations you logged in step3.
Caveat list:
Before you patch, you can still keep automatic/manual failover setting no change. Just a reminder: if during
patching time, primary is down, automatic failover may fail if the secondary hasnt completed the patching.
If primary and secondary replicas are in multisubnet, your client may experience a little bit longer time of
disconnection or timeout during failover.
Please do remember to switch back to your original synchronization mode.
AG on FCIs (Failover Cluster Instances)

FCI on AG deployment Example
Primary replica(A): FCI1
o Node1 active
o Node2 - passive
Secondary Replica(B): FCI2
o Node3 active
o Node4 - passive
Choose between one of the following two options:
Longer downtime, less steps
(FCI rolling patching).
Patching steps (basic):
1. Patch Node4
2. Move FCI2 from
3. Patch Node3
4. Move FCI2 from
5. Patch Node2
6. Move FCI1 from
7. Patch Node1
8. Move FCI1 from
Node3 to Node4
Node4 to Node3
Node1 to Node2
Node2 to Node1
Optimized downtime, more steps

(Leverage AG failover patching).
Patching steps (optimized):

1. Patch Node4
2. Move FCI2 from Node3 to Node4
3. Patch Node3
5. Log the original synchronization configurations for each replica. Change the secondary replica and primary
replica to Synchronous Commit mode, waiting for the secondary replica (B) to be synchronized.
6. Manually failover AG from FCI1 to FCI2 (now the new primary is on FCI2, the new secondary is on FCI1)
7. Patch Node2
9. Patch Node1
10.Move FCI1 from Node2 to Node1
11.Manually failover AG from FCI2 back to FCI1
12.Change each replicas synchronization mode to the original configurations you logged in step #5.
Caveat list:
** Please use basic patching steps if primary and secondary are on different data centers/subnets **
FCI rolling patch guarantees zero data lost
Use synchronous commit secondary on a high latency network would impact OLTP performance
AG failover cross subnets might cause up to 20 seconds delay on client first connections.

Troubleshooting SQL Server Alwayson v1 0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Troubleshooting SQL Server Alwayson v1 0

Uploaded by

Copyright:

Available Formats

SQL Server AlwaysOn errors (related to Availability Groups)

availability group. Some

The database '%.*ls' is

Before you can drop the database, you need to remove it

can be added to this list. To

The availability group

network for the cluster with

Added a new IP address (with different subnet) manually

The listener with DNS name

Network Name '%s' has no

FILESTREAM File I/O access

dispatcher started up. If so,

A connection timeout has

If there is a login failed for domain\node$ account around

and availability replica

Configuration Manager. The

Could not process the

Reenter the command,

TSQL to unjoin is ALTER DATABASE db SET HADR OFF.

same name, then try the DROP AVAILABILITY GROUP.

Cannot complete this

Failed to create the

Skipping the default

Check SQL and Windows logs for additional messages if

Link redirects to http://msdn.microsoft.com/enus/library/ff877956.aspx and the mention steps should be

persists, you might need to

The availability group

mismatch. The database

Failed to remove the

If AG still exists, DROP AVAILABILITY GROUP.

Availability group name to

only. No user action is

only. No user action is

instance was offline, or

In DOS prompt, run Net helpmsg on the %d value, and

Configuration data for the

belong to the availability

This is an informational message only. No user action is

Failed to delete SQL Server

AlwaysOn: The availability

AlwaysOn: The local replica

Startup of the AlwaysOn

when obtaining handles for

AlwaysOn: The availability

'%.*ls' because its

Cannot failover availability

Verify the names of the

Failed to join the

Check if *_FailoverCluster_health_XeLogs confirm that the

Cannot process the

allow data loss, NO data loss occurs

Windows Server Failov

Check this document for error number mentioned in %d.

been rolled back. Check

availability group may need

Check for SQL/Windows messages around same time.

Failed to join local

does not match the

operation to complete, and

An error occurred while

An error occurred while

In DOS prompt, run Net helpmsg on the %d value, and

Cannot drop availability

the availability group in