Wondering how to resolve EC2 error sql server instance failed over from a primary replica to a secondary? We can help you.
Here at Bobcares, we handle requests from our customers to fix similar issues as a part of our Server Management Services.
Today let’s see how our Support Engineers fix this for our customers.
How to troubleshoot EC2 error sql server instance failed over from a primary replica to a secondary?
To determine if the issue is at the cluster level, view the System Logs in the Event Viewer using the following steps:
- Firstly, open the Run application, and then enter eventvwr and select OK.
- Select Windows Logs, System.
If you see events 1069, 1146, 1230, or 1135 in the logs, then begin investigating at the cluster level by generating cluster logs.
Today, let us see the steps followed by our Support Techs to troubleshoot the issue.
Follow below command according to your Windows operation system to validate that cluster service is continuously running and available.
For Windows Server 2008 R2 cluster
From an elevated cmd prompt, run the below command:
cluster.exe node /stat
For Windows Server 2012 and Windows Server 2012 R2 cluster
Run the following PS command:
Follow below steps to generate and retrieve cluster logs:
- Generate the latest set of cluster logs by running the get-clusterlogs command in Windows PowerShell.
- Retrieve the cluster logs from the default location at C:\windows\cluster\reports.
If the cluster logs show that the cluster failed over due to SQL resources, review the Event Viewer application logs for SQL errors.
[Need assistance with EC2 error? We can help you]
In short, today we saw how our Support Techs troubleshoot the EC2 error.