none
Windows server update failed(kb2463332)

    Question

  • Every time i try to install windows update "Windows Internal Database Service Pack 4 for x64 Edition (KB2463332)" I get a falure the fail code is 643.

    Event Details

      System

       
    - Provider
          [ Name] Microsoft-Windows-WindowsUpdateClient
          [ Guid] {945a8954-c147-4acd-923f-40c45405a658}
       
      EventID 20
       
      Version 0
       
      Level 2
       
      Task 1
       
      Opcode 13
       
      Keywords 0x8000000000000028
       
    - TimeCreated
          [ SystemTime] 2011-03-03T19:47:36.322Z
       
      EventRecordID 1550761
       
      Correlation
       
    - Execution
          [ ProcessID] 244
          [ ThreadID] 4832
       
      Channel System
       
      Computer EXCHANGE.wct.local
       
    - Security
          [ UserID] S-1-5-18

    - EventData

        errorCode 0x80070643
        updateTitle Windows Internal Database Service Pack 4 for x64 Edition (KB2463332)
        updateGuid {5991F683-DDEC-4038-A601-71B32D8C66DC}
        updateRevisionNumber 100

     

    Thanks in Advance

    Thursday, March 03, 2011 8:10 PM

Answers

  • This worked for me:
    http://support.microsoft.com/kb/925976

    The run down is that the computer either had the internal database installed whilst it was a domain controller (during upgrade to Server 2008?), and was subsequently demoted, or was promoted to DC after the internal database was installed.

    This either removes local groups which are referenced in the internal database setup (a DC has not local groups) or means that the domain group used in setup cannot have local credentials added to it because local groups are available on the demoted server.

    The upshot is you have to delete the registry keys telling the server what those groups are - it should then create them afresh in the appropriate place

    • Proposed as answer by lavee383 Thursday, March 10, 2011 6:43 PM
    • Marked as answer by Tim QuanModerator Friday, March 11, 2011 1:55 AM
    Thursday, March 10, 2011 12:12 PM

