SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server 2008 R2 SP1 Install failed


SQL Server 2008 R2 SP1 Install failed

Author
Message
Damian-1673
Damian-1673
Old Hand
Old Hand (365 reputation)Old Hand (365 reputation)Old Hand (365 reputation)Old Hand (365 reputation)Old Hand (365 reputation)Old Hand (365 reputation)Old Hand (365 reputation)Old Hand (365 reputation)

Group: General Forum Members
Points: 365 Visits: 289
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
dan-572483
dan-572483
Hall of Fame
Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)

Group: General Forum Members
Points: 3613 Visits: 2000
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
Sunny1
SSC Veteran
SSC Veteran (221 reputation)SSC Veteran (221 reputation)SSC Veteran (221 reputation)SSC Veteran (221 reputation)SSC Veteran (221 reputation)SSC Veteran (221 reputation)SSC Veteran (221 reputation)SSC Veteran (221 reputation)

Group: General Forum Members
Points: 221 Visits: 753
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.
Octavian C.
SSC Journeyman
SSC Journeyman (90 reputation)SSC Journeyman (90 reputation)SSC Journeyman (90 reputation)SSC Journeyman (90 reputation)SSC Journeyman (90 reputation)SSC Journeyman (90 reputation)SSC Journeyman (90 reputation)SSC Journeyman (90 reputation)

Group: General Forum Members
Points: 90 Visits: 40
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
isd83
SSC Veteran
SSC Veteran (231 reputation)SSC Veteran (231 reputation)SSC Veteran (231 reputation)SSC Veteran (231 reputation)SSC Veteran (231 reputation)SSC Veteran (231 reputation)SSC Veteran (231 reputation)SSC Veteran (231 reputation)

Group: General Forum Members
Points: 231 Visits: 574
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



Chris Taylor
Chris Taylor
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1308 Visits: 1918
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

_________________________________________________________________________________

SQLGeordie

Web:- Jarrin Consultancy
Blog:- www.chrisjarrintaylor.co.uk
Twitter:- @SQLGeordie
J Gins
J Gins
SSC Rookie
SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)

Group: General Forum Members
Points: 29 Visits: 44
Changing the 3s to 1s worked for me also.
madhugundapaneni
madhugundapaneni
Grasshopper
Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)

Group: General Forum Members
Points: 24 Visits: 72
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
Andrew G
SSCarpal Tunnel
SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)

Group: General Forum Members
Points: 4077 Visits: 2282
SP2 has been out since July 2012, why are you installing SP1?
sscdba
sscdba
SSC Rookie
SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)

Group: General Forum Members
Points: 25 Visits: 8
Wonderfull :-D
Changing the registry entries worked for me too.
THANKS!
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search