- You install a new SQL Server 2008 R2 Failover cluster.
- When you configure the cluster instance, you use an IP address that is already being used. This results in a failure in feature configuration for that instance
- You try unsuccessfully to repair or uninstall that instance, and you leave the failed instance as it is.
- You install a new instance of a SQL Server 2008 R2 Failover cluster.
- The new instance is installed successfully and is put into production.
In this scenario, if you try to update the new instance with a cumulative update or a service pack, the setup fails. Additionally, you receive the following error message:
- TITLE: SQL Server Setup failure.
- SQL Server Setup has encountered the following error:
- A failure was detected for a previous installation, patch, or repair for instance '<Instance name>' during configuration for features [SQL_Replication_Core_Inst,SQL_Engine_Core_Inst,MPT_AGENT_CORE_CNI,]. In order to apply this patch package (<Package name>), you must resolve any issues with the previous operation that failed. View the summary.txt log to determine why the previous operation failed.
- A failure was detected for a previous installation, patch, or repair during configuration for features [SQL_Engine_Core_Shared,CommonFiles,SQL_WRITER,SQL_Browser_Redist,]. In order to apply this patch package (<Packagename>), you must resolve any issues with the previous operation that failed. View the summary.txt log to determine why the previous operation failed.
- Error code 0x84B20001.
The failure of the original instance sets the ConfigurationState setting of various Shared Features to a failed update state in the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\ConfigurationState
When an update is applied, it checks this registry key and returns an error if any feature is in a failed state.
To resolve this problem, repair the Shared features of SQL Server 2008 R2 running on the system by using the Add or Remove Programs item in Control Panel before you apply any updates to the working instances on the various nodes of the cluster.
For more information, see the following topic in Books Online:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.