Microsoft Developer Network > Forums Home > SQL Server Forums > SQL Server Setup & Upgrade > Security Update for SQL Server 2008 R2 (KB2494088) failed with Error Code: 0x84B20001

Unanswered Security Update for SQL Server 2008 R2 (KB2494088) failed with Error Code: 0x84B20001

  • Tuesday, June 28, 2011 4:15 PM
     
     

    I have Windows XP. I installed SQL EXpress to use while learning C# using books (for C#). Everything I did was mostly through Visual Studio IDE, so my SQL knowlege is very limited. Though I installed SQL Express I see in Windows Explorer and Registry in the folder "Microsoft SQL Server" two folders "MSSQL10.SQLEXPRESS" and "MSSQL10_50.MSSQLSERVER". I don't recall ever installing full version of SQL Server (it's not free). I installed operating system myself on a clean hard drive. So now when failed update refers to "Security Update for SQL Server 2008 R2 (KB2494088)" does it refer to SQL Express? (Thinking that somehow I have full version of SQL server I tried to remove it from Control Panel  -"Add and Remove programms" but the only titles I see are (don't see any Express):

    Microsoft SQL Server 2008,   Microsoft SQL Server 2008 R2,   Microsoft SQL Server 2008 R2 Data-Tier Application Framework,   Microsoft SQL Server 2008 R2 Data-Tier Application Project,   Microsoft SQL Server 2008 R2 Management Objects, Microsoft SQL Server 2008 R2 Native Client,   Microsoft SQL Server 2008 R2 Policies,   Microsoft SQL Server 2008 R2 Setup (English),   Microsoft SQL Server 2008 R2 Transact-SQL Language Service, Microsoft SQL Server 2008 Setup Support Files,   Microsoft SQL Server Browser,   Microsoft SQL Server Compact 3.5 SP2 ENU,   Microsoft SQL Server Compact 3.5 SP2 Query Tools ENU,   Microsoft SQL Server Database Publishing Wizard 1.4,   Microsoft SQL Server System CLR Types, Microsoft SQL Server VSS Writer.

    Do I have just SQL EXpress installation? What I can safely remove (if it's not Express) and avoid installing failing update (first solution)

    If not.

    Everytime I start the computer Automatic updates  asks me if I want to install new updates. Recently it's Security Update for SQL Server 2008 R2 (KB2494088). Everytime I click "OK" Installation starts but in 1 min fails with "Some updates could not be installed" (and below "The following updates were not installed: Security Update for SQL Server 2008 R2 (KB2494088)". Now, every time I shut computer it tells me not to turn off the power - it will be turned off when updates are installed. Meaning the update for SQL Server because I know there were no other updates in the list. How could that be if update failed in the first place - computer trying to install it again while shutting down??? And even if I don't try to install any updates (Ignoring little yellow shield in the right bottom corner on the Task Bar) I still get the same warning not turn off the power because computer will install new updates. It fails as well because after turning computer on again I see the same offer to install Security Update for SQL Server 2008 R2 (KB2494088).

    What is the best solution? Thank you in advance.


    Vitaly Novikov

All Replies

  • Tuesday, June 28, 2011 6:49 PM
     
     

    Hello,

    The update applies to the SQL Server 2008 R2 instance. That instance is not the Express Edition.

    Please try to repair SQL Server 2008 R2 first, and then let Windows Update apply again the KB2494088 update or apply it yourself manually.

    http://msdn.microsoft.com/en-us/library/cc646006(v=SQL.105).aspx 


    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

  • Wednesday, June 29, 2011 3:29 AM
     
     

    Tryed to repair - failure. Tried several times.  This instance was installed by downloading and extracting files from Microsoft site (R2 Express edition). Failure includes problem accessing folder where setup.exe file was extracted though I manually went there and launched setup.exe to start repair. Sorry, no idea what to do next. Even tried to uninstall SQL Server 2008 (not R2) from Add and remove programs - removes succesfully - thats what it writes but then it's still there and working properly with other applications (means was not removed). Is it only me or SQL Server 2008 has lots of problems generally and it's best to avoid using it?

    Here is a log:

    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2068052700
      Exit facility code:            1212
      Exit error code:               1316
      Exit message:                  Failed: see details below
      Start time:                    2011-06-28 23:08:18
      End time:                      2011-06-28 23:11:47
      Requested action:              Repair
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110628_230735\SSCRuntime_Cpu32_1.log
      Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1

    Machine Properties:
      Machine name:                  COMPANY-01A2BAC
      Machine processor count:       2
      OS version:                    Windows XP
      OS service pack:               Service Pack 3
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No

    Product features discovered:
      Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services                 1033                 Express Edition      10.1.2531.0     No       
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication                   1033                 Express Edition      10.1.2531.0     No       
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services                 1033                 Express Edition      10.50.1600.1    No       
      Sql Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         SQL Server Replication                   1033                 Express Edition      10.50.1600.1    No       
      Sql Server 2008 R2                                                       Management Tools - Basic                 1033                 Express Edition      10.50.1600.1    No       

    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         d:\0d604c098500816a96444fac29ee\x86\setup\
      Installation edition:          EXPRESS_ADVANCED

    User Input Settings:
      ACTION:                        Repair
      AGTDOMAINGROUP:                <empty>
      AGTSVCACCOUNT:                 <empty>
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASCONFIGDIR:                   Config
      ASDOMAINGROUP:                 <empty>
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      CONFIGURATIONFILE:            
      ENU:                           True
      FAILOVERCLUSTERGROUP:          <empty>
      FAILOVERCLUSTERNETWORKNAME:    <empty>
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 *****
      HELP:                          False
      IACCEPTSQLSERVERLICENSETERMS:  False
      INDICATEPROGRESS:              False
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      PASSPHRASE:                    *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      SQLDOMAINGROUP:                <empty>
      SQLSVCACCOUNT:                 <empty>
      SQLSVCPASSWORD:                *****
      UIMODE:                        AutoAdvance
      X86:                           False

      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110628_230735\ConfigurationFile.ini

    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:      0x4971D227@1204@2
      Configuration error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110628_230735\Detail.txt
      Configuration status:          Failed: see details below
      Configuration error code:      0x4971D227@1204@2
      Configuration error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110628_230735\Detail.txt
      Configuration status:          Failed: see details below
      Configuration error code:      0x4971D227@1204@2
      Configuration error description: The SQL Server feature 'SQL_Replication_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110628_230735\Detail.txt
      Configuration status:          Failed: see details below
      Configuration error code:      0x4971D227@1204@2
      Configuration error description: The SQL Server feature 'SQL_Replication_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110628_230735\Detail.txt

      Feature:                       SQL Client Connectivity
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       SQL Writer
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       SQL Browser
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:      0x4971D227@1204@2
      Configuration error description: The SQL Server feature 'SQL_Replication_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110628_230735\Detail.txt
      Configuration status:          Failed: see details below
      Configuration error code:      0x4971D227@1204@2
      Configuration error description: The SQL Server feature 'SQL_Replication_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110628_230735\Detail.txt
      Configuration status:          Failed: see details below
      Configuration error code:      0x4971D227@1204@2
      Configuration error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110628_230735\Detail.txt
      Configuration status:          Failed: see details below
      Configuration error code:      0x4971D227@1204@2
      Configuration error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110628_230735\Detail.txt

      Feature:                       SQL Compact Edition Tools
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       SQL Compact Edition Runtime
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed

      Feature:                       Microsoft Sync Framework
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed

    Rules with failures:

    Global rules:

    There are no scenario-specific rules.

    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110628_230735\SystemConfigurationCheck_Report.htm


    Vitaly Novikov
  • Friday, July 01, 2011 8:55 AM
    Moderator
     
     

    Hi Vitaly Novikov,

     

    Based on the error log, we could see that you have two instances installed on your computer as follows:

     

    • SQL Server 2008 Express(this is the named instance: MSSQL10.SQLEXPRESS)
    • SQL Server 2008 R2 Express(this is the default instance: MSSQL10_50.MSSQLSERVER)

     

    And you are using SQL Server 2008 R2 EXPRESS_ADVANCED to repair, EXPRESS_ADVANCED is the installation media for SQL Server Express with Advanced service edition, this mean that it could only repair the instance of SQL Server Express with Advanced service edition, but all your instance are SQL Server Express edition. They are different.

     

    Please try to download the SQL Server Express edition from the below website and try to repair instances separately and correspondingly:

    SQL Server 2008 Express edition: http://www.microsoft.com/download/en/details.aspx?id=1695

    SQL Server 2008 R2 Express edition: http://www.microsoft.com/sqlserver/en/us/editions/express.aspx

     

    After the repair succeed,  you could check this website for the latest service pack for each version of instance and apply them in your need.

     

    For the Windows Update alerts, you can hide it if you are sure that this updates has been applied or you do not need it, for more detailed please check here.

     

    If there are any more questions, please feel free to ask.

     

    Thanks,

    Weilin Qiao


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.
  • Monday, July 04, 2011 4:17 PM
     
     

    Thank you guys for your help. Using first link (to Express (no R2) tried to repair. In the middle of it message that it cannot verify account name and password. While I was using it with VS 2010 the only option I used was Windows athentication. I don't know what it wants from me and even if I wanted how could I supply that during repair if the only thing I have is a Massage Box (no input options). How I can just uninstall everything. I tried to uninstal Microsoft SQL Server 2008 from Add/Remove program window but I still see it in Add/Remove and in Windows Explorer in the folder "Microsoft SQL Server" I still can see the folder "MSSQL10.SQLEXPRESS". Why it is not removed (though if I try to Uninstall Microsoft SQL Server 2008 from Add/Remove program window again I don't see that instance any more). All I need is R2 edition - I am confused enough as you can see.

    Thank you all very much for your help.


    Vitaly Novikov
  • Wednesday, July 13, 2011 3:58 PM
     
     

    I got the same thing. Through Windows Update (on Win 7 x64 Ultimum), I kept getting error for this update.  After reading the material on the following page, it looks like that the update was for the original releases of the SQL 2008 R2 Express, so I just reinstalled SQL server express 08 using the newest MSI from the links provided in responses above, and it worked.

    http://support.microsoft.com/kb/2494088

    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26304

    http://www.microsoft.com/technet/security/Bulletin/MS11-049.mspx

     

     

     

     

  • Wednesday, August 31, 2011 9:12 AM
     
     

    Hi folks,

     

    I had this same issue for a long time and the only way to solve it was removing the 2008 r2 sp1 and without it i was able to install the pact and after that the sp1 was installed sucessufuly.