locked
WSUS 3.0 SP2 - cannot upgrade RRS feed

  • Question

  • I am trying to install WSUS 3.0 SP2 on my 2003 x86 box. I already have WSUS 3.0 SP1 installed and it has been working fine ever since I set it up about a year ago. Now when I try to install the SP2 update, I get an error almost immediately, and it tells me to check the setup log, which reads:

    2009-08-26 14:44:46  Success   MWUSSetup          Validating pre-requisites...
    2009-08-26 14:44:46  Error     MWUSSetup          CSqlConnection::Open: CoCreateInstance returned error (Error 0x800703E6: Invalid access to memory location.)
    2009-08-26 14:44:46  Error     MWUSSetup          CUpgradeDriver::PerformPreSetupActions: Failed to open connection to SQL instance %computername%\MICROSOFT##SSEE (Error 0x800703E6: Invalid access to memory location.)
    2009-08-26 14:44:46  Error     MWUSSetup          CSetupDriver::LaunchSetup: Failed to perform pre-setup actions (Error 0x800703E6: Invalid access to memory location.)
    2009-08-26 14:44:46  Error     MWUSSetup          CProgressManager::EnableCancel: GetDlgItem returning error (Error 0x80070578: Invalid window handle.)
    2009-08-26 14:45:01  Error     MWUSSetup          CWatsonhelper::Init: Failed to load WER library. (Error 0x8007007E: The specified module could not be found.)
    2009-08-26 14:45:01  Error     MWUSSetup          CSetupDriver::ReportFailure: Failed to initalize the CWatsonhelper.  This is expected on pre-Vista machines. (Error 0x80004005: Unspecified error)
    2009-08-26 14:45:01  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x800703E6: Invalid access to memory location.)


    I get this same issue every time I try to run the installer. Also, I tried to uninstall WSUS, without checking off any of the options (log files, db, whatever the third option was...), but that failed as well, and the setup log reads for that:

    2009-08-26 15:24:39  Success   MWUSSetup          Validating pre-requisites...
    2009-08-26 15:25:01  Success   MWUSSetup          Removing Wsus...
    2009-08-26 15:25:02  Success   CustomActions.Dll  Successfully set propery of WSUS admin groups' full names
    2009-08-26 15:25:02  Error     CustomActions.Dll  CSqlConnection::Open: CoCreateInstance returned error (Error 0x800703E6: Invalid access to memory location.)
    2009-08-26 15:25:02  Error     CustomActions.Dll  GetDatabaseLocation: Failed to open connection to SQL instance %computername%\MICROSOFT##SSEE (Error 0x800703E6: Invalid access to memory location.)
    2009-08-26 15:25:02  Error     CustomActions.Dll  SetWyukonInstallDirProperty: Failed to get installed location of SUSDB in WYukon (Error 0x800703E6: Invalid access to memory location.)
    2009-08-26 15:25:02  Error     CustomActions.Dll  SetUnInstallProperties: Failed to set WYUKON install directory (Error 0x800703E6: Invalid access to memory location.)
    2009-08-26 15:25:02  Error     MWUSSetup          RemoveWsus: MWUS Uninstall Failed (Error 0x80070643: Fatal error during installation.)
    2009-08-26 15:25:02  Error     MWUSSetup          Wsus MSI uninstallation failed. (Error 0x80070643: Fatal error during installation.)
    2009-08-26 15:25:02  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
    2009-08-26 15:25:05  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)

    While it would be nice to be able to install this service pack, I feel as if there is a more serious problem underneath that could cause issues if we don't resolve them. I appreciate any and all input.

    Thanks,

    Drew Green

    P.S.: I have tried the following to no avail:

    In SQL Server Configuration Manager, I set the Named Pipes and TCP/IP to enabled.

    I've set the "Log on as" to Built in account -> Local System

    Done "Add New Administrator" using the SQL Server Surface Area Configuration.
    Thursday, August 27, 2009 1:27 PM

Answers

  • > 1. SQL Auth in mixed mode. WSUS in another site was installed (upgrade) with SQL in mixed auth mode and everything was ok.

    Whether it's "OK" or not on another installation is a matter of opinion and circumstance, but doesn't apply to this circumstance in any event.

    WSUS is Not Supported in a database service enabled for Mixed Mode Authentication.

    This is the most likely cause of your inability to successfully apply the upgrade.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Wednesday, September 2, 2009 2:18 PM
  • Last error was fixed with adding NT AUTHORITY\NETWORK SERVICE account to the master database permissions list.
    WSUS SP2 Upgrade success.

    PS Lawrence, thanks for help )
    Regards, Dmitriy Ilyin

    Adding incorrect and unneeded permissions to a database is *never* the correct solution.

    The fact that you did that indicates you have significant (and possibly severe) deficiencies in the security configuration of this server.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Wednesday, September 2, 2009 2:19 PM