All replies

  • Try this Microsoft hotfix.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Thursday, March 03, 2011 8:24 PM
  • I have tried that hotfix already

    Thank you for reply

    Thursday, March 03, 2011 8:58 PM
  • Download and install the System Update Readiness Tool  and check if all is okay or not.



    Download and run the tool, it will say that it's "installing"...it's actually running the readiness scan at this time so you should let the installation run to completion. The KB article says it will appear to hang at 60% completion and I've observed this as well. Just be patient and let it finish. After the "installation" is completed, check if this solve your problem or not.


    If this does not solve your problem, please reset windows update components.



    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Thursday, March 03, 2011 9:14 PM
  • Nope Both suggestions failed. Thank you anyway.

    Any other suggestions?

    Friday, March 04, 2011 4:38 AM
  • I too am having the same issues with KB2463332.  Continuous fail.  Found the following half way thru the log:

    Loaded DLL:
    C:\Users\AdminProfile\AppData\Local\Temp\xmlrw.dll
     Version:
    2.0.3609.0

    Failed to find installation media path due to datastore exception
    in FindSetupFolder()

    GetServiceUserGroup failed for MICROSOFT##SSEE, 5
            Error Code: 0x80070534 (1332)
    Windows Error Text: No mapping between account names and security IDs was done.
      Source File Name: sqlca\sqlcax.cpp
    Compiler Timestamp: Thu Dec  9 14:16:50 2010
         Function Name: SetInstanceProperty
    Source Line Number: 1224

    Error Code: 1332
    MSI (s) (FC!88) [07:41:59:305]: Product: Windows Internal Database -- Error 29528. The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.

    Error 29528. The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.

    <Failure Type='Fatal' Error='1332'>
    <EndFunc Name='LaunchFunction' Return='1332' GetLastError='203'>
    CustomAction SetInstanceProperty.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

     

    checked event viewer and i see

    EventID 10005 MsiInstaller:  Product: Windows Internal Database - - Error 29528.  Setup has encountered an unexpected error while Setting Internal Properties.  The error is: Fatal error during installation.

    EventID 20:  Windows Update Agent:  Installation Failure:  Windows failed to install the following update with error 0x80070643:  Windows Internal Database Service Pack 4 for x64 Edition (KB2463332).

    • Edited by lavee383 Tuesday, March 08, 2011 4:34 PM additional information
    Tuesday, March 08, 2011 4:23 PM
  • I am having this same issue too. Im running a WSUS on this server. Are either of you using WSUS or something else?
    Wednesday, March 09, 2011 6:04 PM
  • No.  The only roles I have installed are:

    AD DS, DHCP, DNS, IIS

    Wednesday, March 09, 2011 6:33 PM
  • This worked for me:
    http://support.microsoft.com/kb/925976

    The run down is that the computer either had the internal database installed whilst it was a domain controller (during upgrade to Server 2008?), and was subsequently demoted, or was promoted to DC after the internal database was installed.

    This either removes local groups which are referenced in the internal database setup (a DC has not local groups) or means that the domain group used in setup cannot have local credentials added to it because local groups are available on the demoted server.

    The upshot is you have to delete the registry keys telling the server what those groups are - it should then create them afresh in the appropriate place

    • Proposed as answer by lavee383 Thursday, March 10, 2011 6:43 PM
    • Marked as answer by Tim QuanModerator Friday, March 11, 2011 1:55 AM
    Thursday, March 10, 2011 12:12 PM
  • Thanks a ton Usolis!!!

    This was exactly my problem...I had installed Internal Database on the server prior to it being promo'd to DC.  I deleted the SIDs for the local groups out of the registry as instructed and retried the install and it worked!

    Thanks again!!!

    Thursday, March 10, 2011 6:45 PM
  • i see that your solution has worked for some people; could u give more details on the registry edit? i would like to try it too, but don't know the exactly registry keys to edit.  thanks

    kkannan7777 (kannan.kamala@gmail.com)

    Friday, March 18, 2011 3:55 PM
  • Great.  This worked for me as well.  My branch server is a WSUS and Domain Controller, so removing the registry keys as noted in the MS KB worked.  I would backup the keys prior to deleting to be on the safe side... as with any manual registry changes.

     

    Thanks!

    Saturday, March 26, 2011 11:48 AM
  • Just had to butt in and say thanks to Usolis, this KB worked perfectly. As usual for Microsoft, I couldn't find it using any sensible search terms of my own and it has resolved an issue on three of my servers! Thanks a lot!!!
    Wednesday, March 30, 2011 7:42 AM
  • Worked like a charm. Cheers.
    Tuesday, September 27, 2011 4:26 PM
  • Perfect a solution with a good description why this happens.

    Thanks


    Marcel Brabetz
    Wednesday, October 19, 2011 12:26 PM
  • Great solution, was exactly the issue described (we promoted our SharePoint server to a DC temporarily when migrating servers, and then demoted it once complete).

    Deleted the registry keys, the windows update re-created them and succeeded.


    Many thanks, Simon Roberts
    Tuesday, November 01, 2011 11:31 AM
  • Worked here as well! Great find!
    Tuesday, November 08, 2011 9:52 PM
  • Great post Usolis, this worked for me... I had installed Internal Database prior to promote it to DC.

    Kind regards

    Wednesday, January 11, 2012 2:14 PM
  • Usolis - URule!!  Thanks for the discovery.  We had done a domain rename, and this turns out to have been one of the few quirks in its outcome.  Deleted the obsolete SID, and the SP installed OK - finally!
    --Generally Confused
    Thursday, January 26, 2012 4:39 PM
  • This solutionworked for me!Thanks for the help

    Justerasethese registry keys, and voila!

    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.<var>X</var>\Setup\SQLGroup
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.<var>X</var>\Setup\AGTGroup
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.<var>X</var>\Setup\FTSGroup
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.<var>X</var>\Setup\ASGroup

    Monday, February 13, 2012 8:29 PM
  • THANK YOU! Usolis.... this finally fixed my problem with the KB2463332.

    ******************************

    This worked for me:
    http://support.microsoft.com/kb/925976

    The run down is that the computer either had the internal database installed whilst it was a domain controller (during upgrade to Server 2008?), and was subsequently demoted, or was promoted to DC after the internal database was installed.

    This either removes local groups which are referenced in the internal database setup (a DC has not local groups) or means that the domain group used in setup cannot have local credentials added to it because local groups are available on the demoted server.

    The upshot is you have to delete the registry keys telling the server what those groups are - it should then create them afresh in the appropriate place


    Tuesday, June 19, 2012 3:14 PM
  • This seems to have fixed it!!!  Thanks!

    Patricia Startz

    Wednesday, June 27, 2012 2:14 PM
  • Usolis, thanks! This one really helped.

    FYI: We did a migration from SBS 2003 to SBS 2011. Maybe during the migration, becoming DC and installing the Internal Database were switched?

    Tuesday, November 06, 2012 2:01 PM