Troubleshooting Alwayson v1 2

41046 16
AlwaysOn Availability Groups:

Local Windows Server Failover
Clustering service has become
unavailable. This is an
informational message only. No
41048 10 user action is required.
Clustering node is no longer
online. This is an informational
message only. No user action is
41049 10 required.
Waiting for local Windows Server
Failover Clustering service to
start. This is an informational
41050 10 required.
Clustering service started. This is
an informational message only.
41051 10 No user action is required.
Failover Clustering node to start.
This is an informational message
41052 10 only. No user action is required.
Clustering node started. This is an
Failover Clustering node to come
online. This is an informational
41054 10 required.
Clustering node is online. This is
an informational message only.
Availability replica '%.*ls' of
availability group '%.*ls' cannot
be brought online on this SQL
Server instance. Another replica
of the same availability group is
already online on the local
Windows Server Failover
Clustering (WSFC) node. Each
41056 16 WSFC node
AlwaysOn: The local replica of
availability group '%.*ls' is
starting. This is an informational
41058 10 required.
AlwaysOn: Availability group
'%.*ls' was removed while the
availability replica on this instance
41059 10 of SQL Server was offline. The
local replica will be removed now.
only. No user action is 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
41060 16 '%.*ls'. The av
stopping. This is an informational
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 was
41062 16 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 availability group
41063 16 state f
Cannot bring the Windows Server  In DOS prompt, run “Net helpmsg” on the %d value, and proceed
Failover Clustering (WSFC) accordingly.
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
41066 16 a 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
GROUP or DROP AVAILABILITY
41069 16 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
AVAILABILITY GROUP or DROP
41070 16 AVAILABILI
Cannot read the persisted
configuration of AlwaysOn
availability group with
corresponding Windows Server
Failover Clustering (WSFC)
resource ID '%.*ls'. The persisted
41071 16 configuration is written by a
higher-version SQL Server that
hosts the primary 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 resolve
41072 16 this error, try to r
The database '%.*ls' cannot be
removed from availability group
'%.*ls'. This database does not
41073 16 belong to the availability group.
AlwaysOn: The local replica of  This is an informational message only. No user action is required
preparing to transition to the
primary role in response to a
request from the Windows
cluster. This is an informational
41074 10 required
preparing to transition to the
resolving role in response to a
request from the Windows Server
Failover Clustering (WSFC) cluster.
41075 10 only. No user action is requir
AlwaysOn: Availability group
'%.*ls' is going offline because it is
being removed. This is an
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 been
41080 16 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
41081 16 details about this SQL Server error
AlwaysOn Availability Groups
startup has been cancelled,
because SQL Server is shutting
down. This is an informational
41089 10 required.
availability group '%.*ls' is going
offline because either the lease
expired or lease renewal failed.
AlwaysOn: The availability replica
manager is going offline because
%ls. This is an informational
41092 10 required.
offline because the corresponding
resource in the Windows Server
Failover Clustering (WSFC) cluster
is no longer online. This is an
restarting because the existing
primary replica restarted or the
availability group failed over to a
new primary replica. This is an
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
41095 10 group state in the instance of SQL
availability group '%.*ls' is being
removed. The instance of SQL
Server failed to validate the
41096 10 integrity of the availability group
configuration in the Windows
store. This is expected if th
offline. This replica failed to read
the persisted configuration
because of a version mismatch.
restarting, because it failed to
read the persisted configuration.
offline. This replica failed to read
the persisted configuration, and it
has exhausted the maximum for
restart attempts. This is an
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 the
availability group, then retry the
41100 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
41101 16 availability replica has joined the
Failed to persist configuration
data of availability group '%.*ls' in
the Windows Server Failover
Clustering (WSFC) cluster. The
local availability replica either is
not the primary replica or is
41102 10 shutting down.
Startup of the AlwaysOn
Availability Replica Manager has
been terminated, because the
'FixQuorum' property of Windows
is not present. The prerequisite
QFE hotfix, KB 2494036, might not
yet be installed on your Windows
41103 10 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
41106 16 is correct and unique, the
Availability group '%.*ls' failed to
create necessary events for the
WSFC Lease mechanism.
Windows returned error code
(%d) when obtaining handles for
Lease events. Resolve the
windows error and retry the
41107 16 availability group operation.
An error occurred while 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
41108 16 Windows Server Failover Clust
Could not enqueue a task (SQL OS
error: 0x%x) for process actions
for the availability group '%.*ls'.
Most likely, the instance of SQL
Server is low on resources. Check
the SQL Server error log to
determine the cause of the
41109 17 failure. Retry the operation l
manager is starting. This is an
manager is waiting for the
instance of SQL Server to allow
client connections. This is an
A Windows Server Failover
Clustering (WSFC) API required by
availability groups has not been
loaded. AlwaysOn Availability
Groups replica manager is not
enabled on the local instance SQL
Server. If the server instance is
41112 16 running an edition of SQL Server t
Cannot failover availability group
'%.*ls' to this instance of SQL
Server because a failover
command is already pending on
the local replica of this availability
group. Wait for the pending
failover command to complete
before issuing another command
41113 16 on t
group named '%.*ls' because it
41114 16 already exists in a system table.
Cannot create the availability
group named '%.*ls' because its
availability group ID (ID: '%.*ls')
41115 16 already exists in a system table.
group named '%.*ls' with replica
ID '%.*ls' because this ID already
41116 16 exists in a system table.
Cannot map local database ID %d
to the availability database ID
'%.*ls' within availability group
'%.*ls'. This database is already
41117 16 mapped to an availability group.
Cannot map database ID %d to
the availability database ID '%.*ls'
within availability group '%.*ls'.
Another local database, (ID %d). is
already mapped to this availability
41118 16 database.
Could not find the availability
41119 16 group ID %d in the system table.
The local availability replica of
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
41121 10 joined). The availabil
Server. The local availability
replica is already the primary
replica of the availability group.
To failover this availability group
to another instance of SQL Server,
41122 16 run the failover c
Operation on the local availability
replica of availability group '%.*ls'
failed. The local copy of the
does not exist or has not been
initialized. Verify that the
availability group exists and that
41126 16 the local copy of the
Attempt to set database mapping
state where the local database id
%d is not mapped to any
41127 16 availability group.
Failed to perform database
operation '%s' on database '%.*ls'
(ID %d) in availability group
'%.*ls'. The database might be in
an incorrect state for the
operation. If the problem
persists, you may need to restart
41128 16 the SQL Server instance.
Failed to schedule or execute
database operation '%s' on
database '%.*ls' (Database ID: %d)
in availability group '%.*ls' (SQL
OS error: %d). The instance of
SQL Server may have insufficient
resources to carry out the
database operation. If the
41129 16 problem p
Operation '%s' on a database
'%.*ls' (Database ID: %d) in
availability group '%.*ls' failed
with SQL Server error %d (Error
41130 16 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
Clustering (WSFC) node is online.
Then verify that the availability
group resource exists in the WSFC
41131 10 cluster. If the problem persis
Cannot join database '%.*ls' to
specified database does not
belong to the availability group.
Verify the names of the database
and the availability group, and
retry the command specifying the
41132 16 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
41133 10 retry the command.
Cannot bring the availability
group '%.*ls' online. The local
instance was not the previous
primary replica when the
availability group went offline, not
41134 16 all databases are synchronized,
and no force failover command
was issued on the local availability
r
Startup of AlwaysOn Availability
Groups replica manager failed due
to SQL Server error %d. To
determine the cause of this error,
check the SQL Server error log for
41135 10 the preceding error.
Failed to join the availability
replica to availability group '%.*ls'
because the group is not online.
Either bring the availability group
online, or drop and recreate it.
41136 16 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).
41137 10 This is an informational mes
Cannot accept AlwaysOn
Availability Groups operation
operation on database '%.*ls' of
database is currently processing
another operation that might
change the database state. Retry
the operation later. If the
41138 17 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 informational
41139 10 required.
Availability group '%.*ls' 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 of this
41140 16 availability group, an
Failed to set availability group
database information for
availability group %.*ls. The local
availability replica is not the
primary, or is shutting down. This
is an informational message only.
 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).
