Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server 2008 R2 SP1 Install failed Expand / Collapse
Author
Message
Posted Tuesday, May 15, 2012 5:51 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, February 20, 2014 4:01 AM
Points: 101, Visits: 259
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



Post #1300148
Posted Tuesday, May 15, 2012 3:37 PM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Friday, September 26, 2014 3:00 PM
Points: 554, Visits: 1,621
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!
Post #1300641
Posted Wednesday, May 16, 2012 11:35 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: 2 days ago @ 3:35 PM
Points: 30, Visits: 599
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.
Post #1301247
Posted Saturday, May 19, 2012 1:30 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, August 11, 2013 1:30 PM
Points: 1, Visits: 12
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%
Post #1303061
Posted Tuesday, September 11, 2012 4:58 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, September 19, 2014 5:19 PM
Points: 56, Visits: 572
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




Post #1357744
Posted Tuesday, December 11, 2012 4:50 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 2:03 AM
Points: 398, Visits: 1,722
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


Chris

Blog:- chrisjarrintaylor.co.uk
Twitter:- @SQLGeordie
Post #1395047
Posted Tuesday, December 18, 2012 1:36 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, May 10, 2014 7:34 PM
Points: 1, Visits: 44
Changing the 3s to 1s worked for me also.
Post #1398016
Posted Thursday, June 5, 2014 12:29 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, September 15, 2014 3:14 AM
Points: 2, Visits: 56
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.
Post #1577632
Posted Thursday, June 5, 2014 12:41 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 10:49 PM
Points: 1,237, Visits: 1,719
SP2 has been out since July 2012, why are you installing SP1?
Post #1577638
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse