Unable to Failover After Applying SP2 CU13
-
Our environment is a two-node cluster (Active/Passive) and after applying the latest patch to the passive node, I am no longer able to failover so I can apply the patch to the other node. It's strange that when I uninstall CU13, which rollbacks to CU12, then it works just fine. The Windows error logs don't provide much detail and I don't see anything in the SQL logs. I've attached what I see in the Windows logs below. It also might be worth noting that I changed the sa password prior to applying the patch but failover worked prior and again after rolling back. A couple things I'm thinking are:
1. Is anyone else seeing an issue with SP2 CU13?
2. Did changing the sa password impact applying patches in any way?Any other suggestions or things to look are are appreciated. Thanks!
-
After no luck finding meaningful error messages or finding information online, I decided to tear into the registry. It's important to note that I did also change the structure and lettering of my disks recently but never thought that would be the issue since failover between the nodes worked fine with CU12 and even the disks were failing over successfully after applying CU13 to the secondary node. I discovered the SQLDataRoot still had a reference to an old disk which was causing the issue. Bottom line is I finally figured it out but still not sure why CU12 to CU12 was working but not CU12 to CU13.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply