You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-sql/virtual-machines/windows/failover-cluster-instance-azure-shared-disks-manually-configure.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,16 +148,14 @@ After you've configured the failover cluster and all cluster components, includi
148
148
149
149
1. In **Failover Cluster Manager**, make sure that all core cluster resources are on the first virtual machine. If necessary, move the disks to that virtual machine.
150
150
151
-
1. If the version of operating system is Windows Server 2019 and windows cluster was created using the default [**Distributed Network Name (DNN)**](https://blogs.windows.com/windows-insider/2018/08/14/announcing-windows-server-2019-insider-preview-build-17733/), then FCI installation for SQL Server 2017 and below will fail with following error:
151
+
1. If the version of the operating system is Windows Server 2019 and the Windows Cluster was created using the default [**Distributed Network Name (DNN)**](https://blogs.windows.com/windows-insider/2018/08/14/announcing-windows-server-2019-insider-preview-build-17733/), then the FCI installation for SQL Server 2017 and below will fail with the error`The given key was not present in the dictionary`.
152
152
153
-
**The given key was not present in the dictionary**
154
-
155
-
SQL Server FCI installation queries for existing Virtual Network Name (VNN) and doesn't recognize the Windows Cluster DNN. The issue has been fixed in SQL Server 2019 setup. For SQL Server 2017 and below, follow these steps to avoid FCI installation error:
153
+
During installation, SQL Server setup queries for the existing Virtual Network Name (VNN) and doesn't recognize the Windows Cluster DNN. The issue has been fixed in SQL Server 2019 setup. For SQL Server 2017 and below, follow these steps to avoid the installation error:
156
154
157
-
- In Failover Cluster Manager, connect to the cluster, rightclick **Roles** and select **Create Empty Role**
158
-
- Rightclick the newly created empty role, select **Add Resource** and select **Client Access Point**
159
-
- Enter any name and complete the wizard to create **Client Access Point**
160
-
-Upon completion of SQL Server FCI installation, this role which contains just the temporary **Client Access Point** can be deleted.
155
+
- In Failover Cluster Manager, connect to the cluster, right-click **Roles** and select **Create Empty Role**.
156
+
- Right-click the newly created empty role, select **Add Resource** and select **Client Access Point**.
157
+
- Enter any name and complete the wizard to create the **Client Access Point**.
158
+
-After the SQL Server FCI installation completes, the role containing the temporary **Client Access Point** can be deleted.
161
159
162
160
1. Locate the installation media. If the virtual machine uses one of the Azure Marketplace images, the media is located at `C:\SQLServer_<version number>_Full`.
0 commit comments