wrenchConsider a scenario where you have encountered issues with the installation of KB2720211 (An update for Windows Server Update Services 3.0 Service Pack 2 is available) which forced you to remove and reinstall WSUS. Afterward, when reinstalling 2720211 it fails to install and in the MWusSetup.txt file you find the following:

2012-07-01 15:45:58 Success CustomActions.Dll Successfully set propery of WSUS admin groups' full names
2012-07-01 15:46:14 Error CustomActions.Dll CSqlConnection::Open: Failed to open SQL connection to instance SERVERNAME\MICROSOFT##SSEE (Error 0x80004005: Unspecified error)
2012-07-01 15:46:14 Error CustomActions.Dll GetDatabaseLocation: Failed to open connection to SQL instance %computername%\MICROSOFT##SSEE (Error 0x80004005: Unspecified error)
2012-07-01 15:46:14 Error CustomActions.Dll SetWyukonInstallDirProperty: Failed to get installed location of SUSDB in WYukon (Error 0x80004005: Unspecified error)
2012-07-01 15:46:14 Error CustomActions.Dll SetUnInstallProperties: Failed to set WYUKON install directory (Error 0x80004005: Unspecified error)

Following this, let’s say you decide to change the value of 'wYukonInstalled' to 0 in the registry under 'HKLM\Software\Microsoft\Update Services\Server\Setup' and after doing so KB2720211 installs successfully. However, a short time later the "Update Services' service fails and will not start and you begin seeing events logged like the one below.

To resolve this, on the server use the SQL Server Configuration Manager tool to check the network configuration of the ‘MICROSOFT##SSEE’ Windows internal database. You need to identify specifically which (if any) protocols are enabled.

1. Open the Sql Server Configuration Manager (Start > Programs > Microsoft SQL Server 2008 R2 > Configuration Tools)
2. SQL Server Network Configuration > Protocols for MICROSOFT##SSEE

If you find that the ‘TCP/IP’ protocol and/or the ‘Named Pipes’ protocols are enabled, then next launch the SQL Client Configuration Utility (Cliconfg.exe) on the server and enable the appropriate protocols to match, then apply the changes.

Following this, next use the services MMC (services.msc) to stop ‘Update Services’, restart the ‘Windows Internal Database’ Service and then start ‘Update Services’ once again. Once this is done, attempt to install the KB2720211 update again on the server.

NOTE The steps above are also applicable if the SUSDB is running in a full version of SQL Server as well.

Tyler Franke | Senior Support Escalation Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/