Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
error severitydescription
Database '%.*ls' is enabled for database
mirroring or has joined an availability group.
957 17 The name of the database cannot be changed.
If
dm_hadr_availability_replica_states.role_desc=3(INVALID),
The target database, '%.*ls', is participating in then check service broker. Because Availability group is
an availability group and is currently not using Service Broker to communicate between SQL Server
accessible for queries. Either data movement is then need to check Service Broker first. Open
suspended or the availability replica is not SSMS>“Server Objects” > “Endpoints”, there are two
enabled for read access. To allow read-only “Service Broker” folder>Expand both, and if the state is
976 14 access to this and other Stopped or Disabled, then can change the state to Started.
The target database ('%.*ls') is in an availability
group and is currently accessible for
connections when the application intent is set
to read only. For more information about
application intent, see SQL Server Books
978 14 Online.
The target database ('%.*ls') is in an availability
group and currently does not allow read only
connections. For more information about
application intent, see SQL Server Books
979 14 Online.
Unable to access the '%.*ls' database because
no online secondary replicas are enabled for
read-only access. Check the availability group
configuration to verify that at least one
secondary replica is configured for read-only
982 14 access. Wait for an enabled r
The remote copy of database "%.*ls" is not
recovered far enough to enable database
mirroring or to join it to the availability group.
You need to apply missing log records to the
remote database by restoring the current log
1408 16 backups from the principal/prim
Database "%.*ls" requires database logs to be
restored either on the future mirror database
before you can enable database mirroring or
on a secondary availability database before
you can join it to the availability group. Restore
1409 16 current log backups from
Database "%.*ls" database is not in full
recovery mode on each of the server instances.
The full recovery model is required for a
database to participate in database mirroring
1465 16 or in an availability group.
Database "%.*ls" is read-only on one of the
server instances which is incompatible with
participating in database mirroring or in an
availability group. Set the database to read-
1466 16 write mode, and retry the operation.
Database "%.*ls" database is in emergency or
suspect mode on one of the partners which is
incompatible with participating in database
1467 16 mirroring or in an availability group.
The operation cannot be performed on
database "%.*ls" because it is involved in a
database mirroring session or an availability
group. Some operations are not allowed on a
database that is participating in a database
1468 16 mirroring session or in an availabilit
Database "%.*ls" is an auto-close database on
1469 16 one of the partnerswhich is incompatible with
participating in database mirroring or in an
availability group.
The %S_MSG database "%.*ls" is changing
roles from "%ls" to "%ls" because the mirroring
session or availability group failed over due to
%S_MSG. This is an informational message
1480 10 only. No user action is required.
Database "%.*ls" database is in single user
mode which is incompatible with participating
in database mirroring or in an availability
group. Set database to multi-user mode, and
1488 16 retry the operation.
File '%ls' cannot be reused until after the next
BACKUP LOG operation. If the database is
participating in an availability group, a dropped
file can be reused only after the truncation LSN
of the primary availability replica has passed
1833 16 the drop LSN of the
RESTORE cannot operate on database '%ls'
because it is configured for database mirroring
or has joined an availability group. If you
intend to restore the database, use ALTER
DATABASE to remove mirroring or to remove
3104 16 the database from its availability gro
Before you can drop the database, you need to remove it
from the availability group. If AG exists, try ALTER
AVAILABILITY GROUP [AGname] REMOVE DATABASE
[DbName]. If AG does not exist, try removing with ALTER
DATABASE [DbName] SET HADR OFF.
If replica_id and group_database_id in sys.databases show
The database '%.*ls' is currently joined to an as null, then this may be due to earlier meta-data when
availability group. Before you can drop the database was part of an AG so stop SQL Server, rename
database, you need to remove it from the the database files and start SQL Server. Then you should
3752 16 availatility group. be able to remove the database.
Failed to remove a FILESTREAM file. The
database is a primary database in an
availability group. Wait for the FILESTREAM
data files to be hardened on every secondary
availability replica. Then retry the drop file
5529 16 operation.
The ALTER AVAILABILITY GROUP command
failed because it contained multiple MODIFY
REPLICA options: %ls. Enter a separate ALTER
AVAILABILITY GROUP ... MODIFY REPLICA
command for each replica option that you
10786 16 want to modify.
13251 10 availability group
The READ_ONLY_ROUTING_URL '%.*ls'
specified for availability replica '%.*ls' is not
valid. It does not follow the required format of
'TCP://system-address:port'. For information
about the correct routing URL format, see the
19401 16 CREATE AVAILABILITY GROUP docum
The availability replica '%.*ls' specified in the
READ_ONLY_ROUTING_LIST for availability
replica '%.*ls' does not exist. Only availability
replicas that belong to the specified availability
group '%.*ls' can be added to this list. To get
19403 16 the names of ava
Failed to create, join or add replica to
availability group '%.*ls', because node '%.*ls'
is a possible owner for both replica '%.*ls' and
'%.*ls'. If one replica is failover cluster
instance, remove the overlapped node from its
19405 16 possible owners and try ag
The state of the local availability replica in
availability group '%.*ls' has changed from '%ls'
19406 10 to '%ls'. The replica state changed because of
either a startup, a failover, a communication
issue, or a cluster error. For more information,
see the availabi
The lease between availability group '%.*ls'
and the Windows Server Failover Cluster has
expired. A connectivity issue occurred between
the instance of SQL Server and the Windows
Server Failover Cluster. To determine whether
19407 16 the availability group is fail
The availability group listener (network name)
with Windows Server Failover Clustering
resource ID '%s', DNS name '%s', port %hu
failed to start with a permanent error: %u.
Verify port numbers, DNS names and other
19452 16 related network configuration, then retry
The availability group listener (network name)
with Windows Server Failover Clustering
resource ID '%s', DNS name '%s', port %hu
failed to start with this error: %u. Verify
19453 16 network and cluster configuration and logs.
The availability group listener (network name)
with Windows Server Failover Clustering
resource ID '%s', DNS name '%s', port %hu
failed to stop with this error: %u. Verify
19454 16 network and cluster configuration and logs.
The WSFC cluster does not have a public
cluster network with an IPv4 subnet. This is a
requirement to create an availability group
DHCP listener. Configure a public network for
the cluster with an IPv4 subnet, and try to
19455 16 create the listener.
None of the IP addresses configured for the Added a new IP address (with different subnet) manually
availability group listener can be hosted by the to the existing Listener [to be tested].
server '%.*ls'. Either configure a public cluster
network on which one of the specified IP
addresses can be hosted, or add another
19456 16 listener IP address which can b
The WSFC nodes that host the primary and
secondary replicas belong to different subnets.
DHCP across multiple subnets is not supported
for availability replicas. Use the static IP option
19458 16 to configure the availability group listener.
The availability group listener with DNS name
'%.*ls' is configured to use DHCP. For listeners
with this configuration, IP addresses cannot be
added through SQL Server. To add IP addresses
to the listener, drop the DHCP listener and
19460 16 create it again config
The listener with DNS name '%.*ls' for the
availability group '%.*ls' is already listening on
the TCP port %u. Please choose a different TCP
port for the listener. If there is a problem with
the listener, try restarting the listener to
19468 16 correct the problem
The specified listener with DNS name, '%.*ls',
does not exist for the Availability Group '%.*ls'.
Use an existing listener, or create a new
19469 16 listener.
The availability group '%.*ls' already has a
listener with DNS name '%.*ls'. Availability
groups can have only one listener. Use the
existing listener, or drop the existing listener
19477 16 and create a new one.
The configuration changes to the availability
group listener were completed, but the TCP
provider of the instance of SQL Server failed to
listen on the specified port [%.*ls:%d]. This TCP
port is already in use. Reconfigure the
19486 16 availability group listener
The availability group associated with Virtual
21872 16 Network Name '%s' has no replicas.
The virtual network name '%s' has been used
to identify the redirected publisher for original
publisher '%s' and database '%s'. The
availability group associated with this virtual
network name, however, does not include the
21880 16 publisher database.
The database '%s' at the redirected publisher
'%s' for original publisher '%s' and database
'%s' belongs to a HADRon availability group
and must be redirected to its associated
21882 16 HADRon Virtual Network Name.
The query at the redirected publisher '%s' to
determine whether the publisher database
'%s' belonged to an availability group failed
21883 16 with error '%d', error message '%s'.
The query at the redirected publisher '%s' to
determine the health of the availability group
associated with publisher database '%s' failed
21884 16 with error '%d', error message '%s'.
The query at the redirected publisher '%s' to
determine whether the publisher database
'%s' belonged to an availability group failed
21887 16 with error '%d', error message '%s'.
Unable to query sys.availability_replicas at the
availability group primary associated with
21892 16 virtual network name '%s' for the server names
of the member replicas: error = %d, error
message = %s.',
The availability group '%.*ls' already exists. If AG still exists, DROP AVAILABILITY GROUP.
This error could be caused by a previous failed Open regedit, backup the entry from the old Availability
CREATE AVAILABILITY GROUP or DROP Group that starts with HADR_Ag_???? key, then delete this
AVAILABILITY GROUP operation. If the key [to be tested].
availability group name you specified is Try with new name for Availability Group.
41042 16 correct, try dropping the availability group a
For availability group '%.*ls', the value of the
name-to-ID map entry is invalid. The binary
value should contain a Windows Server
Failover Clustering (WSFC) resource ID, a WSFC
group ID, and their corresponding lengths in
41043 16 characters. The availability g
Availability group name to ID map entry for
availability group '%.*ls' cannot be found in the
Windows Server Failover Clustering (WSFC)
store. The availability group name may be
incorrect, or the availability group may not
41044 16 exist in this Windows Server Fa
Cannot add database '%.*ls' to the availability
group '%.*ls', because there is already a
database with the same name in the
availability group. Please verify that the
database and availability group names
41045 16 specified are correct.
Cannot add replica '%.*ls' to the availability
group '%.*ls', because there is already a replica
with the same name in the availability group.
Please verify the replica and availability group
41046 16 names specified are correct.
AlwaysOn Availability Groups: Local Windows
41048 10 Server Failover Clustering service has become
unavailable. This is an informational message
only. No user action is required.
AlwaysOn Availability Groups: Local Windows
Server Failover Clustering node is no longer
online. This is an informational message only.
41049 10 No user action is required.
AlwaysOn Availability Groups: Waiting for local
Windows Server Failover Clustering service to
start. This is an informational message only. No
41050 10 user action is required.
AlwaysOn Availability Groups: Local Windows
Server Failover Clustering service started. This
is an informational message only. No user
41051 10 action is required.
AlwaysOn Availability Groups: Waiting for local
Windows Server Failover Clustering node to
start. This is an informational message only. No
41052 10 user action is required.
AlwaysOn Availability Groups: Local Windows
Server Failover Clustering node started. This is
an informational message only. No user action
41053 10 is required.
AlwaysOn Availability Groups: Waiting for local
Windows Server Failover Clustering node to
come online. This is an informational message
41054 10 only. No user action is required.
AlwaysOn Availability Groups: Local Windows
Server Failover Clustering node is online. This
is an informational message only. No user
41055 10 action is required.
Availability replica '%.*ls' of availability group
'%.*ls' cannot be brought online on this SQL
Server instance. Another replica of the same
41056 16 availability group is already online on the local
Windows Server Failover Clustering (WSFC)
node. Each WSFC node
Cannot bring the Windows Server Failover In DOS prompt, run “Net helpmsg” on the %d value, and
Clustering (WSFC) resource (ID '%.*ls') online proceed accordingly.
(Error code %d). The WSFC service may not be
running or may not be accessible in its current
state, or the WSFC resource may not be in a
41066 16 state that could accept the r
The existence of availability group data for the
availability group '%.*ls' in the Windows Server
Failover Clustering (WSFC) store could not be
determined. The local WSFC node may be
down, or a previous CREATE AVAILABILITY
41069 16 GROUP or DROP AVAILABILITY GROU
Configuration data for the availability group
with Windows Server Failover Clustering
(WSFC) resource ID '%.*ls' is not found in the
WSFC data store. The availability group may
have been dropped, or a previous CREATE
41070 16 AVAILABILITY GROUP or DROP AVAILABILI
Cannot read the persisted configuration of
AlwaysOn availability group with
corresponding Windows Server Failover
Clustering (WSFC) resource ID '%.*ls'. The
persisted configuration is written by a higher-
version SQL Server that hosts the primary
41071 16 availabi
The ID of availability group '%.*ls' in local data
store does not exist in the Windows Server
Failover Clustering (WSFC) data store. The
availability group may have been dropped but
the current WSFC node was not notified. To
41072 16 resolve this error, try to r
The database '%.*ls' cannot be removed from
availability group '%.*ls'. This database does
41073 16 not belong to the availability group.
AlwaysOn: The local replica of availability This is an informational message only. No user action is
group '%.*ls' is preparing to transition to the required
primary role in response to a request from the
Windows Server Failover Clustering (WSFC)
cluster. This is an informational message only.
41074 10 No user action is required
AlwaysOn: The local replica of availability
group '%.*ls' is preparing to transition to the
resolving role in response to a request from
the Windows Server Failover Clustering (WSFC)
cluster. This is an informational message only.
41075 10 No user action is requir
AlwaysOn: Availability group '%.*ls' is going
offline because it is being removed. This is an
informational message only. No user action is
41076 10 required.
Failed to delete SQL Server instance name to
Windows Server Failover Clustering node name
map entry for the local availability replica of
availability group '%.*ls'. The operation
encountered SQL Server error %d and has
41080 16 been terminated. Refer to the SQL
Failed to destroy the Windows Server Failover
Clustering group corresponding to availability
group '%.*ls'. The operation encountered SQL
Server error %d and has been terminated.
Refer to the SQL Server error log for details
41081 16 about this SQL Server error
AlwaysOn Availability Groups startup has been
41089 10 cancelled, because SQL Server is shutting
down. This is an informational message only.
No user action is required.
AlwaysOn: The local replica of availability
group '%.*ls' is going offline because either the
lease expired or lease renewal failed. This is an
informational message only. No user action is
41091 10 required.
AlwaysOn: The availability replica manager is
going offline because %ls. This is an
informational message only. No user action is
41092 10 required.
AlwaysOn: The local replica of availability
group '%.*ls' is going offline because the
corresponding resource in the Windows Server
Failover Clustering (WSFC) cluster is no longer
online. This is an informational message only.
41093 10 No user action is required.
AlwaysOn: The local replica of availability
group '%.*ls' is restarting because the existing
primary replica restarted or the availability
group failed over to a new primary replica. This
is an informational message only. No user
41094 10 action is required.
AlwaysOn: Explicitly transitioning the state of
the Windows Server Failover Clustering (WSFC)
resource that corresponds to availability group
'%.*ls' to Failed. The resource state is not
consistent with the availability group state in
41095 10 the instance of SQL
AlwaysOn: The local replica of availability
group '%.*ls' is being removed. The instance of
SQL Server failed to validate the integrity of
41096 10 the availability group configuration in the
Windows Server Failover Clustering (WSFC)
store. This is expected if th