Symptoms

Assume that you use Always On availability groups (AG) in Microsoft SQL Server 2014, 2016 or 2017, and there is one node that's not reachable in a cluster. For example, you add an incoming firewall rule to block TCP port 135, 137, 139, or 445.

In this scenario, when you install an instance of SQL Server in the cluster, the SQL Server installer scans all cluster nodes for a duplicate instance name. If any of the other cluster nodes are unreachable, the installation is unsuccessful.

Resolution

The fix for this issue is included in the following updates for SQL Server:

          Cumulative Update 13 for SQL Server 2017

          Cumulative Update 5 for SQL Server 2016 SP2

Cumulative Update 1 for SQL Server 2014 Service Pack 3

This fix adds a new SkipRule switch to bypass remote node discovery. To add this switch in a SQL Server installation, use the following format:

setup /SkipRules=Cluster_VerifyForErrors_Instance_Name /ACTION=Install

Each new build for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server: 

Latest cumulative update for SQL Server 2017

Latest cumulative update for SQL Server 2016    

SQL Server 2014 build versions

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology Microsoft uses to describe software updates.

Har du brug for mere hjælp?

Udvid dine færdigheder
Gå på opdagelse i kurser
Få nye funktioner først
Deltag i Microsoft insiders

Var disse oplysninger nyttige?

Hvad påvirkede din oplevelse?

Tak for din feedback!

×