June 8, 2016 at 5:54 am
When you uninstalled your ins1, ins2, did you clean out the redundant virtual names from AD?
If AD still has an entry that relates to the original ins1 Agent name, then the SID entry within it will not match the currently installed Agent. This could prevent your Agent group from authenticating with AD, which would stop it coming online to the cluster. You can check (and correct if needed) this level of detail within AD with ASDI Edit, but make sure you know what you are doing before updating AD.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
September 20, 2017 at 11:06 am
I know this is an old issue, but one I ran into as well some months back. The solution is to uninstall / reinstall ODBC drivers as there is a bug the fix for which did not make it into SP1. Please see my update on SP1 release blog under "sqlGDBA" here : https://blogs.msdn.microsoft.com/sqlreleaseservices/sql-server-2016-service-pack-1-sp1-released/
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply