SQL Server Home
SQL 2008 SP1 Fails with error code 0x84B20001.
Shah - MSFT
as By Design
3/7/2009 8:28:42 AM
User(s) can reproduce this bug
Installing SP1 Fails.
Server has two instances. Default instance of SQL Server 2008 and named instance of SQL Server 2005 SP1. Installation is failing with error on "SQL_Replication_core_inst".
Below are some of the things i did but the error was still there.
Disabled Publisher/Distributor on default instance
Disabled Publisher/Distributor on Named instance.
Disabled CDC on default instance.
Stopped SQL Services on default instance
private build - 10.00.9022
Windows Server 2003 (all x64 editions)
Operating System Language
Steps to Reproduce
Install SQL 2008 SP1
Installation fails with error below.
A failure was detected for a previous installation, patch, or repair for instance 'MSSQLSERVER' during configuration for features [SQL_Replication_Core_Inst,]. In order to apply this patch package (KB959337), you must resolve any issues with the previous operation that failed. View the summary.txt log to determine why the previous operation failed.
Installation should complete succesfully
to post a comment.
Please enter a comment.
on 12/16/2013 at 9:40 AM
I had to uninstall "SQL Server 2008 R2 Books Online" and then the upgrade worked.
on 7/26/2012 at 1:29 AM
The workaround posted by Trevor Seward sorted my system the registry keys I set to 1 were in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\ConfigurationState and this solved the "SQL 2008 SP1 Fails with error code 0x84B20001" windows update error that had been bugging me for months!
on 9/29/2010 at 2:46 PM
i have the problem, to but the workaround dont work. I got the messege that the integration services runs with a wrong User/Password. Is there any way update to sp1 without deinstallation/repairing the integration services? please help!
on 4/9/2010 at 5:37 AM
I have windows 7 and I am try to install SQL Server and getting this error. does any one know why????????
thanks in advance
on 7/5/2009 at 3:36 PM
See my workaround on the workarounds page. Make sure that you do "<<Repair shared components only>>", not a particular instance, when doing the Repair wizard.
on 6/25/2009 at 9:57 AM
Same deal here, edition upgrade from Ent Eval. No fix? Closed (By Design)?
on 5/13/2009 at 5:00 PM
Got same problem with single instance of SQL Server. Was upgrade edition from Ent Eval to Workgroup.
Repair does not help.
on 4/15/2009 at 4:11 AM
I am having the same issue. Per instruction to repair instance - can you be more specific? Does this mean run setu0p0 from the original dvd and choose a repair option? (Note: My installation was developer edition. No evaluation edition ever installed on this machine.)
on 4/8/2009 at 3:19 PM
got the same error, did anyone know how to fix it ?
on 3/13/2009 at 1:03 PM
I've closed this bug - if my previous advice did not help you resolve your issue please reactivate this bug and provide details.
on 3/11/2009 at 11:15 AM
Your logs indicate that your existing install needs to be Repair. Please Repair your instance and try applying SP1 again.
on 3/11/2009 at 4:23 AM
I too am having the same issue. Was the instance originally an evaluation version which you had to upgrade?
Shah - MSFT
on 3/9/2009 at 2:16 PM
Attached are log files from two different runs of the installation which both failed.
on 3/9/2009 at 1:20 PM
Please attach your logs so we can investigate.
Logs: %programfiles%\Microsoft SQL Server\100\Setup Bootstrap\log
to post a workaround.
Please enter a workaround.
on 4/16/2012 at 8:31 AM
I believe Nicholas is correct; the state is left inconsistent which is probably why MS seems unable to resolve this problem for everyone.
Due to upgrading from dev to full version, I had previously had to set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\ConfigurationState\CommonFiles to the value "3" in order for the upgrade to work. It seems that this value breaks the KB2494088 patch. Setting the value back to the original (1) value allowed the patch to proceed and finish.
on 7/18/2011 at 3:40 PM
Check the values at:
HKLM\Software\Microsoft\Microsoft SQL Server\100\ConfigurationState
You may also need to check values at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\ConfigurationState
And similar keys. If the value isn't "1" for the data (e.g. "Analysis_Server_Full", or "SQL_Engine_Core_Shared"), the installation appears to fail.
on 7/5/2009 at 3:33 PM
This seems to be a bug with the 2008 installer whenever you do an Edition Upgrade, such as if when you forgot to install Management Studio Express and did an edition upgrade to get it. The SQL Sever 2008 installer appears to leave things in an inconsistent state after doing an Edition Upgrade.
To work around this bug that Microsoft seems to think is not a bug:
Step 0. If you have Visual Studio 2008 SP1 installed, you MUST first remove "Microsoft SQL Server Compact 3.5 SP1 <Language>" via Add/Remove Programs as described in http://support.microsoft.com/default.aspx/kb/970876. (It will get re-installed later during the repair; this works around yet another bug in SQL Server 2008's installer.)
Step 1. Download and run the original self-extracting installation of SQL Server 2008. If you have installation media, you can use the "SQL Server Installation Center" option in your Start menu.
Step 2. Choose Maintenance > Repair. When asked what to repair, choose "<<Repair shared components only>>", then let the repair complete. Then close the SQL Server Installation Center. (You shouldn't have to repair any instances.)
Step 3. You should now be able to run the SP1 installer.
Good luck! Here's hoping that they rewrite the entire installer in 2010.
Shah - MSFT
Shah - MSFT
© 2014 Microsoft