6There was an error to lookup cluster name. Error: {0}
6There was an error to lookup cluster nodes. Error: {0}
7There was an error to lookup cluster groups. Error: {0}
9There was an error to lookup cluster networks. Error: {0}
:There was an error to lookup cluster resources. Error: {0}
?There was an error to lookup cluster resource types. Error: {0}
@Setup was unable to find the cluster network name '{0}' via WMI.
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.
CThe network prefix for the resource '{0}' could not be determined as an error occurred. Error: {1}
CThere was an error to lookup cluster network interfaces. Error: {0}
GThere was an error to add cluster node '{0}' as a possible owner of cluster resource '{1}'. Error: {2}
GThere was an error to lookup disk volumes for cluster resource '{0}', Disk property evaluated to null..
HThere was an error to rename the cluster group name to '{0}'. Error: {1}
IThere was an error setting restart period for resource '{0}'. Error: {1}
JThere was an error setting pending timeout for resource '{0}'. Error: {1}
JThere was an error setting the requires separate resource monitor property for resource '{0}'. Error: {1}
LSetup was unable to set the IP address dependencies for the cluster network name '{0}' to '{1}'. Error: {2}
LThe restart action '{1}', restart threshold '{2}', restart period '{3}' could not be set for resource '{0}'.
LThere was an error getting the validation status of the cluster. Error: {0}
LThere was an error setting restart threshold for resource '{0}'. Error: {1}
MSetup was unable to query WMI for the cluster network name '{0}'. Error: {1}
NSetup was unable to search WMI for the cluster network name '{0}'. Error: {1}
PThere was an error to lookup disk volumes for cluster resource '{0}'. Error: {1}
RThere was an error to lookup resource class for cluster resource '{0}'. Error: {1}
SThe resource restart action could not be determined for resource '{0}'. Error: {1}
SThe resource restart period could not be determined for resource '{0}'. Error: {1}
Setup was unable to open a WMI connection on machine {0} in order to set the IP address dependencies for the cluster network name '{1}'. Error: {2}
TThere was an error getting cluster resources for the cluster group '{0}'. Error: {1}
TThere was an error looking up private property '{0}' for resource '{1}'. Error: {2}
The MSDTC service is not running on computer {0}. Some SQL Server features require the MSDTC service. If MSDTC is clustered, verify that the MSDTC service is up and running through Cluster Administrator. If the MSDTC service is not clustered, start the MSDTC service through the Services MMC snap-in.
The cluster resource '{0}' could not be brought online due to an error bringing the dependency resource '{1}' online. Refer to the Cluster Events in the Failover Cluster Manager for more information.
There was an error during the SQL Server upgrade operation. Setup failed to move the failover cluster resource group and bring it online. To continue this upgrade operation, bring the resource group online manually and retry Setup. Reason: {0}
This is the only node in the SQL Server failover cluster. During the upgrade process, SQL Server Setup will restart the SQL Server resource group and complete the database upgrade. Applications will not be able to connect to SQL Server services while the database upgrade is in progress.
VThere was an error to lookup private properties for cluster resource '{0}'. Error: {1}
YThere was an error removing possible owner '{0}' from cluster resource '{1}'. Error: {2}
^There was an error getting the cluster group preferred owner nodes for group '{0}'. Error: {1}