CU Failed however SQL Upgraded

Question

CU Failed however SQL Upgraded

Steve Q-426954

SSC-Addicted

Points: 450
More actions
July 8, 2014 at 6:42 am

#397021

All,
I was updating (CU) a node of an AG, this was an Asnc copy in a different subnet than my production copy. SQL 2012 SP1 EE.
I tried upgrading to 3 different CU's. Each time it showed the database engine failed, however SQL showed the new version, and in the SQL Logs I see the upgrade scripts running.
Error from log
There was an error to lookup cluster resource types. Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 4104. Description: .
Error code: 0x86D80018
Any Ideas?
Q

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

SqlZen SSC Enthusiast Points: 110 More actions · Answer 1

Seems to be a cluster problem.

Check this : http://social.msdn.microsoft.com/Forums/wpapps/en-US/ae7008a9-0b42-4a5c-a8c3-3446281733fe/add-node-failure-on-sql-2012-failover-cluster

Steve Q-426954 SSC-Addicted Points: 450 More actions · Answer 2

thanks for the reply. I dont think this is related.

Any other ideas?

sql-lover SSCoach Points: 18530 More actions · Answer 3

Steve Q-426954 (7/8/2014)
All,
I was updating (CU) a node of an AG, this was an Asnc copy in a different subnet than my production copy. SQL 2012 SP1 EE.
I tried upgrading to 3 different CU's. Each time it showed the database engine failed, however SQL showed the new version, and in the SQL Logs I see the upgrade scripts running.
Error from log
There was an error to lookup cluster resource types. Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 4104. Description: .
Error code: 0x86D80018
Any Ideas?
Q

Maybe a DLL was not properly updated on one of the nodes?

Did you check all your AG and ensure you can fail-over to any of them? Check MS-SQL version once you moved to any of them.

Rudyx - the Doctor SSC-Forever Points: 43695 More actions · Answer 4

Let me guess ... the CU ran for longer than normal.

If this is the case look at the SQL errorlog and you will see a series of messages in the log indicating that so-and-so could not connect because the SQL Server was in 'single user' mode.

We recently ran into this situation when applying a CU to a normal SQL Server. We had to stop the SCOM and SEP services - they were connecting into the SQL instance when the CU process was trying to get in and execute scripts in the master database while the engine was in 'single user' mode.

SCOM and SEP may not be the only services, maybe 'Always On' is shooting you down as well.

Take heart though, once you find the culprit and terminate their access the CU will update normally.

RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

SqlZen SSC Enthusiast Points: 110 More actions · Answer 5

Check section Upgrading to a SQL Server 2012 Multi-Subnet Failover Cluster at

http://msdn.microsoft.com/en-us/library/ms191295(v=sql.110).aspx