Event Id 1146 Microsoft Windows Failover Clustering Tools
Event ID 1541 — Backup and Restore Functionality in a Cluster. ID: 1541: Source: Microsoft-Windows. Tools, and then click Failover Cluster.
| Event Id | 1135 |
| Source | Microsoft-Windows-FailoverClustering |
| Description | Cluster node '%1' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges. |
| Event Information | According to Microsoft : Cause : This event is logged when Cluster node was removed from the active failover cluster membership. Resolution : Check network hardware and configuration If you do not currently have Event Viewer open, see 'Opening Event Viewer and viewing events related to failover clustering.' After reviewing event messages, choose actions that apply to your situation:
Using the Validate a Configuration Wizard to review the network configuration To use the Validate a Configuration Wizard to review the network configuration:
To open Event Viewer and view events related to failover clustering:
Confirm that the nodes are running and that the backup or restore process succeeded. To perform this procedure, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority. Viewing the status of the nodes in a failover cluster To view the status of the nodes in a failover cluster:
Using a command to view the status of the nodes in a failover cluster To use a command to view the status of the nodes in a failover cluster:
|
| Reference Links | Event ID 1135 from Microsoft-Windows-FailoverClustering |
Roughly a year ago, i had this problem with an 2008R2 cluster. I asked about it here, but i didn't grab enough logs in the process. And now i have the same problem on my 2012 failover cluster. So i'm making a separate question on the 'new' problem.
I have a hard time thinking that its just a coincident that both cluster has the same problem. But i can't find an solution, plus it's alot of planning to take down time to test solutions. But i'm throwing it out here and see if someone has any ideas.
The cluster is two physical node Windows Server 2012 R2 Standard with SQLServer 2012 SP2. Aplikasi sistem informasi desa. The SQLServer contains 101 DBs with sizes spanning from 2 mb to 150 gb. Most DBs are around 200-300 mb, are in simple mode and have a low use. (The 2008 cluster is very similar to this, but with 150ish DBs)
When i install SP3 on the passive node, it works fine, no errors. But when i failover, it takes online the storage, servername, File server and DTC resources, SQL Server is online pending, SQL Server Agent is down. After 10 minutes it changes SQL Server resource to Failed and does a fail back to the other node
And this:
I have added all the SPNs its complaining on with:
setspn -S cifs/CLUSTER_NAME.domain.se CLUSTER_NAME Checking domain DC=domain,DC=se Registering ServicePrincipalNames for CN=CLUSTER_NAME,OU=Clustername,OU=Servers, DC=domain,DC=se cifs/CLUSTER_NAME.domain.se Updated object
Other entrys in the errorlog:
Regarding this one, i tried to up the maximum failure value for the resource without luck:
And then a bunch of errors on opening a logfile. I tried to add rights to that folder for the AD-account that the SQLServer resource runs under, no luck, still getting these:
These also show up, but they are showing up regardless of the Servicepack installation License status 11.1 6011.
I have also been looking thru the Windows cluster log (get-clusterlog), and can't find anything that stands out.
Having this problem on 2 servers with 100+ DBs, can it be something with the upgrade taking to long, and the windows cluster getting impatient and think it failed?
I looked into this artice: [https://blogs.msdn.microsoft.com/clustering/2013/01/24/understanding-how-failover-clustering-recovers-from-unresponsive-resources/] and tried to double the Deadlocktimeout value without luck.
Anyone with any idea? I'm treading water here.
1 Answer
Microsoft Windows Failover Clustering Error
I found the issue after a long time. It was due to 1 million+ files in the MSSQLlog folder.
After setting up a job that cleared that folder. The failover after SP install worked fine.
The solution was confirmed on both this 2012 cluster, and the 2008R2 cluster we had the same problem on
Feb 17, 2018 - Sep 12, 2005 Environments for All Local Action Sand Dunes Hedging Toolcare The Urban Handbook Dry Stone Walling Footpaths. Dec 23, 2017 - Many popular paths, especially in the uplands, have become eroded through over-use. The traditional skills of stone pitching and drainage.