Figure 8: The Select Features page of the Install a SQL Server 2008 Patch dialog box for a cumulative update After you have updated the first passive node, you can repeat the same installation steps if other passive nodes form part of your first round of planned updates. For example, if you have a four-node cluster, and you are updating two passive nodes, you would repeat the update process for each of the two passive nodes that were removed as potential hosts of the SQL Server instance. After you have completed the updates to the passive nodes, in the Failover Cluster Management tool, in the SQL Server network resource, on the Advanced Policies tab, you should reselect the updated nodes to enable hosting of the SQL Server instance. After you have re-enabled the updated nodes, you can then fail over the SQL Server instance from the node that has not been updated to an updated node. After failover to the updated node, update scripts automatically run against the engine. You can use the Failover Cluster Management tool to confirm that the SQL Server instance resources came online on the newly updated node. Then, you can confirm the version number of the SQL Server instance by
Install Windows Installer 4.5: Windows Installer 4.5 is required, and it can be installed by the Installation Wizard. If you are prompted to restart your computer, restart it, and then start SQL Server 2008 Setup again. If you want to preinstall the Windows Installer 4.5 package, you can download it from here:
Error message Scenarios Troubleshooting tips For IPv4 addresses, a portion of the mask is > 255 (for example, 346.0.0.1) IPv6 is not supported for clustering on OS versions lower than Windows Server 2008. INSTALLFAILOVERCLUSTER COMPLETEFAILOVERCLUSTER Applies to the /FAILOVERCLUSTERIPADDRESS ES setting IPv6 is only supported on Windows Server 2008 operating systems No cluster networks have a bound IPv6 address which indicates IPv6 is not supported on this machine. Bind an address to the cluster name or other resource to continue. INSTALLFAILOVERCLUSTER COMPLETEFAILOVERCLUSTER Applies to the /FAILOVERCLUSTERIPADDRESS ES setting Verify that at least one of the cluster networks available has at least one active IPv6 address bound to it The IP Address '%1' cannot use DHCP because it is not supported on this operating system. INSTALLFAILOVERCLUSTER COMPLETEFAILOVERCLUSTER Applies to the /FAILOVERCLUSTERIPADDRESS ES setting DHCP is only supported for SQL Server 2008 instances installed on Windows Server 2008 operating systems The IP Address '%1' has an invalid network name '%2'. To continue, specify an IP address with a network name and retry. INSTALLFAILOVERCLUSTER COMPLETEFAILOVERCLUSTER Applies to the /FAILOVERCLUSTERIPADDRESS ES setting The network name portion of the setting does not specify a valid network on the cluster The cluster network '%1' does not have a IPv6 address which indicates IPv6 is not supported for that network. Bind an address to the cluster name or other resource to continue. INSTALLFAILOVERCLUSTER COMPLETEFAILOVERCLUSTER Applies to the /FAILOVERCLUSTERIPADDRESS ES setting Verify that the cluster network specified for the IP address has at least one active IPv6 address bound to it No IP Address cluster resources could be found for the SQL Server failover cluster instance name '%1'. UPGRADE REPAIR REBUILDDATABASE Applies to the /FAILOVERCLUSTERIPADDRESS ES setting This validation only runs if the the instance is installed into was found The error is reported when the group the instance is installed in has no IP address resources
Error message Scenarios Troubleshooting tips Manually repair the to restore the missing resources, and run the scenario The instance specified is either not installed, or not prepared for use with failover clustering. Confirm that the correct SQL Server instance name was specified, and then run Setup again. INSTALLFAILOVERCLUSTER COMPLETEFAILOVERCLUSTER Applies to the internal /FAILOVERCLUSTERNODES setting The list of nodes is automatically calculated Verify that the instance name specified by the user is installed on some of the cluster The cluster node name '%1' is invalid. The specified computer is not a cluster node in this SQL Server failover cluster. INSTALLFAILOVERCLUSTER COMPLETEFAILOVERCLUSTER Applies to the internal /FAILOVERCLUSTERNODES setting The list of nodes is automatically calculated Verify that all the nodes reported by Setup in the instance are active members of the Windows cluster A clustered instance of SQL Server could not be found to upgrade. Possible reasons are that the wrong instance name was specified, the instance is not clustered, or Setup could not determine the failover cluster network name based on the instance name. Confirm that the correct information was specified, and then run Setup again. UPGRADE Applies to the internal /FAILOVERCLUSTERNODES setting The list of nodes is automatically calculated Verify that the instance name specified by the user is installed on some of the cluster on detected settings, the SQL Server instance is clustered, but no clustered features could be found. SQL Server Setup is unable to repair the instance due to the mismatch in detected settings. To continue, confirm that the failover cluster network name is correct and that the installed features were successfully clustered. REPAIR REBUILDDATABASE Applies to the internal /FAILOVERCLUSTERNODES setting The list of nodes is automatically calculated Verify that the instance name specified by the user is installed on some nodes of the cluster The local computer is the only node left in the failover cluster that has not been upgraded, or it is a single- UPGRADE Applies to the /FAILOVERCLUSTERROLLOWN ERSHIP setting
Error message Scenarios Troubleshooting tips The volume containing SQL Server data directory %1 does not belong to the cluster INSTALLFAILOVERCLUSTER COMPLETEFAILOVERCLUSTER Applies to the /INSTALLSQLDATADIR and related data directory settings Make sure that the path specified is on one of the disks selected for the cluster group (SLP setting /FAILOVERCLUSTERDISKS) Missing domain group. To continue, provide a valid domain group for the Database Engine service. PREPAREFAILOVERCLUSTER INSTALLFAILOVERCLUSTER UPGRADE REPAIR Applies to the/SQLDOMAINGROUP setting Required only on Windows Server 2003 for PREPAREFAILOVERCLUSTER and INSTALLFAILOVERCLUSTER, and UPGRADE from SQL Server 2000. May be required for REPAIR if the domain cannot be found. Invalid domain group. To continue, provide a valid domain group for the Database Engine service. PREPAREFAILOVERCLUSTER INSTALLFAILOVERCLUSTER UPGRADE REPAIR Applies to the /SQLDOMAINGROUP setting Verify that the group account exists and is in the same domain forest as the domain to which the cluster node is joined For Windows 2000 Server mixed-mode domains, this cannot be a domain local group. However, this situation is not diagnosed by Setup. It will show up at service startup with access-denied errors on the SQL Server error log. The service account is not valid. To continue, provide a domain account for Database Engine service. PREPAREFAILOVERCLUSTER INSTALLFAILOVERCLUSTER REPAIR Applies to the /SQLSVCACCOUNT setting Verify that the service account specified exists and is in the same domain forest as the domain to which the cluster node is joined The service account is not in the domain group. Ensure the service account is a member of the domain group for the Database Engine. PREPAREFAILOVERCLUSTER INSTALLFAILOVERCLUSTER REPAIR Applies to the /SQLSVCACCOUNT setting Verify that the service account is in the domain group specified by the /SQLDOMAINGROUP setting