WSUS SP2 installation failed.
- Hi
I am trying to install WSUS SP2 on a server and i am getting the following error when i double click on the install package.
2009-10-22 22:09:13 Success MWUSSetup Validating pre-requisites...
2009-10-22 22:09:30 Error MWUSSetup CSqlConnection::Open: Failed to open SQL connection to instance FS01MILGEIHGE\MICROSOFT##SSEE (Error 0x80004005: Unspecified error)
2009-10-22 22:09:30 Error MWUSSetup CUpgradeDriver::PerformPreSetupActions: Failed to open connection to SQL instance %computername%\MICROSOFT##SSEE (Error 0x80004005: Unspecified error)
2009-10-22 22:09:30 Error MWUSSetup CSetupDriver::LaunchSetup: Failed to perform pre-setup actions (Error 0x80004005: Unspecified error)
2009-10-22 22:09:30 Error MWUSSetup CProgressManager::EnableCancel: GetDlgItem returning error (Error 0x80070578: Invalid window handle.)
2009-10-22 22:09:55 Error MWUSSetup CWatsonHelper::Init: Failed to load WER library. (Error 0x8007007E: The specified module could not be found.)
2009-10-22 22:09:55 Error MWUSSetup CSetupDriver::ReportFailure: Failed to initalize the CWatsonHelper. This is expected on pre-Vista machines. (Error 0x80004005: Unspecified error)
2009-10-22 22:09:55 Error MWUSSetup DoInstall: Wsus setup failed (Error 0x80004005: Unspecified error)
2009-10-22 22:33:23 Success MWUSSetup Validating pre-requisites...
2009-10-22 22:33:40 Error MWUSSetup CSqlConnection::Open: Failed to open SQL connection to instance FS01MILGEIHGE\MICROSOFT##SSEE (Error 0x80004005: Unspecified error)
2009-10-22 22:33:40 Error MWUSSetup CUpgradeDriver::PerformPreSetupActions: Failed to open connection to SQL instance %computername%\MICROSOFT##SSEE (Error 0x80004005: Unspecified error)
2009-10-22 22:33:40 Error MWUSSetup CSetupDriver::LaunchSetup: Failed to perform pre-setup actions (Error 0x80004005: Unspecified error)
2009-10-22 22:33:40 Error MWUSSetup CProgressManager::EnableCancel: GetDlgItem returning error (Error 0x80070578: Invalid window handle.)
Prior to install of WSUS SP2 i have installed all the software required and SQL Express 2008 which i want to use for the DB.
The Servers is running W2k3 SP2 and prior to the install i removed the windows internal db as i do not want to use it.
Has anyone any ideas what the problem is ???
All Replies
My first question is: Why do you want to use SQL Express 2008 instead of the Windows Internal Database.
2009-10-22 22:09:30 Error MWUSSetup CSqlConnection::Open: Failed to open SQL connection to instance FS01MILGEIHGE\MICROSOFT##SSEE (Error 0x80004005: Unspecified error)
My second question is: The installer is trying to connect to an instance of the Windows Internal Database, and you've stated you "removed the windows internal db" -- so WAS? IS? this machine a WSUS server? Is this an UPGRADE, or is this a FRESH install. What's the history on this machine?
Most likely the cause is that you uninstalled the Windows Internal Database (thus blocking any possibility of using a previously existing database), but the installer sees there's supposed to be a WSUS database in the installed Windows Internal Database (the wYukonInstalled registry value in HKLM\Software\Microsoft\Update Services\Server\Setup), but cannot connect to it.
Question: Did you also uninstall the previously existing version of WSUS? If so, then delete the HKLM\Software\Microsoft\Update Services\Server\Setup key and re-try your installation (although I would strongly recommend *against* using SQL Server 2008 Express Edition for WSUS).
Finally... my standard question in such scenarios: Have you reviewed the WSUS Release Notes?
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- Hi,
I'm using SQL Express as it was recommended to me by 1 of my colleagues alot more familar with the application than me.
This machine was a WSUS server running WSUS 3.0, but since we migrated it to a new domain WSUS is no longer working. The primary WSUS server has also been migrated to this domain but is working. I could not get the app working so the next option was to upgrade. I sucessfully upgraded 3 servers, but i have gotten this error on 4 more.
I did try to uninstall WSUS from the server but it did not cleanly uninstall. I will try remove the registry key tonight and see if it works and if so use the Windows Internal Database as suggested.
Thanks for your advise.
Regards
Shane - I went through the steps above unistalling WSUS again from the command prompt and then deleting the registry key suggested above.
I now get the error message below :-( which seems to reference the reg key i deleted.
2009-10-27 19:46:39 Error MWUSSetup ParseCommandLine: Failed to open SOFTWARE\Microsoft\Update Services\Server\Setup registry key (Error 0x80070002: The system cannot find the file specified.)
2009-10-27 19:46:43 Error MWUSSetup DoInstall: ParseCommandLine failed (Error 0x80041453)
2009-10-27 19:46:50 Error MWUSSetup ParseCommandLine: Failed to open SOFTWARE\Microsoft\Update Services\Server\Setup registry key (Error 0x80070002: The system cannot find the file specified.) Hi,
I'm using SQL Express as it was recommended to me by 1 of my colleagues alot more familar with the application than me.
Then may I be so bold and crass as to suggest you should get your WSUS and SQL Server advice from a different resource!? :-)
Frankly, anybody who's recommending SQL Server Express Edition for WSUS can't be that familiar with WSUS.
Nobody that I know of that has any authoritative knowledge has ever recommended SQL Server Express Edition as a substitute for the Windows Internal Database, so I'm not even sure where your colleague got that recommendation, but you might consider challenging it. Yes, it will work; but NO it's not a Good Decision.
Here's the simple facts:
SQL Server Express Edition can:
[a] only use 1GB RAM for buffer cache
[b] only use 1 CORE of your CPU for processing
[c] only have a maximum database size of 4GB
WSUS, on the other hand:
[a] needs more than 1GB RAM for caching (most WSUS databases are at least 2GB-3GB in size). I have a training server supporting 4 machines and only Windows Server 2003 updates, and that database is over 1GB in size!
[b] needs more than 1 CORE of a multi-core or multi-socket system (Particularly if BITS, ASP.NET, and SQLSERVR.EXE are all trying to use the processor(s) concurrently)
[c] may quite likely exceed 4GB of size in a mid-size organization.
Windows Internal Database has NO LIMITS on RAM, CPU, or database size.
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.comThis machine was a WSUS server running WSUS 3.0, but since we migrated it to a new domain WSUS is no longer working. The primary WSUS server has also been migrated to this domain but is working. I could not get the app working so the next option was to upgrade. I sucessfully upgraded 3 servers, but i have gotten this error on 4 more.
I did try to uninstall WSUS from the server but it did not cleanly uninstall. I will try remove the registry key tonight and see if it works and if so use the Windows Internal Database as suggested.
Some basic principles here:
1. You cannot upgrade a broken server. The fundamental principle of upgrading to WSUS3SP2 is that WSUS3SP1 (or WSUS3RTM) is actually *working*. So if the server broke in the process of migrating to a new domain (and I wouldn't be surprised by that in the least), the server cannot be upgraded. You should uninstall WSUS, IIS, WID, and maybe even .NET20 and reinstall them in this order: IIS, .NET20, WSUS/WID.
2. The upgrade process actually consists of two discrete steps:
[a] Uninstall WSUS3SP1 (or WSUS3RTM or WSUS2SP1)
[b] Install WSUS3SP2.
Where the "upgrade" fails (i.e fails on uninstalling the current version, or fails on installing the SP2 version) is critical information as to how to resolve the issue. Either way, the only correct remediation is to reinstall the downlevel version. WSUS3SP2 *cannot* be installed to a pre-existing WSUS3SP1 (or earlier) database.
Thus, as documented in the Release Notes, if the "upgrade" fails you must:
[a] Restore the previous WSUS environment (which can be done by reinstalling on the previous database, or by restoring from backups)
[b] Identify and remediate the cause of the upgrade failure.
[c] Restart the upgrade.
or, strip the machine, give up your data/approvals/configs/etc, and install a fresh WSUS3SP2 on a machine that complies with the installation requirements for WSUS3SP2.
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.comI went through the steps above unistalling WSUS again from the command prompt and then deleting the registry key suggested above.
I now get the error message below :-( which seems to reference the reg key i deleted.
2009-10-27 19:46:39 Error MWUSSetup ParseCommandLine: Failed to open SOFTWARE\Microsoft\Update Services\Server\Setup registry key (Error 0x80070002: The system cannot find the file specified.)
2009-10-27 19:46:43 Error MWUSSetup DoInstall: ParseCommandLine failed (Error 0x80041453)
2009-10-27 19:46:50 Error MWUSSetup ParseCommandLine: Failed to open SOFTWARE\Microsoft\Update Services\Server\Setup registry key (Error 0x80070002: The system cannot find the file specified.)
You need to use the instructions in this WSUS Support Team blog post to uninstall WSUS before attempting a new installation.
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- Thanks for the advice. Heading into Month-end so i will work this next week.
- Hi, I have made some progress. I have managed to get WSUS SP1 installed on the servers and the GUI loads :-) BUT i cannot still get the servers to sync with the Upstream server. Any idea The upstream box is working as i have 2 servers that are able to sync with it. All are in the same domain.
- I presume you're getting some sort of reason for the sync failure recorded in either the Application Event Log or the SoftwareDistribution.log.
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 - Hi,
WebException: The request failed with HTTP status 404: Not Found.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse
response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke
(String methodName, Object[] parameters)
at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper
webServiceHelper)
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager,
Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect) WebException: The request failed with HTTP status 404: Not Found.
I would surmise that you've most likely failed to append port 8530 to the URL configured for the upstream server. Other possibilities are an incorrect URL, or DNS is not properly resolving the hostname of the upstream server.
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