All replies

  • Drew.. have you reviewed the Release Notes? Have you confirmed that none of the issues documented in the Release Notes are applicable to your server?

    Making the other changes -- protocol configurations, logon account changes, etc. -- aren't of any value either, and might even be complicating the issue. Certainly making changes without having a specific reason for the change designed to remediate an identified and confirmed defect, generally only complicates the diagnostic process.

    Since you've tried an uninstallation and it failed (which might well have been caused by the changes you made), you're going to have to clean up after that failed uninstallation before anything else has a chance of working.

    Incidentally, does this Windows Server 2003 system hosting WSUS have Service Pack 1 or Service Pack 2 installed?


    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Friday, August 28, 2009 3:04 AM
  • The system is running SP2.  I looked at the release notes, and nothing sticks out.  I changed permissions and the other items only after finding information online that suggested I was having an issue connecting to my DB.

    EDIT:  I only tried the changes after both the upgrade and the uninstallation failed after multiple tries.  The changes I made are not the cause of the original problem, and they are easily changed back (most of which I already have changed back).
    Friday, August 28, 2009 11:37 AM
  • Has the same result...
    ATTENTION!
    WSUS SP2 this is not update. This is standalone installer.
    1. It delete WSUS SP1
    2. It try to install itself in place.

    But in configurations with remote SQL servers all u can get it's uninstalled WSUS (

    WSUSSetup.log
    2009-08-28 17:41:17  Error     MWUSSetup          InstallWsus: MWUS Installation Failed (Error 0x80070643: Fatal error during installation.)
    2009-08-28 17:41:17  Error     MWUSSetup          CUpgradeDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Fatal error during installation.)
    2009-08-28 17:41:17  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
    2009-08-28 17:45:28  Error     MWUSSetup          CWatsonHelper::Init: Failed to load WER library. (Error 0x8007007E: The specified module could not be found.)
    2009-08-28 17:45:28  Error     MWUSSetup          CSetupDriver::ReportFailure: Failed to initalize the CWatsonHelper.  This is expected on pre-Vista machines. (Error 0x80004005: Unspecified error)
    2009-08-28 17:45:28  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)

    WSUSSetupmsi_090828_1737.log
    MSI (s) (E4:6C) [17:40:50:041]: Executing op: ActionStart(Name=ExConfigureDb,Description=Configuring the database,)
    MSI (s) (E4:6C) [17:40:50:041]: Executing op: CustomActionSchedule(Action=ExConfigureDb,ActionType=3074,Source=BinaryData,Target=-S SRVDB1 -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:\DOCUME~1\SUPPOR~4\LOCALS~1\Temp\WSUSCa_090828_1737.log",)
    MSI (s) (E4:6C) [17:40:51:400]: Note: 1: 1722 2: ExConfigureDb 3: C:\WINDOWS\Installer\MSI146.tmp 4: -S SRVDB1 -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:\DOCUME~1\SUPPOR~4\LOCALS~1\Temp\WSUSCa_090828_1737.log" 
    MSI (s) (E4:6C) [17:40:59:150]: 
    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\MSI146.tmp, command: -S SRVDB1 -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:\DOCUME~1\SUPPOR~4\LOCALS~1\Temp\WSUSCa_090828_1737.log" 
    MSI (s) (E4:6C) [17:41:02:900]: User policy value 'DisableRollback' is 0
    MSI (s) (E4:6C) [17:41:02:900]: Machine policy value 'DisableRollback' is 0
    Action ended 17:41:02: InstallFinalize. Return value 3.
    WSUS SP1 work with remote SQL fine. But SP2 ((
    Regards, Dmitriy Ilyin
    Friday, August 28, 2009 2:51 PM
  • WSUSSetupmsi_090828_1737.log
    MSI (s) (E4:6C) [17:40:50:041]: Executing op: ActionStart(Name=ExConfigureDb,Description=Configuring the database,)
    
    MSI (s) (E4:6C) [17:40:50:041]: Executing op: CustomActionSchedule(Action=ExConfigureDb,ActionType=3074,Source=BinaryData,
    Target=-S SRVDB1 -F SUSDB -i "c:\Program Files\Update Services\Database\CreateDatabase.sql
    MSI (s) (E4:6C) [17:40:59:150]: 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
    When you ran the installer did you tell it to use an existing database server, or did you tell it to create a new database?
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Friday, August 28, 2009 5:09 PM
  • I tried creating the internal DB but it always failed for some reason, so I then installed SQL 2005 Express and pointed it to that.   Now, I have tried uninstalling everything (using the Windows installer cleanup tool), creating a new DB, but it always says it cannot connect to the DB (during the installation), even though this is a fresh DB.
    Friday, August 28, 2009 7:09 PM
  • Actually I was asking that question of of Dmitriy because his logs suggest he was trying to create a database on a back-end server that already existed. The CreateDatabase.sql script would not be called if the installer option was set to "Use an existing database".

    As for your scenario Drew, first step is to lose the SQL 2005 Express Edition (Express is not a good choice for a database engine for WSUS because of its resource limitations -- 1 CPU; 1GB RAM; 4GB max database size). In addition, if there are issues with the common components of the SQL2005 application installation, installing a second instance is not likely to result in any new success.

    You didn't mention directly doing so, thus I'm assuming that you did not, but you may find that explicitly removing the Windows Internal Database will be of some help. The commands for doing that are documented in Appendix A of the WSUS Operations Guide.

    If the W.I.D. has not been uninstalled, and is corrupted somehow, that would manifest as a connection failure during the installation. The "Fresh DB" was never an issue, since the database server hasn't even been found yet. The error message logged has a strong indication that there may be an issue with the database service installation:

    Failed to open connection to SQL instance %computername%\MICROSOFT##SSEE (Error 0x800703E6: Invalid access to memory location.)


    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Friday, August 28, 2009 9:27 PM
  • I have a similar issue.

    I have SBS 2003 SP2 Standard Edition and am running WSUS V3.1.6001.65 and am trying to upgrade to WSUS 3.0 SP2.
    The upgrade fails with a message Setup Not Completed and the following reason:

    Windows Server Update Services could not be upgraded. A database backup was created at H:\WSUS\{95CB4758-D807-409E-AF16-7DBBF77BB5E0}. For more information, see the Setup log "c:\temp\1\WSUSSetup.log".

    The log file contains the following:

    2009-08-30 10:08:32  Error     MWUSSetup          RemoveWsus: MWUS Uninstall Failed (Error 0x80070663: This patch package could not be opened.  Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.)
    2009-08-30 10:08:32  Error     MWUSSetup          CUpgradeDriver::PerformSetup: Failed to remove earlier version of WSUS (Error 0x80070663: This patch package could not be opened.  Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.)
    2009-08-30 10:08:32  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070663: This patch package could not be opened.  Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.)
    2009-08-30 10:09:38  Error     MWUSSetup          CWatsonHelper::Init: Failed to load WER library. (Error 0x8007007E: The specified module could not be found.)
    2009-08-30 10:09:38  Error     MWUSSetup          CSetupDriver::ReportFailure: Failed to initalize the CWatsonHelper.  This is expected on pre-Vista machines. (Error 0x80004005: Unspecified error)
    2009-08-30 10:09:38  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070663: This patch package could not be opened.  Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.)

    Any help to resolve this would be appreciated.

    Many thanks

    Steve
    StevieM
    • Proposed as answer by jcoleman789 Monday, December 17, 2012 6:10 PM
    Sunday, August 30, 2009 9:51 AM
  • When you ran the installer did you tell it to use an existing database server, or did you tell it to create a new database?
    Well... I've tried to install SP2 with several options
    1. Run installer without any parametrs. It's suggest to upgrade SP1. But at the "Configuring DB" point rollback install proccess and delete existing WSUS SP1.
    2. Reinstall SP1 again (with local DB), then change regestry to remote DB. Then install with SQLINSTANCE_NAME=SRVDB1 switch. The same result.
    3. Try to install SP2 with local DB and then reconect to existing WSUS SP1 DB. Error when opening console.

    Yes, i used SQLINSTANCE_NAME=SRVDB1 switch, but i didn't add CREATE_DATABASE=0.

    Tomorow i try your suggestion.


    Regards, Dmitriy Ilyin
    Sunday, August 30, 2009 10:35 AM
  • Okay... here's a suggestion... run the installer *Interactively* and just answer the prompts with the correct answers.

    Unless you're intimately familiar with WSUS, using the command line and parameters can be very confusing, and unless you get absolutely the correct set of all parameters needed, you'll end up with a failed installation.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Sunday, August 30, 2009 1:36 PM
  • Ok. I'm here again ).

    Let's play a little.
    Installing WSUS SP2 with remote SQL
    I took a new server W2K3SP2R2EN clean installed. And already have SQL 2008 intalled (on host W2008SP2). I delete old DB SUSDB from SQL.
    My domain rights - Domain Administrator, Enterprise Administrator. SQL Server rights - sysadmin.

    Experement 1.
    Let's try to install like it described in Deployment Guide - Appendix B: Configure Remote SQL
    On third step we must run installer with SQLINSTANCE_NAME=SRVDB1
    I unpacked WSUS30-KB972455-x86.exe and start install with:
    WusSetup.exe SQLINSTANCE_NAME=SRVDB1
    And on install step where the DB place choosing i choose SRVDB1 again. It say that connection success.
    Successfully connected to SQL server instance SRVDB1

    But on installer step:
    Configuring the database
    I get error:
    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.

    Let's take a look at logs:
    WSUSSetup.log
    2009-08-31 09:34:57  Success   MWUSSetup          Validating pre-requisites...
    2009-08-31 09:34:57  Error     MWUSSetup          Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
    2009-08-31 09:36:30  Success   MWUSSetup          No SQL instances found
    2009-08-31 09:36:55  Success   MWUSSetup          Initializing installation details
    2009-08-31 09:36:55  Success   MWUSSetup          Installing ASP.Net
    2009-08-31 09:37:33  Success   MWUSSetup          ASP.Net is installed successfully
    2009-08-31 09:37:33  Success   MWUSSetup          Installing WSUS...
    2009-08-31 09:37:34  Success   CustomActions.Dll  Unable to get INSTALL_LANGUAGE property, calculating it...
    2009-08-31 09:37:35  Success   CustomActions.Dll  Successfully set propery of WSUS admin groups' full names
    2009-08-31 09:37:36  Success   CustomActions.Dll  .Net framework path: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
    2009-08-31 09:37:41  Success   CustomActions.Dll  Creating user group:  with Description: 
    2009-08-31 09:37:41  Success   CustomActions.Dll  Creating  user group
    2009-08-31 09:37:41  Success   CustomActions.Dll   user group already exists
    2009-08-31 09:37:41  Success   CustomActions.Dll  Successfully created  user group
    2009-08-31 09:37:41  Success   CustomActions.Dll  Creating user group:  with Description: 
    2009-08-31 09:37:41  Success   CustomActions.Dll  Creating  user group
    2009-08-31 09:37:41  Success   CustomActions.Dll   user group already exists
    2009-08-31 09:37:41  Success   CustomActions.Dll  Successfully created  user group
    2009-08-31 09:37:41  Success   CustomActions.Dll  Successfully created WSUS user groups
    2009-08-31 09:37:41  Success   CustomActions.Dll  Succesfully set binary SID property
    2009-08-31 09:37:41  Success   CustomActions.Dll  Succesfully set binary SID property
    2009-08-31 09:37:41  Success   CustomActions.Dll  Successfully set binary SID properties
    2009-08-31 10:36:34  Error     MWUSSetup          InstallWsus: MWUS Installation Failed (Error 0x80070643: Fatal error during installation.)
    2009-08-31 10:36:34  Error     MWUSSetup          CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Fatal error during installation.)
    2009-08-31 10:36:34  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
    2009-08-31 10:36:41  Error     MWUSSetup          CWatsonHelper::Init: Failed to load WER library. (Error 0x8007007E: The specified module could not be found.)
    2009-08-31 10:36:41  Error     MWUSSetup          CSetupDriver::ReportFailure: Failed to initalize the CWatsonHelper.  This is expected on pre-Vista machines. (Error 0x80004005: Unspecified error)
    2009-08-31 10:36:41  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)
    

    Lets search value 3 in WSUSSetupmsi_090831_0937.log
    ........................................
    MSI (s) (84:08) [09:38:22:391]: Executing op: ActionStart(Name=ExRollbackCreatedDb,,) MSI (s) (84:08) [09:38:22:391]: Executing op: CustomActionSchedule(Action=ExRollbackCreatedDb,ActionType=3330,Source=BinaryData,Target=-S SRVDB1 -i "C:\Program Files\Update Services\Database\Uninstall.sql" -l "C:\DOCUME~1\SUPPOR~4\LOCALS~1\Temp\WSUSCa_090831_0934.log",) MSI (s) (84:08) [09:38:22:391]: Executing op: ActionStart(Name=ExConfigureDb,Description=Configuring the database,) MSI (s) (84:08) [09:38:22:391]: Executing op: CustomActionSchedule(Action=ExConfigureDb,ActionType=3074,Source=BinaryData,Target=-S SRVDB1 -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:\DOCUME~1\SUPPOR~4\LOCALS~1\Temp\WSUSCa_090831_0934.log",) MSI (s) (84:08) [09:38:23:469]: Note: 1: 1722 2: ExConfigureDb 3: C:\WINDOWS\Installer\MSIA8.tmp 4: -S SRVDB1 -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:\DOCUME~1\SUPPOR~4\LOCALS~1\Temp\WSUSCa_090831_0934.log" MSI (s) (84:08) [10:36:18:936]: 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\MSIA8.tmp, command: -S SRVDB1 -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:\DOCUME~1\SUPPOR~4\LOCALS~1\Temp\WSUSCa_090831_0934.log" MSI (s) (84:08) [10:36:22:576]: User policy value 'DisableRollback' is 0 MSI (s) (84:08) [10:36:22:576]: Machine policy value 'DisableRollback' is 0 Action ended 10:36:22: InstallFinalize. Return value 3.
    .........................................

    And another intresting log WSUSCa_090831_0934.log
    Msg 18456, Level 14, State 1, Server SRVDB1,  Line 65536
    Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
    Msg 18456, Level 14, State 1, Server SRVDB1,  Line 65536
    Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
    Msg 18456, Level 14, State 1, Server SRVDB1,  Line 65536
    Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
    


    Experement 2.
    Let's run installer without ANY parameters.
    Set instance name to SRVDB1
    Successfully connected to SQL server instance SRVDB1

    And again on installer step:
    Configuring the database
    I get error:
    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.

    Log's:
    WSUSSetup.log
    2009-08-31 11:14:30  Success   MWUSSetup          Validating pre-requisites...
    2009-08-31 11:14:31  Error     MWUSSetup          Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
    2009-08-31 11:14:42  Success   MWUSSetup          No SQL instances found
    2009-08-31 11:16:15  Success   MWUSSetup          Initializing installation details
    2009-08-31 11:16:15  Success   MWUSSetup          Installing ASP.Net
    2009-08-31 11:16:58  Success   MWUSSetup          ASP.Net is installed successfully
    2009-08-31 11:16:58  Success   MWUSSetup          Installing WSUS...
    2009-08-31 11:17:00  Success   CustomActions.Dll  Unable to get INSTALL_LANGUAGE property, calculating it...
    2009-08-31 11:17:01  Success   CustomActions.Dll  Successfully set propery of WSUS admin groups' full names
    2009-08-31 11:17:01  Success   CustomActions.Dll  .Net framework path: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
    2009-08-31 11:17:07  Success   CustomActions.Dll  Creating user group:  with Description: 
    2009-08-31 11:17:07  Success   CustomActions.Dll  Creating  user group
    2009-08-31 11:17:07  Success   CustomActions.Dll   user group already exists
    2009-08-31 11:17:07  Success   CustomActions.Dll  Successfully created  user group
    2009-08-31 11:17:07  Success   CustomActions.Dll  Creating user group:  with Description: 
    2009-08-31 11:17:07  Success   CustomActions.Dll  Creating  user group
    2009-08-31 11:17:07  Success   CustomActions.Dll   user group already exists
    2009-08-31 11:17:07  Success   CustomActions.Dll  Successfully created  user group
    2009-08-31 11:17:07  Success   CustomActions.Dll  Successfully created WSUS user groups
    2009-08-31 11:17:07  Success   CustomActions.Dll  Succesfully set binary SID property
    2009-08-31 11:17:07  Success   CustomActions.Dll  Succesfully set binary SID property
    2009-08-31 11:17:07  Success   CustomActions.Dll  Successfully set binary SID properties
    2009-08-31 11:18:57  Error     MWUSSetup          InstallWsus: MWUS Installation Failed (Error 0x80070643: Fatal error during installation.)
    2009-08-31 11:18:57  Error     MWUSSetup          CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Fatal error during installation.)
    2009-08-31 11:18:57  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
    2009-08-31 11:19:30  Error     MWUSSetup          CWatsonHelper::Init: Failed to load WER library. (Error 0x8007007E: The specified module could not be found.)
    2009-08-31 11:19:30  Error     MWUSSetup          CSetupDriver::ReportFailure: Failed to initalize the CWatsonHelper.  This is expected on pre-Vista machines. (Error 0x80004005: Unspecified error)
    2009-08-31 11:19:30  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)
    

    WSUSSetupmsi_090831_1116.log
    MSI (s) (1C:F0) [11:17:49:952]: Executing op: ActionStart(Name=ExConfigureDb,Description=Configuring the database,)
    MSI (s) (1C:F0) [11:17:49:952]: Executing op: CustomActionSchedule(Action=ExConfigureDb,ActionType=3074,Source=BinaryData,Target=-S SRVDB1 -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:\DOCUME~1\SUPPOR~4\LOCALS~1\Temp\WSUSCa_090831_1114.log",)
    MSI (s) (1C:F0) [11:17:52:624]: Note: 1: 1722 2: ExConfigureDb 3: C:\WINDOWS\Installer\MSID1.tmp 4: -S SRVDB1 -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:\DOCUME~1\SUPPOR~4\LOCALS~1\Temp\WSUSCa_090831_1114.log" 
    MSI (s) (1C:F0) [11:18:00:640]: 
    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\MSID1.tmp, command: -S SRVDB1 -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:\DOCUME~1\SUPPOR~4\LOCALS~1\Temp\WSUSCa_090831_1114.log" 
    MSI (s) (1C:F0) [11:18:44:266]: User policy value 'DisableRollback' is 0
    MSI (s) (1C:F0) [11:18:44:266]: Machine policy value 'DisableRollback' is 0
    Action ended 11:18:44: InstallFinalize. Return value 3.
    WSUSCa_090831_1114.log

    Msg 18456, Level 14, State 1, Server SRVDB1,  Line 65536
    Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
    Msg 18456, Level 14, State 1, Server SRVDB1,  Line 65536
    Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
    Msg 18456, Level 14, State 1, Server SRVDB1,  Line 65536
    Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

    Regards, Dmitriy Ilyin
    Monday, August 31, 2009 8:31 AM
  • Well )
    Another log portion.
    The error above was fixed with SetSPN because our SQL Server service started with non system account. After add SPN to MSSQL Service install error changed :)
    This STEP 3 from this page was used to add SPN:
    http://technet.microsoft.com/en-us/library/ms189585(SQL.90).aspx

    Here is new log's:
    WSUSSetup.log

    2009-08-31 17:33:23  Success   MWUSSetup          Validating pre-requisites...
    2009-08-31 17:33:23  Error     MWUSSetup          Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
    2009-08-31 17:33:27  Success   MWUSSetup          No SQL instances found
    2009-08-31 17:33:35  Success   MWUSSetup          Initializing installation details
    2009-08-31 17:33:35  Success   MWUSSetup          Installing ASP.Net
    2009-08-31 17:34:12  Success   MWUSSetup          ASP.Net is installed successfully
    2009-08-31 17:34:12  Success   MWUSSetup          Installing WSUS...
    2009-08-31 17:34:24  Success   CustomActions.Dll  Unable to get INSTALL_LANGUAGE property, calculating it...
    2009-08-31 17:34:24  Success   CustomActions.Dll  Successfully set propery of WSUS admin groups' full names
    2009-08-31 17:34:26  Success   CustomActions.Dll  .Net framework path: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
    2009-08-31 17:34:29  Success   CustomActions.Dll  Creating user group: WSUS Reporters with Description: WSUS Administrators who can only run reports on the Windows Server Update Services server.
    2009-08-31 17:34:29  Success   CustomActions.Dll  Creating WSUS Reporters user group
    2009-08-31 17:34:30  Success   CustomActions.Dll  Successfully created WSUS Reporters user group
    2009-08-31 17:34:30  Success   CustomActions.Dll  Creating user group: WSUS Administrators with Description: WSUS Administrators can administer the Windows Server Update Services server.
    2009-08-31 17:34:30  Success   CustomActions.Dll  Creating WSUS Administrators user group
    2009-08-31 17:34:30  Success   CustomActions.Dll  Successfully created WSUS Administrators user group
    2009-08-31 17:34:30  Success   CustomActions.Dll  Successfully created WSUS user groups
    2009-08-31 17:34:30  Success   CustomActions.Dll  Succesfully set binary SID property
    2009-08-31 17:34:30  Success   CustomActions.Dll  Succesfully set binary SID property
    2009-08-31 17:34:30  Success   CustomActions.Dll  Successfully set binary SID properties
    2009-08-31 17:35:59  Error     MWUSSetup          InstallWsus: MWUS Installation Failed (Error 0x80070643: Fatal error during installation.)
    2009-08-31 17:35:59  Error     MWUSSetup          CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Fatal error during installation.)
    2009-08-31 17:35:59  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
    2009-08-31 17:37:26  Error     MWUSSetup          CWatsonHelper::Init: Failed to load WER library. (Error 0x8007007E: The specified module could not be found.)
    2009-08-31 17:37:26  Error     MWUSSetup          CSetupDriver::ReportFailure: Failed to initalize the CWatsonHelper.  This is expected on pre-Vista machines. (Error 0x80004005: Unspecified error)
    2009-08-31 17:37:26  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation

    WSUSSetupmsi_090831_1734.log
    .........................................
    MSI (s) (FC:84) [17:35:13:951]: Executing op: CustomActionSchedule(Action=ExConfigureDb,ActionType=3074,Source=BinaryData,Target=-S srvdb1 -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:\DOCUME~1\SUPPOR~4\LOCALS~1\Temp\WSUSCa_090831_1733.log",) MSI (s) (FC:84) [17:35:37:029]: Executing op: ActionStart(Name=ExInstallSqlQuery,,) MSI (s) (FC:84) [17:35:37:029]: Executing op: CustomActionSchedule(Action=ExInstallSqlQuery,ActionType=3074,Source=BinaryData,Target=-S srvdb1 -Q " USE SUSDB EXEC dbo.spSetupLogin 0x010500000000000515000000CAB0DE1410B1DDC0B69D2B321F230000, N'AGROCOM\SRVMON$', N'webService' GO UPDATE dbo.tbConfigurationB SET LocalContentCacheLocation = N'c:\WSUS\WsusContent\' GO UPDATE dbo.tbConfigurationA SET HostOnMu = '0' GO UPDATE dbo.tbConfiguration SET Value = N'c:\Program Files\Update Services\LogFiles\WSusTemp' WHERE Name = N'TempContentCache' GO UPDATE dbo.tbConfigurationB SET LogPath = N'c:\Program Files\Update Services\LogFiles\SoftwareDistribution.log' GO INSERT INTO dbo.tbTargetGroup(TargetGroupTypeID, Name, Description, TargetGroupID, OrderValue, IsBuiltin, GroupPriority, ParentGroupId) values (0, N'All Computers', N'', 'A0A08746-4DBE-4a37-9ADF-9E7652C0B421', 0, 1, 0, NULL) GO INSERT INTO dbo MSI (s) (FC:84) [17:35:39:451]: Note: 1: 1722 2: ExInstallSqlQuery 3: C:\WINDOWS\Installer\MSI23.tmp 4: -S srvdb1 -Q " USE SUSDB EXEC dbo.spSetupLogin 0x010500000000000515000000CAB0DE1410B1DDC0B69D2B321F230000, N'AGROCOM\SRVMON$', N'webService' GO UPDATE dbo.tbConfigurationB SET LocalContentCacheLocation = N'c:\WSUS\WsusContent\' GO UPDATE dbo.tbConfigurationA SET HostOnMu = '0' GO UPDATE dbo.tbConfiguration SET Value = N'c:\Program Files\Update Services\LogFiles\WSusTemp' WHERE Name = N'TempContentCache' GO UPDATE dbo.tbConfigurationB SET LogPath = N'c:\Program Files\Update Services\LogFiles\SoftwareDistribution.log' GO INSERT INTO dbo.tbTargetGroup(TargetGroupTypeID, Name, Description, TargetGroupID, OrderValue, IsBuiltin, GroupPriority, ParentGroupId) values (0, N'All Computers', N'', 'A0A08746-4DBE-4a37-9ADF-9E7652C0B421', 0, 1, 0, NULL) GO INSERT INTO dbo.tbTargetGroup(TargetGroupTyp MSI (s) (FC:84) [17:35:43:342]: 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 ExInstallSqlQuery, location: C:\WINDOWS\Installer\MSI23.tmp, command: -S srvdb1 -Q " USE SUSDB EXEC dbo.spSetupLogin 0x010500000000000515000000CAB0DE1410B1DDC0B69D2B321F230000, N'AGROCOM\SRVMON$', N'webService' GO UPDATE dbo.tbConfigurationB SET LocalContentCacheLocation = N'c:\WSUS\WsusContent\' GO UPDATE dbo.tbConfigurationA SET HostOnMu = '0' GO UPDATE dbo.tbConfiguration SET Value = N'c:\Program Files\Update Services\LogFiles\WSusTemp' WHERE Name = N'TempContentCache' GO UPDATE dbo.tbConfigurationB SET LogPath = N'c:\Program Files\Update Services\LogFiles\SoftwareDistribution.log' GO INSERT INTO dbo.tbTargetGroup(TargetGroupTypeID, Name, Description, TargetGroupID, OrderValue, IsBuiltin, GroupPriority, ParentGroupId) values (0, N'All Computers', N'', 'A0A08746-4DBE-4a37-9ADF-9E7652C0B421', 0, 1, 0, NULL) GO INSERT INTO dbo.tbTargetGroup(TargetGroupTypeID, Name, Description, TargetGroupID, OrderValue, IsBuiltin, GroupPriority, ParentGroupId) values (0, N'Unassigned Computers', N'', 'B73CA6ED-5727-47f3-84DE-015E03F6A88A', 0, 1, 1, 'A0A08746-4DBE-4a37-9ADF-9E7652C0B421') GO INSERT INTO dbo.tbTargetGroup(TargetGroupTypeID, Name, Description, TargetGroupID, OrderValue, IsBuiltin, GroupPriority, ParentGroupId) values (1, N'Downstream Servers', N'', 'D374F42A-9BE2-4163-A0FA-3C86A401B7A7', 0, 1, 1, 'A0A08746-4DBE-4a37-9ADF-9E7652C0B421') GO ALTER DATABASE SUSDB SET MULTI_USER WITH NO_WAIT GO" -l "C:\DOCUME~1\SUPPOR~4\LOCALS~1\Temp\WSUSCa_090831_1733.log" MSI (s) (FC:84) [17:35:46:014]: User policy value 'DisableRollback' is 0 MSI (s) (FC:84) [17:35:46:014]: Machine policy value 'DisableRollback' is 0 Action ended 17:35:46: InstallFinalize. Return value 3.
    ......................................

    WSUSCa_090831_1733.log
    ......................................
    Changed database context to 'SUSDB'. Creating PublicViewAccess Database role Creating view PUBLIC_VIEWS.vUpdate Creating view PUBLIC_VIEWS.vCategory Creating view PUBLIC_VIEWS.vClassification Creating view PUBLIC_VIEWS.vUpdateInCategory Creating view PUBLIC_VIEWS.vLanguage Creating view PUBLIC_VIEWS.vUpdateText Creating view PUBLIC_VIEWS.vUpdateAdditionalInfoUrl Creating view PUBLIC_VIEWS.vCategoryText Creating view PUBLIC_VIEWS.vClassificationText Creating view PUBLIC_VIEWS.vDownstreamServer Creating view PUBLIC_VIEWS.vComputerTarget Creating view PUBLIC_VIEWS.vComputerTargetGroup Creating view PUBLIC_VIEWS.vComputerGroupMembership Creating view PUBLIC_VIEWS.vUpdateApproval Creating view PUBLIC_VIEWS.vUpdateInstallationInfoBasic Creating view PUBLIC_VIEWS.vUpdateInstallationInfo Creating view PUBLIC_VIEWS.vUpdateEffectiveApprovalPerComputer Creating view PUBLIC_VIEWS.vSupportedInventory Creating view PUBLIC_VIEWS.vComputerInventory Creating TVF PUBLIC_VIEWS.fnUpdateInstallationStateMap Changed database context to 'SUSDB'. Finished login creation phase. The login name is: AGROCOM\SRVMON$ Finished user creation phase. The user name is: dbo The role principal ID is 5 Adding user to role... Msg 15405, Level 11, State 1, Server srvdb1, Procedure sp_addrolemember, Line 84 Cannot use the special principal 'dbo'. Changed database context to 'master'.


    The last step was:  
    Adding user to role...
    To be continued.... :)
    Regards, Dmitriy Ilyin
    Monday, August 31, 2009 3:06 PM
  • > And already have SQL 2008 intalled (on host W2008SP2).

    Have you *confirmed* that all of the installation and configuration parameters of this pre-existing SQL Server 2008 installation match those needed by WSUS?

    Of immediate consideration comes these two:
    1. WSUS does not support SQL Server instances installed with Mixed Mode Authentication (i.e. SQL Authentication enabled).
    2. WSUS requires that Nested Triggers be ENABLED at the server level, and if the DBA who installed SQL Server 2008 disabled that feature as part of the standard installation and configuration, then you may also have issues -- although more likely during execution, not installation.

    There are others that need to be considered as well.

    Such as... since you're using Windows Server 2008 SP2 -- have you ensured the Windows Firewall is properly configured to permit network connections to the SQL Server service?

    And, as documented in the Deployment Guide -- does the account you are using to install WSUS actually have permissions to access SQL Server =and= is that account configured with the MASTER database as its Default Database?
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Tuesday, September 1, 2009 12:08 AM
  • I have a similar issue.

    I have SBS 2003 SP2 Standard Edition and am running WSUS V3.1.6001.65 and am trying to upgrade to WSUS 3.0 SP2.
    The upgrade fails with a message Setup Not Completed and the following reason:

    Windows Server Update Services could not be upgraded. A database backup was created at H:\WSUS\{95CB4758-D807-409E-AF16-7DBBF77BB5E0}. For more information, see the Setup log "c:\temp\1\WSUSSetup.log".

    The log file contains the following:

    2009-08-30 10:08:32  Error     MWUSSetup          RemoveWsus: MWUS Uninstall Failed (Error 0x80070663: This patch package could not be opened.  Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.)
    2009-08-30 10:08:32  Error     MWUSSetup          CUpgradeDriver::PerformSetup: Failed to remove earlier version of WSUS (Error 0x80070663: This patch package could not be opened.  Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.)
    2009-08-30 10:08:32  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070663: This patch package could not be opened.  Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.)
    2009-08-30 10:09:38  Error     MWUSSetup          CWatsonHelper::Init: Failed to load WER library. (Error 0x8007007E: The specified module could not be found.)
    2009-08-30 10:09:38  Error     MWUSSetup          CSetupDriver::ReportFailure: Failed to initalize the CWatsonHelper.  This is expected on pre-Vista machines. (Error 0x80004005: Unspecified error)
    2009-08-30 10:09:38  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070663: This patch package could not be opened.  Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.)

    Any help to resolve this would be appreciated.

    Many thanks

    Steve
    StevieM

    Steve I'm not convinced you have the same issue -- although it is similar in that you cannot perform the upgrade.

    In this instance it appears that your installer package might be defective. How did you get the WSUS3SP2 installer packae on your SBS2003 machine?

    Where is it being run from?, and Does the account being used to install the update belong to the Domain Admins group?

    Also, how *exactly* are you running the installer?


    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Tuesday, September 1, 2009 12:11 AM
  • 1. SQL Auth in mixed mode. WSUS in another site was installed (upgrade) with SQL in mixed auth mode and everything was ok.
    2. Nested trigers enabled.
    3. Windows firewall is OFF.
    4. My domain account has sysadmin rights (i wrote above). Default DB for this account - master.

    Regards, Dmitriy Ilyin
    Wednesday, September 2, 2009 6:11 AM
  • Last error was fixed with adding NT AUTHORITY\NETWORK SERVICE account to the master database permissions list.
    WSUS SP2 Upgrade success.

    PS Lawrence, thanks for help )
    Regards, Dmitriy Ilyin
    • Proposed as answer by Dmitriy Ilyin Wednesday, September 2, 2009 8:21 AM
    • Unproposed as answer by Lawrence Garvin Wednesday, September 2, 2009 2:19 PM
    Wednesday, September 2, 2009 8:00 AM
  • > 1. SQL Auth in mixed mode. WSUS in another site was installed (upgrade) with SQL in mixed auth mode and everything was ok.

    Whether it's "OK" or not on another installation is a matter of opinion and circumstance, but doesn't apply to this circumstance in any event.

    WSUS is Not Supported in a database service enabled for Mixed Mode Authentication.

    This is the most likely cause of your inability to successfully apply the upgrade.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Wednesday, September 2, 2009 2:18 PM
  • Last error was fixed with adding NT AUTHORITY\NETWORK SERVICE account to the master database permissions list.
    WSUS SP2 Upgrade success.

    PS Lawrence, thanks for help )
    Regards, Dmitriy Ilyin

    Adding incorrect and unneeded permissions to a database is *never* the correct solution.

    The fact that you did that indicates you have significant (and possibly severe) deficiencies in the security configuration of this server.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Wednesday, September 2, 2009 2:19 PM
  • >>WSUS is Not Supported in a database service enabled for Mixed Mode Authentication
    Please, give a link for documentation.

    >>Adding incorrect and unneeded permissions to a database is *never* the correct solution.
    hm... well maybe.... but problem was in installing WSUS. and this was fixed.
    after intall i delete NT AUTHORITY\NETWORK SERVICE.

    Regards, Dmitriy Ilyin
    Thursday, September 3, 2009 8:53 AM
  • C'mon Dmitriy.. you already have links to the documentation! You quoted the Deployment Guide in this very thread on August 31st!


    Pick any one of these links:

    From the Deployment Guide: Choose the Database Used for WSUS 3.0 SP2
    You cannot use SQL authentication with WSUS, which supports only Windows authentication.

    From the Deployment Guide: Appendix B: Configure Remote SQL
    You cannot use SQL authentication. WSUS supports only Windows authentication.

    From the Operations Guide: Migrating from Windows Internal Database to SQL Server
    You cannot use SQL authentication. WSUS supports Windows authentication only.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Thursday, September 3, 2009 2:51 PM
  • Yes, a sow this :)
    But i try to tell that this is not MEAN that MS does not support SQL Server running in mixed auth mode.
    It's take us attention that WSUS can't be authentificated with SQL authentification on SQL server (even those options(keys) STILL present in SP2 in regestry).

    Regards, Dmitriy Ilyin
    Friday, September 4, 2009 6:24 AM

  • Yes, Microsoft supports SQL Server, in general, running in Mixed Mode Authentication,
    but if you attach a WSUS Server to that database, they will not support your *WSUS* installation.

    Microsoft WILL NOT SUPPORT (means if you call Product Support Services for help they'll tell you to REINSTALL the database server)
    the use of Windows Server Update Services connected to a SQL Server database configured to use Mixed Mode Authentication.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Friday, September 4, 2009 2:36 PM
  • make sure your ODBC can access your WSUS database both pipename and TCP dynamic
    you got to know what is the name of the database table
    once your ODBC works, your SP2 upgrade will not have any errors

    Sunday, October 4, 2009 6:17 AM
  • make sure your ODBC can access your WSUS database both pipename and TCP dynamic
    you got to know what is the name of the database table
    once your ODBC works, your SP2 upgrade will not have any errors


    I'm not exactly sure what this statement has to do with this thread.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Sunday, October 4, 2009 2:24 PM
  • Hi All: I just ran into a similar problem on SBS2003 sp2, where I had WSUS 3.0 sp1 installed and running fine for some time. Update Services downloaded and I allowed it to try to install sp2 (in the GUI, I enabled the update, and then later, I let the updater do it's "express install"). 

    The update fails with 

    Windows Server Update Services 3.0 SP2 could not be installed. For more information, see the Setup log "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\WSUSSetup.log".

    The setup log shows the following:

    2009-10-25 07:43:01  Success   MWUSSetup          Validating pre-requisites...
    2009-10-25 07:43:01  Error     MWUSSetup          ExecuteQuery: Failed to execute SQL query USE SUSDB IF EXISTS (select * FROM master..sysdatabases WHERE name= N'SUSDB' AND suser_sname(sid) is null) EXEC dbo.sp_changedbowner N'NHIRSCHGROUP\administrator' (Error 0x80040E14)
    2009-10-25 07:43:01  Error     MWUSSetup          ExecuteQueryGetNoResults: Failed to execute query USE %s IF EXISTS (select * FROM master..sysdatabases WHERE name= N'%s' AND suser_sname(sid) is null) EXEC dbo.sp_changedbowner N'%s' (Error 0x80040E14)
    2009-10-25 07:43:01  Error     MWUSSetup          CUpgradeDriver::PerformPreSetupActions: Failed to reset database owner name for SUSDB to owner NHIRSCHGROUP\administrator (Error 0x80040E14)
    2009-10-25 07:43:01  Error     MWUSSetup          CSetupDriver::LaunchSetup: Failed to perform pre-setup actions (Error 0x80040E14)
    2009-10-25 07:43:01  Error     MWUSSetup          CProgressManager::EnableCancel: GetDlgItem returning error (Error 0x80070578: Invalid window handle.)
    2009-10-25 07:43:18  Error     MWUSSetup          CWatsonHelper::Init: Failed to load WER library. (Error 0x8007007E: The specified module could not be found.)
    2009-10-25 07:43:18  Error     MWUSSetup          CSetupDriver::ReportFailure: Failed to initalize the CWatsonHelper.  This is expected on pre-Vista machines. (Error 0x80004005: Unspecified error)
    2009-10-25 07:43:18  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80040E14)

    I can't uninstall sp2 since it's not installed, and sp1 is not running now...do i need to uninstall 3.0 sp1 and reinstall at this point? Just hoping there may be a simple answer.

    NB: I followed a different thread that led me to manually uninstall sp1. When I ran the sp2 installer again, it alerted me that "Microsoft Report Viewer Redistributable 2008" was not installed. When I installed that component, sp2 seems to be installing OK. I guess I get dope-slapped for letting windows update run by itself :(
    Sunday, October 25, 2009 12:02 PM