Availability group failover
- Last UpdatedApr 24, 2025
- 1 minute read
If you have configured an availability group on the system, temporary disconnection of product applications to Microsoft SQL Server will occur if the applications attempt to access historical data during an availability group failover. The recovery rate of individual applications after the new primary node is achieved is variable, but the applications will re-establish connections and continue processing data.
Examples—error messages in log files
Unable to Connect to 'ls1pdcAG,20010' -- Unable to access availability database 'ARCHIVE' because the database replica is not in the PRIMARY or SECONDARY role. Connections to an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later.
RDBMSInfrastructure.MonitorExecute failed to establish connection to SQL Server. Error: Unable to build the 'Databases' collection because execution of the SQL query failed
(HistoricalFailure) SQL error: ConnectionTemporarilyLost
In addition, within the Databases node of the Historical service in the Network Management Console (NMC), the Health State of the databases may temporarily show as failed.