none
WSUS 3.0 SP2 install fails on Windows 2008 R2 Event ID 11722

    Question

  • I am trying to setup SCCM on a single server.  The server is Windows 2008 R2, with SQL 2008 R2.  Before I setup SCCM, I want to put WSUS 3.0 SP2 on the box, however the install fails with an error on the screen.

    "There is a problem with this windows Installer package.  A program run as part of the setup did not finish as expected. Contact...."

    Event ID 11722 pops up in the application log.  Giving this...

    Product: Windows Server Update Services 3.0 SP2 -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action ExConfigureDb, location: C:\Windows\Installer\MSI8DA3.tmp, command: -S HQ1SVRSMS010 -F SUSDB -i "C:\Program Files\Update Services\Database\CreateDatabase.sql;C:\Program Files\Update Services\Database\mwus_database_schema.sql;C:\Program Files\Update Services\Database\ServerSync.sql;C:\Program Files\Update Services\Database\ClientWebService.sql;C:\Program Files\Update Services\Database\Setup.sql;C:\Program Files\Update Services\Database\Reporting.sql;C:\Program Files\Update Services\Database\ReportingSummarization.sql;C:\Program Files\Update Services\Database\ReportingRollup.sql;C:\Program Files\Update Services\Database\AdminAPI.sql;C:\Program Files\Update Services\Database\popdb.sql;C:\Program Files\Update Services\Database\EvtNamespaceImport.sql;C:\Program Files\Update Services\Database\SqlSettings.sql;C:\Program Files\Update Services\Database\Inventory.sql;C:\Program Files\Update Services\Database\PublicViews.sql" -l "C:\Users\LINDLO~1\AppData\Local\Temp\3\WSUSCa_110121_0902.log"

    Setup Log File....

    2011-01-21 09:10:32  Success   MWUSSetup          Installing WSUS...
    2011-01-21 09:10:32  Success   CustomActions.Dll  Unable to get INSTALL_LANGUAGE property, calculating it...
    2011-01-21 09:10:32  Success   CustomActions.Dll  Successfully set propery of WSUS admin groups' full names
    2011-01-21 09:10:32  Success   CustomActions.Dll  .Net framework path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319
    2011-01-21 09:10:34  Success   CustomActions.Dll  Creating user group: WSUS Reporters with Description: WSUS Administrators who can only run reports on the Windows Server Update Services server.
    2011-01-21 09:10:34  Success   CustomActions.Dll  Creating WSUS Reporters user group
    2011-01-21 09:10:34  Success   CustomActions.Dll  WSUS Reporters user group already exists
    2011-01-21 09:10:34  Success   CustomActions.Dll  Successfully created WSUS Reporters user group
    2011-01-21 09:10:34  Success   CustomActions.Dll  Creating user group: WSUS Administrators with Description: WSUS Administrators can administer the Windows Server Update Services server.
    2011-01-21 09:10:34  Success   CustomActions.Dll  Creating WSUS Administrators user group
    2011-01-21 09:10:34  Success   CustomActions.Dll  WSUS Administrators user group already exists
    2011-01-21 09:10:34  Success   CustomActions.Dll  Successfully created WSUS Administrators user group
    2011-01-21 09:10:34  Success   CustomActions.Dll  Successfully created WSUS user groups
    2011-01-21 09:10:34  Success   CustomActions.Dll  Succesfully set binary SID property
    2011-01-21 09:10:34  Success   CustomActions.Dll  Succesfully set binary SID property
    2011-01-21 09:10:34  Success   CustomActions.Dll  Successfully set binary SID properties
    2011-01-21 09:24:55  Error     MWUSSetup          InstallWsus: MWUS Installation Failed (Error 0x80070643: Fatal error during installation.)
    2011-01-21 09:24:55  Error     MWUSSetup          CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Fatal error during installation.)
    2011-01-21 09:24:55  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
    2011-01-21 09:24:56  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)

    Frustrating to say the least.  This is a brand new server.  Microsoft REALLY needs to update SCCM, the fact that is has to use WSUS for updating clients is a joke.....but I have to use this tool at work.

     

    Any help would be great!

     


    Thanks, -Lindy
    Friday, January 21, 2011 3:26 PM

