Event Id 1146 Microsoft Windows Failover Clustering Tools
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.
Contacts of the Sensors plug were tightened; I think this solved the problem; resistance of the sensor checked. Bosch wet 2820 manual pdf. It must be 4.8K at 25 degree C. And decrease when temperature increases.
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. 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)
To open Event Viewer and view events related to failover clustering: If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
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 96 hours taken 2 stream.
Microsoft Windows Download
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?
Microsoft Windows Help And Support
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
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