Error Creating Availability Group – Error: 41042 (Fixed)

While Building 50 Servers with 10 AG Groups in each Server we had to uninstall SQL and re-install again to address one of the server configuration issue. While re-installing we had challenges creating the availability group.

Final solution is to delete the AGNames from Failover Cluster Manager (Resources) and delete registry entry @ HKEY_LOCAL_MACHINE\Cluster\HadrAgNameToldMap.

Interestingly, when we create first Availability group, all 10 Registry entries were restored @ HKEY_LOCAL_MACHINE\Cluster\HadrAgNameToldMap. We had to delete appropriate entry from Registry and create availability group, repeat this process for all 10 AGs being created.

Referring to https://connectbeta.microsoft.com/SQLServer/feedback/details/2451275/uninstall-does-not-remove-ag-registry-hadragnametoldmap-and-cluster-entries, workaround/recommendation is to delete the AGs before uninstalling the SQL Server.

Please Vote to fix this bug at https://connectbeta.microsoft.com/SQLServer/feedback/details/2451275/uninstall-does-not-remove-ag-registry-hadragnametoldmap-and-cluster-entries!

Advertisements
This entry was posted in High Availability, SQL, SQL Error, Uncategorized and tagged , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s