SQL Server 2012 SP4 Patch Failed on 1 node in AG Cluster.

Hi EE,

An upgrade to SQL server 2012 SP4 has failed, context:

I'm patching a 2 node AG cluster the first patch has been applied to secondary node successfully:

I then failed over the secondary node.  Then I began patching primary node:

The primary node patch failed I have got no idea why it failed and the SQL instance is no longer accessible.

I restored from a VM snapshot, tried it again and got the same error.  

Looking at these error log files I can't make sense of what went wrong.

Any assistance is appreciated.

Thank you
ERRORLOG.txt
ERRORLOG1.txt
ERRORLOG2.txt
ERRORLOG3.txt
ERRORLOG4.txt
ERRORLOG5.txt
ERRORLOG6.txt
ZackGeneral IT Goto GuyAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
>> The primary node patch failed I have got no idea why it failed and the SQL instance is no longer accessible.

Have you tried restarting the server to see whether it helped or not..

>> I restored from a VM snapshot, tried it again and got the same error.

Instead, can you try re configuring that node and make it as a valid secondary node..
ZackGeneral IT Goto GuyAuthor Commented:
Hi Raja,

Have you tried restarting the server to see whether it helped or not..

- I did the SQL server was unresponsive according to the data logs the master database was corrupt.

Instead, can you try reconfiguring that node and make it as a valid secondary node.

- I made that node the secondary node before I commenced the update.

Any other ideas?

Thank you.
Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
>> I did the SQL server was unresponsive according to the data logs the master database was corrupt

Have you tried fixing corrupted master database by rebuilding it or restoring from a backup..

Instead, can you try reconfiguring that node and make it as a valid secondary node.

I mentioned to rebuild the SQL Server instance completely and add it as a new node to your AG group..
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

ZackGeneral IT Goto GuyAuthor Commented:
Hi Raja,

I did try fixing the corrupted master database by restoring from the backup, but the SQL server was still showing as the same version.

Second query:  I mentioned to rebuild the SQL Server instance completely and add it as a new node to your AG group..

I could try de-attach the node completely:

https://www.mssqltips.com/sqlservertip/4231/how-to-remove-node-from-a-sql-server-failover-cluster/

Then try patch the server.

The question I would have is would the cluster work with only 1 node on it.

Just to reiterate the cluster consists of 2 nodes and 1 witness server.

Thank you.
ZackGeneral IT Goto GuyAuthor Commented:
Hi Raja.

Correcting technical details

I did try fixing the corrupted master database by restoring from the backup, but the SQL server was still showing as the same version.

Second query:  I mentioned to rebuild the SQL Server instance entirely and add it as a new node to your AG group.

I could try de-attach the node completely:

https://www.mssqltips.com/sqlservertip/4619/removing-a-secondary-replica-from-a-sql-server-alwayson-availability-group/

Then try patch the server.

The question I have is would the AG work with only one node on it.

Just to reiterate the cluster consists of 2 nodes and 1 witness server.

Thank you.
Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
>> The question I have is would the AG work with only one node on it.

Yes, technically out of the 2 nodes, if Primary goes down due to any reason, then secondary will take over and act as Primary..
But the problem working with only one node is if that node gets any failure, then your applications can't connect at all as no nodes are active..

So, you have time now to fix the secondary node completely and add it correctly..
Hope this clarifies..

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ZackGeneral IT Goto GuyAuthor Commented:
Thank you Raja my apologies for the delay in the acceptance of the answer.
Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
No issues, glad to assist..
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.