The availability replica for o When a cluster is started in forced_quorum mode (net.exe start
availability group '%.*ls' on this clussvc /forcequorum, OR Failover Cluster Manager>left
instance of SQL Server cannot pane>right-click Windows cluster>choose Force Cluster
become the primary replica. One Start>Confirm by clicking Yes.) on primary replica, the
or more databases are not availability group is required to be started by issuing command
synchronized or have not joined ALTER AVAILABILITY GROUP <AGNAME>
the availability group, or the FORCE_FAILOVER_ALLOW_DATA_LOSS;. Because this is the
WSFC cluster was started in Force original primary, despite issuing force allow data loss, NO data
41142 16 Quorum loss occurs
o When a cluster is started in forced_quorum mode on secondary
replica, first check
sys.dm_hadr_database_replica_cluster_states.is_failover_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 it’s
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_hardened_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.
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
41143 16 failure, either restart
availability group '%.*ls' 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
41144 16 Windows Server Failov
database has already joined the
41145 10 availability group. This is an
informational message. No user
action is required.
Failed to bring Availability Group

'%.*ls' online. The Windows
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
41146 16 retry the operation.
AlwaysOn Availability Groups was
not started because %ls. This is
an informational message. No
Cannot add or join database
'%.*ls' to availability group '%.*ls'.
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
41148 16 operation, specifying the correc
Operation on the availability
group '%.*ls' has been cancelled
or terminated, either because of a
connection timeout or
cancellation by user. This is an
informational message. No user
41149 16 action is required.
Failed to take availability group
'%.*ls' offline. The Windows
41150 16 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
41151 16 retry the operation.
Failed to create availability group  Check this document for error number mentioned in %d.
'%.*ls'. The operation
and has 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
41152 16 command
Failed to create availability group
encountered SQL 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
41153 16 to clean up any
'%.*ls' to this SQL Server instance.
The availability group is still being
created. Verify that the specified
41154 16 availability group name is correct.
Wait for CREATE AVAILABILITY
GROUP command to finish, then
retry the op
Server. The availability group is
being dropped. Verify that the
is correct. The availability group
may need to be recreated if the
41155 16 drop operation was
Cannot drop availability group
'%.*ls' from this instance of SQL
Server. The availability group is
either being dropped, or the local
availability replica is being
removed from the availability
group. Verify that the specified
41156 16 availability group name is
Cannot remove the local
availability replica from
availability group '%.*ls' from this
instance of SQL Server. The
availability group is either being
dropped, or the local availability
replica is being disjoined. Verify
41157 16 that the specified availability g
Failed to join local availability  Check for SQL/Windows messages around same time.
replica to availability group
and has been rolled back. Check
the SQL Server error log for more
41158 16 details. When the cause of the
error has been resolved, retry the
A
Failed to join local availability

