The specified IP Address '%1' is a reserved IP address. To continue, specify an IP address that does not end in '.0'. Applies to the setting For IPv4 addresses, confirm that the last quartet of the address is not .0 The IP Address '%1' is already in use. Pick another IP address to continue. Applies to the setting For IPv4 addresses, the address is assigned to a device on the network The subnet mask '%1' is invalid. To continue, specify a valid subnet mask, then try again. Applies to the setting The subnet mask was not specified in the setting For IPv4 addresses, the mask is not correct (that is, it doesn’t match the format XXX.XXX.XXX.XXX) 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. Applies to the 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. Applies to the setting Verify that at 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. Applies to the 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 valid network name and retry. Applies to the setting The network name portion of the setting does not specify a valid network on the cluster
Based 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 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 local computer is the only node left in the failover cluster that has not been upgraded, or it is a single-node failover cluster. As part of the upgrade of the local computer, ownership of the failover cluster group must be transferred to the upgraded version of SQL Server. The only valid options for the %1 setting in this scenario are 1 or 2. UPGRADE Applies to the setting Remove the setting from the command line, or change the value to 1 or 2 The failover cluster group is already owned by the upgraded nodes of the SQL Server instance, so it is not possible to transfer ownership to the newer version again. The only valid options for the %1 setting in this scenario are 0 or 2. UPGRADE Applies to the setting Remove the setting from the command line, or change the value to 0 or 2 The local node of the failover cluster has already been upgraded, and no other nodes have been upgraded. It is not possible to run upgrade on the local node again. UPGRADE Applies to the setting Remove the setting from the command line, or change the value to 0 or 2 Run upgrade on a another node of the cluster, because the node was already upgraded None of the nodes in the failover cluster have been upgraded yet. Because of this, it is not possible for the ownership of the failover UPGRADE Applies to the setting
The service account is not valid. To continue, provide a domain account for Database Engine service. 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. REPAIR Applies to the /SQLSVCACCOUNT setting Verify that the service account is in the domain group specified by the /SQLDOMAINGROUP setting The SQL Server service domain group or account does not match with that on the remaining cluster nodes. REPAIR Indicates that was run for the same instance id on different cluster nodes without specifying identical values for /SQLDOMAINGROUP and /SQLSVCACCOUNT You must run REMOVENODE on each of the nodes that are incorrect and then rerun specifying the correct values Invalid or missing username or password. To continue, provide valid credentials for the Database Engine service. ADDNODE REPAIR This applies to the /SQLSVCACCOUNT and /SQLSVCPASSWORD settings In particular, for ADDNODE, the password needs to be respecified for the Database Engine service because the password cannot be acquired from the active node SQLBrowser: SQL Server Browser Install for feature generated exception, and will invoke option. The exception: Failed to open registry key ADDNODE (Note: SQL Server Browser does not have cluster-specific failures. SQL Server Browser does not have cluster specific failures. This error indicates that the Database Engine or Analysis Services MSI is not installed correctly; however, this is not cluster-specific.
REPAIR (Cluster only) ADDNODE The specified SQL Server instance does not have a SQL Agent service that Setup can successfully start. UPGRADE (Standalone instance only) The SQL Server Agent service of the SQL Server instance to be upgraded cannot be started. Ensure that the SQL Server Agent service can start before performing the upgrade. The associated is performed for an upgrade of a stand-alone instance only. On a domain controller, the SQL Server Agent service account cannot be a built-in account. INSTALL REPAIR For SQL Server instances on a domain controller machine, the SQL Server Agent service account cannot be a built-in account such as Network Service. Use a user account instead. The AGTSVCSTARTUPTYPE start mode must be Manual for Clustering. The service startup mode must be Manual when installing a clustered instance. The specified SQL Server Agent service account is not a valid user account. INSTALL REPAIR ADDNODE The SQL Server Agent service account has to be a user account. It cannot be a local group such as BUILTIN\Administrators. The SQL Agent service domain group could not be recovered. To complete repair, SQL Agent Service domain group must be provided. REPAIR (Cluster only) In repairing the SQL Server service of a clustered instance, the domain group of SQL Server Agent could not be found. To complete repair, provide the SQL Server Agent domain group that was specified during installation of the instance being repaired. The SQL Server Agent service (SQLServerAgent) is missing and REPAIR(Cluster only) In repair of a clustered SQL Server instance, the SQL
manually at the end of the upgrade. the OLAP administrator after the upgrade. Unable to connect to Analysis Services server, '%1'. Ensure that the service is accessible. UPGRADE Make sure the firewall is not blocking access to the active node during the upgrade. The user must be an OLAP administrator to update the settings. Change the settings manually at the end of the upgrade. UPGRADE The account under which Setup runs must be an OLAP administrator in order to update the config values. If you receive this error, the account does not have OLAP administrator permissions; after the upgrade, you can manually change the settings. The cluster resource is not online. Bring the Analysis Services server online before starting the upgrade process. UPGRADE The resource to be online during the upgrade. Service Account, '%1', is not part of the domain group, '%2'. REPAIR To solve this problem, add the service account to the domain group The service account could not be retrieved. Use the ASSVCACCOUNT service account command line parameter to specify the service account. REPAIR During repair, Setup was unable to get the service account. Pass the service account and password in the command line to proceed with the repair process. The configuration path could not be retrieved from the active node. Check whether you can reach the active node from the given node. REPAIR During repair, Setup tries retrieve the config path from active node; if Setup is unable to retrieve the information, Setup was not able reach the active node. Ensure that the active node can be reached from the computer you are repairing. No user name was provided. Use the ASSVCACCOUNT command line parameter to specify a user name. REPAIR During repair, Setup was unable to get the service account. Pass the service account and password in the command line to proceed with the repair process. Unable to connect to the active node. REPAIR During repair, make sure the passive node can reach the active node. Verify that there are no network problems.
The service account is different from the active node. Use the SQL Configuration Manager to change the service account to match the active node. REPAIR During repair, Setup validates whether the passive node service account is the same as active node service account. If it is different, change the account using SQL Server Configuration Manager. The domain group, '%1', does not exist on the active node. Specify a valid domain group. REPAIR The domain group might be missing. Provide the domain group through a command line parameter for repair. The domain group does not exist on the active node. Specify a valid domain group. REPAIR The domain group might be missing; provide the domain group through a command line parameter for repair. The Service Start Mode parameter cannot be disabled on the active node. Change the service state to either manual or automatic using the SQL Configuration Manager. REPAIR None. The domain group was not provided. Specify the domain group on the command line. REPAIR The domain might be missing; provide the domain group through a command line parameter for repair. The configuration path was not provided. Provide the configuration path on the command line. REPAIR The configuration path might be missing on the active node; provide a configuration path through command line The configuration path is not valid. Specify a valid configuration path. REPAIR Provide valid configuration path through the command line The configuration path is not valid on the active node. Specify a valid configuration path on the active node. REPAIR Make sure the configuration path is and accessible The configuration path is not accessible. Check whether you can access the disk from the given machine. REPAIR Make sure the configuration path is valid and accessible
The configuration path is not part of a valid shared disk. Specify a valid shared disk. REPAIR Make sure the configuration path is valid and accessible Troubleshooting Error Messages in “*ErrorLog” Files message Scenarios Troubleshooting tips Removal of clustered feature %1 is not supported UNINSTALL This happens when the user tries to remove a clustered feature via /ACTION UNINSTALL instead of /ACTION REMOVENODE The value of 1 in the <InstId>\ClusterState key triggers this block Install of feature %1 is not supported on clustered instance INSTALL UPGRADE This occurs when the instance the user specified is already installed on the machine, and the instance contains clustered features, and the user is trying to add additional stand-alone features. It is not possible to install nonclustered features to a clustered instance. Values of 1 or 2 in the <InstId>\ClusterState key trigger this block The CPU platform for the %1 feature is inconsistent between the nodes of the cluster. To cluster an instance, the platform of the instance COMPLETEFAILOVERCLUSTER ADDNODE This occurs when believes the platform of the instance is not consistent on some of the nodes, for example, one instance is 32-bit and the other one is For remote detection, the platform of the installation is determined by which side of the registry the registry value was