无法访问srv解析_SQL Server始终打开：在具有各种错误的辅助服务器上失败，但为什么主要无法访问？...

Hello Experts,

I ran into  issue on SQL 2012 SP4 Environment where secondary server went down and when i checked the logs found exact somany different errors which was listed below.

Primary server was always up and running but not sure what caused users to to stop the access on Primary database.

Also SQL account on Primary which was used for connection tuned into orphaned user when i checked so had to remap on Primary.

Though everything went   back to normal when secondary server came up but why users were not able to access primary server though it was up and running.

Any idea what could have happened to Primary even though it was all time up and running?

Did It tried to fail over on Secondary some reason?

*******************************************************************

Error Log as below:

Failed to update Replica status within the local Windows Server Failover Clustering (WSFC) due to exception 41034.

Failed to update Replica status within the local Windows Server Failover Clustering (WSFC) due to exception 41005.

Error: 41144, Severity: 16, State: 8.

The local availability replica of availability group ' ' is in a failed state.  The replica failed to read or update the persisted configuration data (SQL Server error: 41034).  To recover from this failure, either restart the local Windows Server

Failover Clustering (WSFC) service or restart the local instance of SQL Server.

Remote harden of transaction 'user_transaction' (ID 0x000000005c947182 0000:28d9d77f) started at Feb  6 2018  5:10PM in database ' ' at LSN (15129:292464:157) failed.

Error: 41143, Severity: 16, State: 2.

Cannot process the operation.  The local replica of availability Group ' ' 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 failure, either

restart the local Windows Server Failover Clustering (WSFC) service or restart the local instance of SQL Server.

Failed to obtain the Windows Server Failover Clustering (WSFC) resource handle for cluster resource with name or ID '567e9cfe-6a0a-4661-b270-b3c717ca0862' (Error code 1722).  The WSFC service may not be running or may not be accessible in its current state,

or the specified cluster resource name or ID is invalid.  For information about this error code, see "System Error Codes" in the Windows Development documentation.

The state of the local availability replica in availability group ' ' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'.  The state changed because the local instance of SQL Server is shutting down.  For more information, see the SQL Server

error log, Windows Server Failover Clustering (WSFC) management console, or WSFC log.

The Cyclic Redundancy Check (CRC) value generated for the retrieved availability group configuration data does not match that stored with the data for the availability group with ID '%.*ls'. If this is a WSFC availability group, the availability group data

in the WSFC store may have been modified outside SQL Server, or the data is corrupt. If the error persists, you may need to drop and recreate the availability group.

Failed to validate the Cyclic Redundancy Check (CRC) of the configuration of availability group '%.*ls'. The operation encountered SQL Server error %d, and the availability group has been taken offline to protect its configuration and the consistency of its

joined databases. Check the SQL Server error log for more details. If configuration data corruption occurred, the availability group might need to be dropped and recreated.

AlwaysOn: The local replica of availability group is preparing to transition to the resolving role in response to a request from the Windows Server Failover Clustering (WSFC) cluster.

A connection timeout has occurred on a previously established connection to availability replica

Thank you.

Thank you very much for your time and effort to answer this post. Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach Best -Ankit

解决方案Hi -kit,

Have you tried restarting the WSFC service and SQL Server?

Best regards,

Dedmon Dai