replica to availability group
An attempt to rollback the
operation failed. Check SQL
Run DROP AVAILABILITY GROUP
41159 16 command to cl
Failed to designate the local
availability replica of availability
group '%.*ls' as the primary
replica. The operation
and has been terminated. Check
the preceding error and the SQL
Server error log for more details
41160 16 about
Failed to validate the Cyclic
Redundancy Check (CRC) of the
configuration of availability group
encountered SQL Server error %d,
and the availability group has
been taken offline to protect its
configuration and the consistency
41161 16 of
Failed to validate sequence
number of the configuration of
availability group '%.*ls'. The in-
41162 16 memory sequence number does
not match the persisted sequence
number. The availability group
and/or the local availability
replica will be restarted
automatical
An error occurred while waiting
for the local availability replica of
availability group '%.*ls' to
transition to the primary role.
OS error %d and has been
terminated. Verify that the
41163 16 Clustering (WS
for the local availability replica of
transition to the resolving role.
OS error %d and has been
41164 16 Clustering (
A timeout error occurred while
waiting to access the local
availability replica of availability
group '%.*ls'. The availability
replica is currently being accessed
by another operation. Wait for
the in-progress operation to
41165 16 complete, and then retry the
An error occurred while waiting to
access the local availability replica
41166 16 of availability group '%.*ls'. The
operation encountered SQL OS
error %d, and has been
terminated. Verify that the local
availability replica is in the correct
state, and then retr
An error occurred while
attempting to access availability
replica '%.*ls' in availability group
'%.*ls'. The availability replica is
not found in the availability group
configuration. Verify that the
availability group and availability
41167 16 replica names are
attempting to access availability
replica with ID '%.*ls' in
availability replica is not found in
the availability group
configuration. Verify that the
availability group name and
41168 16 availability repl
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 that
the availability group name and
41169 16 avail
Post-online processing for
availability group '%.*ls' has been
41170 10 terminated. 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 infor
'%.*ls', because a Windows Server
Failover Cluster (WSFC) group
with the specified name already
exists. The operation has been
rolled back successfully. To retry
creating an availability group,
41171 16 either remove or rename
An error occurred while dropping  In DOS prompt, run “Net helpmsg” on the %d value, and proceed
availability group '%.*ls' from accordingly.
Clustering (WSFC) cluster and
from the local metadata. The
41172 16 specified availability gr
An error occurred while removing
the local availability replica from
is correct, and then retry the
41173 16 command
Failed to acquire exclusive access
to local availability group
41176 10 configuration data (SQL OS error:
%d). If the problem persists, you
might need to restart the instance
of SQL Server.
The availability replica of the
specified availability group '%.*ls'
is being dropped. Wait for the
completion of the drop command
41177 16 and retry the operation later.
Cannot drop availability group
'%.*ls' from this SQL Server
instance. The availability group is
currently being created. Verify
that the specified availability
group name is correct. Wait for
the current operation to
complete, then retry the
41178 16 command if
Cannot remove the local
availability replica from
availability group '%.*ls' from this
instance of SQL Server. The
availability group is currently
being created. Verify that the
is correct. Wait for the current
41179 16 operati
Attempt to access non-existent 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
41180 16 user action is requir
availability group '%.*ls' did not
become primary. A concurrent
operation may have changed the
state of the availability group in
Windows Server Failover Cluster.
Verify that the availability group
41181 16 state in Windows Serv
Failed to set the local availability
replica of availability group '%.*ls'
as joined in Windows Server
database. Either the local
availability replica is no longer the
primary, or the WSFC service is
41182 16 not accessible. Verify tha
Failed to modify availability
replica options for availability
group '%.*ls'. Before the
could be updated, the operation
The operation has been rolled
back. Refer to the SQL Server
41183 16 error
Failed to modify availability
replica options for availability
group '%.*ls'. The availability
group configuration has been
updated. However, the operation
while applying the new
configuration to the local
41184 16 availability re
Replica option specified in ALTER
AVAILABILITY GROUP '%.*ls'
MODIFY DDL is same is cached
41185 10 availability group configuration.
process an ALTER AVAILABILITY
GROUP command at this time.
The availability group is still being
created. Verify that the specified
availability group name is correct.
Wait for CREATE AVAILABILITY
41186 16 GROUP command to finis
process an ALTER AVAILABILITY
GROUP command at this time.
The availability group is being
dropped. Verify that the specified
availability group name is correct.
The availability group may need
41187 16 to be recreated if it was
process %s-%s command. The
operation encountered SQL
Server error %d before the
could be updated, and has been
rolled back. Refer to the SQL
Server error log for details. Verify
41188 16 that
process the %s-%s command. The
has been updated. However, the
41189 16 operation encountered SQL
Server error %d while applying
the new configuration to the local
availability replica, and has
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
41190 16 the primary replica, the
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
41191 16 Server to the same
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
41192 17 count on
database is in the process of being
removed from the availability
group. When the remove-
41193 10 database operation completes,
the database will no longer be
joined to the availability group.
Then
for the local availability replica for
complet post-online work. The
error %d and has been
41194 16 Clustering (WSFC) c
process the WSFC lease-renewal
command. The local availability
replica lease is no longer valid to
process the lease renewal
command. Availability replica
lease expired. This is an
41195 16 user a
'%.*ls', because a Windows Server
Failover Cluster (WSFC) group
with the specified name already
exists. An attempt to rollback the
operation failed. Check the SQL
41196 16 To manually clean
The specified command is invalid
because the AlwaysOn Availability
Groups feature is not supported
by this edition of SQL Server. For
41199 16 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
41402 16 loss of quorum in the cluster.
41403 16 Availability group is offline.
The availability group is offline,
and is unavailable. This issue can
be caused by a failure in the
server instance that hosts the
primary replica or by the WSFC
availability group resource going
41404 16 offline.
Availability group is not ready for
41405 16 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
41406 16 secondary replica is unavail
In this availability group, at least
one secondary replica has a NOT
SYNCHRONIZING synchronization
state and is not receiving data
41408 16 from the primary replica.
one synchronous replica is not
currently synchronized. The
replica synchronization state
could be either SYNCHONIZING or
41410 16 NOT SYNCHRONIZING.
one availability replica does not
currently have the primary or
41412 16 secondary role.
one secondary replica is not
connected to the primary replica.
The connected state is
41414 16 DISCONNECTED.
This secondary database is not
The configuration of this
secondary database is
incomplete. For information
about how to join a secondary
database to an availability group,
41424 16 see SQL Server Books Online.
This secondary replica is not
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
41428 16 ho
SQL Server AlwaysOn (SQL Server Configuration Manager)
 You may receive this error if you don't have the

An error occurred while loading the AlwaysOn High appropriate permission. Try right click ‘SQL Server
Availability properties [return code: 0x80070005]. Configuration Manager’ and select ‘Run as
Administrator’.
The AlwaysOn Availability Groups feature requires the  Verify OS is Windows 2008 or later version.
x86(non-WOW) or x64 Enterprise Edition of SQL  If OS is Windows 2008 or Windows 2008 R2, install
Server 2012 (or later version) running on Windows Windows hotfix KB 2494036, if not already
Server 2008 (or later version) with WSFC hotfix KB installed.
2494036 installed. This SQL Server edition and/or
Windows Server System does not meet one or more
of the requirements
SQL Server AlwaysOn (New Availability Group wizard errors)
 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.
The current WSFC cluster quorum o While setting up the availability group in the wizard, you
vote configuration is not configured a replica to asynchronous availability mode. This
recommended for this availability warning is only reported in SQL 2012 RTM, not in SP1 of SQL
group. 2012 RTM.
For more information, see the o While setting up the availability group in the wizard, you
following topic in SQL Server Books configured a replica for manual failover mode. This warning is
Online: only reported in SQL 2012 RTM, not in SP1 of SQL 2012 RTM.
http://go.microsoft.com/fwlink/?Li  Check the link. Redirects to http://msdn.microsoft.com/en-
nkId=224159. us/library/hh270280.aspx
Checking for the database files on  Check if database-file paths are identical on source and on destination
the secondary replica resulted in servers. If different, manual (rather than using AG wizard) restore may
an error. be required with WITH MOVE syntax.
(Microsoft.SqlServer.Management.
HadrTasks)
------------------------------
Program Location:
at
Microsoft.SqlServer.Management.
Hadr.TestDatabaseFileExisting.Do
Work()
at
TaskForms.SimpleWorkItem.Run()
============================
=======
The following database files
already exist on the server instance
that hosts secondary replica HA-
VM3\TEST1:
\\path\file.mdf
\\path\file_log.ldf
(Microsoft.SqlServer.Management.
HadrTasks)
------------------------------
Program Location:
at
Hadr.TestDatabaseFileExisting.Do
Work()
SQL Server AlwaysOn (performance issues)

Unable to access database '%.*ls' because its replica  Check SQL ERRORLOGs, event logs, etc. for
role is RESOLVING which does not allow connections. network, storage related messages etc.
983 14 Try the operation again later.
 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
The database '%ls' is marked %ls and is in a state that "_old" suffix and changed them back to the original name.
3402 10 does not allow recovery to be run. 8) Had the customer start the SQL Server Service.
 If KB2723814 not applied, then try the KB
Slow synchronization. Waittime for workaround of suspend secondary replica and then
HADR_SYNC_COMMIT grows anywhere from 500ms resume, so that AlwaysOn knows that availability
to 900ms (compared to less than 15-20 ms). mode has changed back to synchronous commit.
SQL Server AlwaysOn errors (other)

The WSFC cluster could not bring the Network Name  Check for associated errors like error 19476.
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
19471 16 running or may be inaccessible. Use a different
The attempt to create the network name and IP  Check for associated errors like error 41009.
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
19476 16 IP address with the network administrator.
 Net helpmsg on the %d value, and proceed
accordingly.
 May also be accompanied by Microsoft-Windows-
FailoverClustering messages in event log.
 Check cluster log.
 If there error is in cluster in Windows Azure, then it
may be because Windows Azure currently does not
support more than one IP address per VM, which is
required by the availability group listener to resolve
The Windows Server Failover Clustering (WSFC) to the availability group owner node. This is
resource control API returned error code %d. The documented in http://msdn.microsoft.com/en-
WSFC service may not be running or may not be us/library/jj870962.aspx (High Availability and
accessible in its current state, or the specified Disaster Recovery for SQL Server in Windows Azure
arguments are invalid. For information about this Virtual Machines).
41009 16 error code,
Failed to obtain the Windows Server Failover  Check if Windows cluster service is running.
Clustering (WSFC) node handle (Error code %d). The  Net helpmsg on the %d value, and proceed
WSFC service may not be running or may not be accordingly.
accessible in its current state, or the specified cluster
41015 16 node name is invalid. For information about this erro
SQL Server AlwaysOn errors (network)
 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
TCP Provider, error: 0 - An operation on a socket could  Add registry setting for TCPTIMEWAITDELAY.
not be performed because the system lacked  App/IIS restart, machine reboot are additional
sufficient buffer space or because a queue was full. options.
SQL Server AlwaysOn errors (Windows)
 Checked if IP is already in use

 Check permission for cluster network object CNO.
5057 The cluster IP address is already in use.
 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
The resource failed to come online due to the failure it does not come online, then this requires
5942 of one or more provider resources. investigation by Windows team.
Application errors
SQL Server AlwaysOn errors (cluster log)
 Status 5 is Access Denied

 In Windows AD, check for CNO (cluster network
object) permissions.
 For example, below to grant the "create 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 -
[RES] Network Name <SPEPD_Tier2>: Unable to Properties.
update password for computer account DCR-SPEPD --> Computers Properties screen appears.
on DC \\ DC-04.xxxx.org, status 5. 7) Security tab-click the Advanced button.
[RHS] Online for resource SPEPD_Tier2 failed. --> 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  net helpmsg 8557 says "Your computer could not
object aglisten11 on DC: \\DC.contoso.com, result: be joined to the domain. You have exceeded the
8557 maximum number of computer accounts you are
ERR [RES] Network Name: [NNLIB] Failed to create allowed to create in this domain. Contact your
Computer Object aglisten11 in the Active Directory, system administrator to have this limit reset or
error 8557 increased."
SQL Server AlwaysOn (patching/updates in SQL 2012)
AG on Standalone Instance
Patching steps:
1. Patch the secondary replica (B)