Answers

  • Never mind, I built a brand new machine just for WSUS, let it use whatever gimped version of SQL it installs these days. 

    Bring on SCCM 2012 with its OWN software update system that DOES NOT require WSUS.

     


    Thanks, -Lindy
    • Marked as answer by cwlindy Friday, January 21, 2011 4:45 PM
    Friday, January 21, 2011 4:33 PM

All replies

  • Never mind, I built a brand new machine just for WSUS, let it use whatever gimped version of SQL it installs these days. 

    Bring on SCCM 2012 with its OWN software update system that DOES NOT require WSUS.

     


    Thanks, -Lindy
    • Marked as answer by cwlindy Friday, January 21, 2011 4:45 PM
    Friday, January 21, 2011 4:33 PM
  • Never mind, I built a brand new machine just for WSUS, let it use whatever gimped version of SQL it installs these days.
    WSUS does not install a gimped version of SQL. The Windows Internal Database is a full-functioning, non-constrained SQL Server database engine sans management and configuration tools.
    Bring on SCCM 2012 with its OWN software update system that DOES NOT require WSUS.

    I've not heard or read anywhere that SCCM 2012 is dropping it's leverage of WSUS as a Software Update Point. Can you point us to a specific Microsoft reference that states that SCCM 2012 will not use WSUS?

    Microsoft REALLY needs to update SCCM, the fact that is has to use WSUS for updating clients is a joke

    Actually the "joke" is that SCCM only partially uses WSUS for updating clients! If it were to fully utilize WSUS, deploying updates via SCCM would be a thousand times easier than it currently is. But let's not devolve this thread into an SCCM vs WSUS flame war. You got your installation working. Incidentally, the logfile contradicts your claim that you were installing to a clean server (it suggests that WSUS had been previously installed on that server), so I suspect the problem was as much an operator issue as it was an SCCM issue.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Saturday, January 22, 2011 1:09 AM
    Moderator
  • Lawrence I so love your attitude.....NOT.  How you became a MVP is beyond me.

    Here is the "systeminfo" results (or enough of them) from the CLI.

    C:\Users\lindloffc>systeminfo

    Host Name:                 HQ1SVRSMS010
    OS Name:                   Microsoft Windows Server 2008 R2 Standard
    OS Version:                6.1.7600 N/A Build 7600
    OS Manufacturer:           Microsoft Corporation
    OS Configuration:          Member Server
    OS Build Type:             Multiprocessor Free
    Registered Owner:          DBG
    Registered Organization:   DBG
    Product ID:                55041-262-0016707-84280
    Original Install Date:     1/18/2011, 1:00:33 AM
    System Boot Time:          1/21/2011, 4:38:23 PM
    System Manufacturer:       VMware, Inc.
    System Model:              VMware Virtual Platform
    System Type:               x64-based PC
    Processor(s):              4 Processor(s) Installed.
                               [01]: Intel64 Family 6 Model 15 Stepping 1 GenuineInt
    el ~2933 Mhz
                               [02]: Intel64 Family 6 Model 15 Stepping 1 GenuineInt
    el ~2933 Mhz
                               [03]: Intel64 Family 6 Model 15 Stepping 1 GenuineInt
    el ~2933 Mhz
                               [04]: Intel64 Family 6 Model 15 Stepping 1 GenuineInt
    el ~2933 Mhz
    BIOS Version:              Phoenix Technologies LTD 6.00, 10/13/2009
    Windows Directory:         C:\Windows
    System Directory:          C:\Windows\system32
    Boot Device:               \Device\HarddiskVolume1
    System Locale:             en-us;English (United States)
    Input Locale:              en-us;English (United States)
    Time Zone:                 (UTC-06:00) Central Time (US & Canada)
    Total Physical Memory:     8,192 MB
    Available Physical Memory: 1,582 MB
    Virtual Memory: Max Size:  10,237 MB
    Virtual Memory: Available: 3,470 MB
    Virtual Memory: In Use:    6,767 MB
    Page File Location(s):     P:\pagefile.sys
    Domain:                    dierbergs.net
    Logon Server:              \\HQ1SVRNET011

    As you can clearly see the server was deployed on the 18th, 3 days ago from a VMware template.  This morning I tried several times to install WSUS, hence the logs files show user groups that were already created if that is what you are getting at.

    WSUS is a great product for SMB's that want good low cost/free solution.  SCCM however should not have to use it.  I dont care if its as simple as taking 90% of the WSUS code and baking it into SCCM.  SUP in SCCM should be option in SCCM that you add and configure completely inside of SCCM.  It would be like having to install Access or Excel to fully utilize SQL Server....and if you install them both on the same box, make sure you do it a specific way or it wont work.  My hope for SCCM is to have its own software patching in the next version.  Also like DPM utilize SQL Server reporting for all reporting vs having a "reporting point" which is configured through SCCM and/or a "reporting services point" configured through both SQL reporting and SCCM.  SCCM is really SMS 2003 with a bunch of stuff bolted on the outside (WSUS).  Call it SMS 2003 R5 if you like.  WSUS = Free, SCCM = everything WSUS is + way more at a cost.

    By the way in the end I got WSUS to work on the same server.  The problem was SQL permissions.  Our DBA's installed SQL on our SCCM server as part of the prereq's and picked the wrong security options, or basically did not follow the technet article I sent them.  I found out after I installed WSUS on another box and tried then to install SCCM.  SCCM gave better error reporting than WSUS did so the problem was fixed pretty quick by the DBA's.  Once the permissions problem was fixed I could also get past the setup error in WSUS.


    Thanks, -Lindy
    Saturday, January 22, 2011 2:04 AM
  • My hope for SCCM is to have its own software patching in the next version. 

    Thank you. I thought this might just be a personal opinion.

    Inasmuch as the next version (SCCM 2012) has been in beta for almost a year now, the architecture and feature list is pretty much 'in stone'.

    Our DBA's installed SQL on our SCCM server as part of the prereq's and picked the wrong security options, or basically did not follow the technet article I sent them.

    99.9% of installation failures observed in this forum since I started posted here were traced to failing to follow the installation instructions.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Monday, January 24, 2011 4:53 PM
    Moderator
  • It would be nice to see an answer here instead of you sniping at each other. I am having the same issue and right now am frustrated with Microsoft. Their products have become less reliable over the last few years. Nonetheless, we need to continue working with them and look to these types of forums for ANSWERS!
    Tuesday, October 09, 2012 12:31 PM
  • It would be nice to see an answer here

    And what is your QUESTION?

    In the case of the original poster, in January 2011 (22 months ago), that problem was trying to install WSUS on a machine with .NET4 installed:

    2011-01-21 09:10:32  Success   CustomActions.Dll  .Net framework path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319

    But before anybody got a chance to respond, the O.P. posted back to "Never Mind", that the server had been reinstalled (and presumably without the .NET4 this time), but more significantly with the correct SQL permissions. Such situations are typically the result of running the installer without understanding the installation requirements of the product, and I pointed that out. (Truly, it was obvious since the correct permissions are documented in the Deployment Guide.)

    Then the O.P went on to make a couple of snarky and grossly inaccurate statements, which it turns out were based on uninformed personal opinions and "hopes" (which were long past the remote possibility of ever coming to reality):

    • That the Windows Internal Database was gimpy.
    • That Configuration Manager 2012 would have a "whole new" update management system not dependent upon WSUS.

    Both of those statements are blatantly false and for the benefit of the readers in this forum, needed to be corrected.

    I am having the same issue

    Exactly which issue are you having:

    • That you're installing WSUS for a Software Update Point in Configuration Manager?
    • That you're trying to install WSUS on a .NET4-enabled machine?
    • That you're trying to install WSUS on a remote SQL Server?
    • Or an entirely different one?

    The conventional practice here is to create a NEW thread, properly describe your specific environment, your specific problem, and then we can have a discussion about your situtaion --- not posting to a 22 month old dead thread and proving no useful information at all, except to engage in your own sniping against Microsoft because some unidentified issue is not being resolved to your liking.

    But at a minimum, provide some FACTS or there's nothing anybody here can do for you.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Saturday, October 13, 2012 4:30 PM
    Moderator