Hi, I posted my situation on a similar question in this forum (https://social.msdn.microsoft.com/Forums/en-US/5d0b9896-d866-40c2-8e36-4009e337ddd1/alwayson-failure-exception-41005?forum=sqldisasterrecovery) but no one has replied to this point.
My layout is 2 primary synchronous nodes, 2 secondary asynch DR nodes, and a file share witness, and while I was rebooting my 2 DR nodes my AG failed over to the synchronous partner on the primary site. I received the same error as the post I
mentioned earlier.
Message
Failed to update Replica status within the local Windows Server Failover Clustering (WSFC) due to exception 41005.
In addition to exception 41005 I also received 41034 and 41000.
After failing over the AG ran fine without issue. My question is..why did I lose quorum? I'm using node and file share Majority, I'm supposed to be able to withstand the loss of 2 nodes out of my 4 as long as the file share witness remains online, and it did. Also..the 2 nodes we rebooted didn't even have a vote for quorum. We changed their nodeweight to 0, so the only quorum voting members were both still online, as was the File Share, yet our prod db had a brief outage as it failed over to the synchronous partner.