SQL Server 2008 R2 SP1 Install failed

Question

SQL Server 2008 R2 SP1 Install failed

Damian-1673

SSCommitted

Points: 1622
More actions
May 15, 2012 at 5:51 am

#268870

Hi
for some reason my install of SP1 crashed and I cant re-run the installation again.
it gives me error as
A failure was detected for a previous installation, patch, or repair for instance 'INS2' during configuration for features [MPT_AGENT_CORE_CNI,]. In order to apply this patch package (KB2528583), 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 for instance 'INS1' during configuration for features [MPT_AGENT_CORE_CNI,]. In order to apply this patch package (KB2528583), 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.
now I tried to run the repair but that's also not going pass this point -- >
Rule "SQL Server Cluster Resource State Check" failed
now I got end up having 1 instance with SP1 and other one just a base sql2008 r2.
I have rebooted the Server many times but no luck.. its a production Server so i can reinstall.
please help!
-D

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

dan-572483 SSCoach Points: 15870 More actions · Answer 1

Cleaning up a failed SQL installtion can be a real bear, but sometime you can't reinstall until all traces of a failed installations are removed.

Here are some hints:

1) First go to add/remove programs and remove any SQL components that are listed.

2) Open regedit and delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

3) Delete the Program Files and Program Files(x86) Microsoft SQL Server folders

4) Go into local users & groups. There there may be custom users installed by SQL. Remove them.

Reboot and look again for the above items to make sure they weren't added back.

Good luck!

Sunny1 SSC Eights! Points: 871 More actions · Answer 2

I would recommand you to review the installation log on the failed instance to find out the error. There are just so many things can go wrong.

Octavian C. SSC Veteran Points: 224 More actions · Answer 3

Hi Damian,

the solution is the following. Change the key

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.<instancename>\ClusterState\MPT_AGENT_CORE_CNI and set the value to 1. All keys there should have the value 1. also the one from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.<instancename>\ConfigurationState.

This will solve the problem 100%

isd83 Ten Centuries Points: 1066 More actions · Answer 4

Modify the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.<instancename>\ConfigurationState seems has resolve the issue. But, it would be helpful to know why and what has caused the Registry value not set correctly and would there be other problems during the initial installation which may have contributed this problem.

GW

ChrisTaylor SSCarpal Tunnel Points: 4527 More actions · Answer 5

This has also worked for me. - granted it was for SP1 CU4

On reviewing the previous logs I could see that a patch done almost 1 year previous had been aborted, hence why the configurationstate was set to 3 and not 1.

Changed them to 1 and jobs a good n

_________________________________________________________________________________SQLGeordieWeb:- Jarrin ConsultancyBlog:- www.chrisjarrintaylor.co.ukTwitter:- @SQLGeordie

J Gins SSC Journeyman Points: 95 More actions · Answer 6

J Gins

SSC Journeyman

Points: 95

December 18, 2012 at 1:36 pm

#1569758

Changing the 3s to 1s worked for me also.

madhugundapaneni Valued Member Points: 74 More actions · Answer 7

We had similar issue while installing SP1 on 2 node cluster which have 8 instances.

We had to change the value from 4 to 1 for •MPT_AGENT_CORE_CNI on Configurationstate key in the registry for 6 instances.

Then sp1 installation went fine. Thanks the workaround.

Andrew G SSChampion Points: 12809 More actions · Answer 8

SP2 has been out since July 2012, why are you installing SP1?

sscdba SSC Enthusiast Points: 103 More actions · Answer 9

Wonderfull 😀

Changing the registry entries worked for me too.

THANKS!

Octavian C. SSC Veteran Points: 224 More actions · Answer 10

sscdba (8/25/2016)
Wonderfull 😀
Changing the registry entries worked for me too.
THANKS!

Hi,

I am glad that helped. i strongly recommend for 2008 R2 to install the latest service pack (3). I use for example the following blog to check the latest versions and release date http://sqlserverbuilds.blogspot.com/[/url]

The update has been out there for a while.

Regards,

Octavian