2. Bring the secondary replica online (will be new version)
3. 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
4. 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
5. Patch the original primary replica (A)
6. Bring the original primary replica (A) online (will be new version )
7. Wait for A to become “Synchronized”
8. Failover the AG back to A
9. Change each replica’s 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 hasn’t 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 Node3 to Node4
3. Patch Node3
5. Patch Node2
7. Patch Node1
Optimized downtime, more steps

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

1. Patch 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
11. Manually failover AG from FCI2 back to FCI1
12. Change each replica’s 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 Alwayson v1 2

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Troubleshooting Alwayson v1 2

Încărcat de

Drepturi de autor:

Formate disponibile

41046 16

AlwaysOn Availability Groups:

The ID of availability group '%.*ls'

Failed to bring Availability Group

Failed to join local availability

 You may receive this error if you don't have the

 When validating WSFC quorum vote configuration, the AlwaysOn

SQL Server AlwaysOn (performance issues)

SQL Server AlwaysOn errors (other)

 NetStat output may show hundreds of entries in

SQL Server AlwaysOn errors (Windows)

 Checked if IP is already in use

 Status 5 is Access Denied

Instructions [to be tested]

SQL Server AlwaysOn (patching/updates in SQL 2012)

1. Patch the secondary replica (B)

AG on FCIs (Failover Cluster Instances)

FCI on AG deployment Example

Choose between one of the following two options:

Patching steps (basic):

Optimized downtime, more steps

Patching steps (optimized):

S-ar putea să vă placă și