Attempting to install WSUS onto server 2012 Standard, with AD roles, all else Vanilla:

The isntall consistently fails with this error:

2012-09-03 15:48:46  Importing default detectoids succeeded.
2012-09-03 15:48:46  Creating default subscription.
2012-09-03 15:48:46  Instantiating UpdateServer
2012-09-03 15:48:49  CreateDefaultSubscription failed. Exception: System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.
   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.Internal.ApiRemoting.GetServerVersion()
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.GetServerVersion()
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.CreateUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer..ctor(Boolean bypassApiRemoting)
   at Microsoft.UpdateServices.Setup.StartServer.StartServer.CreateDefaultSubscription()
2012-09-03 15:48:49  StartServer encountered errors. Exception=The request failed with HTTP status 503: Service Unavailable.
2012-09-03 15:48:49  Microsoft.UpdateServices.Administration.CommandException: Failed to start and configure the WSUS service
   at Microsoft.UpdateServices.Administration.PostInstall.Run()
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
Fatal Error: Failed to start and configure the WSUS service

The server is a secondary DC with the other DC also being the primary WSUS server (to be decommissioned as is only 2012 Beta)

Regards,

Clarence

TechNet Subscriber Support

If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

• Proposed as answer by Mark e Vandenberk Tuesday, May 21, 2013 12:52 PM

I am having this issue as well. I looked at the IIS Instance and it points to: C:\Program Files\Update Services\WebServices\Root\

When I go there, the folder is empty.

This is on a VM using ESXi 5. Fresh install. 2012 RTM as well.

Found fixed the issue on my machine by:

• Uninstall WSUS
• Delete the SUSDB database from the internal database
• demote the server to a member server
• Re-Install the WSUS feature
• Configure WSUS (as a test)
• Promote the server to a domain controller again.

Hope this helps!

• Proposed as answer by Phil W Friday, September 07, 2012 10:39 AM

Interesting, usually DC promo kills any existing roles due to the increased security introduced at DCPromo. I'll give that a try as this is only a lab environment for me.

No dice - similar error:

2012-09-11 16:26:33  Postinstall started
2012-09-11 16:26:33  Detected role services: Api, UI, WidDatabase, Services
2012-09-11 16:26:33  Start: LoadSettingsFromXml
2012-09-11 16:26:33  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
2012-09-11 16:26:33  Value is true
2012-09-11 16:26:33  End: GetConfigValue
2012-09-11 16:26:33  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentDirectory
2012-09-11 16:26:33  Value is E:\WSUS
2012-09-11 16:26:33  End: GetConfigValue
2012-09-11 16:26:33  Content directory is E:\WSUS
2012-09-11 16:26:33  Database roleservice is not installed
2012-09-11 16:26:33  End: LoadSettingsFromXml
Post install is starting
2012-09-11 16:26:33  Start: Run
2012-09-11 16:26:33  Configuring content directory...
2012-09-11 16:26:33  Configuring groups...
2012-09-11 16:26:33  Starting group configuration for WSUS Administrators...
2012-09-11 16:26:33  Found group in regsitry, attempting to use it...
2012-09-11 16:26:35  Writing group to registry...
2012-09-11 16:26:35  Finished group creation
2012-09-11 16:26:35  Starting group configuration for WSUS Reporters...
2012-09-11 16:26:35  Found group in regsitry, attempting to use it...
2012-09-11 16:26:35  Writing group to registry...
2012-09-11 16:26:35  Finished group creation
2012-09-11 16:26:35  Configuring permissions...
2012-09-11 16:26:35  Fetching content directory...
2012-09-11 16:26:35  Fetching ContentDir from registry store
2012-09-11 16:26:35  Value is E:\WSUS
2012-09-11 16:26:35  Fetching group SIDs...
2012-09-11 16:26:35  Fetching WsusAdministratorsSid from registry store
2012-09-11 16:26:35  Value is S-1-5-21-2969037017-3679756223-2518936209-1000
2012-09-11 16:26:35  Fetching WsusReportersSid from registry store
2012-09-11 16:26:35  Value is S-1-5-21-2969037017-3679756223-2518936209-1001
2012-09-11 16:26:35  Creating group principals...
2012-09-11 16:26:35  Granting directory permissions...
2012-09-11 16:26:35  Granting permissions on content directory...
2012-09-11 16:26:35  Granting registry permissions...
2012-09-11 16:26:35  Granting registry permissions...
2012-09-11 16:26:35  Granting registry permissions...
2012-09-11 16:26:35  Configuring shares...
2012-09-11 16:26:35  Configuring network shares...
2012-09-11 16:26:35  Fetching content directory...
2012-09-11 16:26:35  Fetching ContentDir from registry store
2012-09-11 16:26:35  Value is E:\WSUS
2012-09-11 16:26:35  Fetching WSUS admin SID...
2012-09-11 16:26:35  Fetching WsusAdministratorsSid from registry store
2012-09-11 16:26:35  Value is S-1-5-21-2969037017-3679756223-2518936209-1000
2012-09-11 16:26:35  Content directory is local, creating content shares...
2012-09-11 16:26:35  Creating share "UpdateServicesPackages" with path "E:\WSUS\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system."
2012-09-11 16:26:35  Deleting existing share...
2012-09-11 16:26:35  Creating share...
2012-09-11 16:26:35  Share successfully created
2012-09-11 16:26:35  Creating share "WsusContent" with path "E:\WSUS\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
2012-09-11 16:26:35  Deleting existing share...
2012-09-11 16:26:35  Creating share...
2012-09-11 16:26:35  Share successfully created
2012-09-11 16:26:35  Creating share "WSUSTemp" with path "C:\Program Files\Update Services\LogFiles\WSUSTemp" and description "A network share used by Local Publishing from a Remote WSUS Console Instance."
2012-09-11 16:26:35  Deleting existing share...
2012-09-11 16:26:35  Creating share...
2012-09-11 16:26:35  Share successfully created
2012-09-11 16:26:35  Finished creating content shares
2012-09-11 16:26:35  Configuring WID database...
2012-09-11 16:26:35  Configuring the database...
2012-09-11 16:26:35  Establishing DB connection...
2012-09-11 16:26:35  Checking to see if database exists...
2012-09-11 16:26:35  Database exists
2012-09-11 16:26:35  Switching database to single user mode...
2012-09-11 16:26:38  Loading install type query...
2012-09-11 16:26:38  DECLARE @currentScriptVersion   int
DECLARE @currentDBVersion       int
IF NOT EXISTS(SELECT * FROM sys.databases WHERE name='SUSDB')
BEGIN
    SELECT 1
END
ELSE
BEGIN
    SET @currentScriptVersion = (9200 + 16384)
    SET @currentDBVersion = (SELECT SchemaVersion FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
    IF @currentDBVersion < 926
    BEGIN
        SELECT 3
    END
    ELSE IF @currentDBVersion < @currentScriptVersion
    BEGIN
        SELECT 2
    END
    ELSE IF @currentDBVersion = @currentScriptVersion
    BEGIN
        SELECT 0
    END
    ELSE
    BEGIN
        SELECT 4
    END
END

2012-09-11 16:26:38  Install type is: Reinstall
2012-09-11 16:26:38  Creating logins...
2012-09-11 16:26:38  Fetching account info for S-1-5-20
2012-09-11 16:26:39  Found principal
2012-09-11 16:26:39  Found account
2012-09-11 16:26:39  Got binary SID
2012-09-11 16:26:39  Fetching WsusAdministratorsSid from registry store
2012-09-11 16:26:39  Value is S-1-5-21-2969037017-3679756223-2518936209-1000
2012-09-11 16:26:39  Fetching account info for S-1-5-21-2969037017-3679756223-2518936209-1000
2012-09-11 16:26:39  Found principal
2012-09-11 16:26:39  Found account
2012-09-11 16:26:39  Got binary SID
2012-09-11 16:26:39  Setting content location...
2012-09-11 16:26:39  Fetching ContentDir from registry store
2012-09-11 16:26:39  Value is E:\WSUS
2012-09-11 16:26:39  Swtching DB to multi-user mode......
2012-09-11 16:26:40  Finished setting multi-user mode
2012-09-11 16:26:40  Writing DB settings to registry...
2012-09-11 16:26:40  Marking PostInstall done for UpdateServices-WidDatabase in the registry...
2012-09-11 16:26:40  Configuring IIS...
2012-09-11 16:26:40  Start: ConfigureWebsite
2012-09-11 16:26:40  Configuring website on port 8530
2012-09-11 16:27:09  2012-09-11 16:24:56  Info      IISCustomAction    Performing Setup Action, Command /Install
2012-09-11 16:26:41  Info      IISCustomAction    Performing Setup Action, Command /Install
2012-09-11 16:27:08  Info      IISCustomAction    Command /Install Succeeded

2012-09-11 16:27:09  End: ConfigureWebsite
2012-09-11 16:27:09  Configuring performance counters...
2012-09-11 16:27:09  Configuring Stats.NET perf counter...
2012-09-11 16:27:09  Configuring reporting perf counter...
2012-09-11 16:27:09  Configuring client webservice perf counter...
2012-09-11 16:27:09  Configuring server sync webservice perf counter...
2012-09-11 16:27:09  Configuring API remoting perf counter...
2012-09-11 16:27:09  Bringing services online...
2012-09-11 16:27:09  Checking initialization status...
2012-09-11 16:27:09  Database needs initialization.
2012-09-11 16:27:09  StartServer starting...
2012-09-11 16:27:09  Generating encryption key to write to the registry...
2012-09-11 16:27:09  Generating encryption key to write to the database...
2012-09-11 16:27:10  Generating encryption key succeeded...
2012-09-11 16:27:10  Setting WSUSService to autostart...
2012-09-11 16:27:10  WSUSService is set to autostart.
2012-09-11 16:27:10  Starting WSUSService...
2012-09-11 16:27:10  Failed to start WsusService. Exception: System.InvalidOperationException: Cannot start service WSUSService on computer '.'. ---> System.ComponentModel.Win32Exception: An instance of the service is already running
   --- End of inner exception stack trace ---
   at System.ServiceProcess.ServiceController.Start(String[] args)
   at Microsoft.UpdateServices.Setup.StartServer.StartServer.StartAndConfigureService()
2012-09-11 16:27:10  Importing default detectoids.
2012-09-11 16:27:10  Importing CriticalUpdates.xml...
2012-09-11 16:27:10  Importing Drivers.xml...
2012-09-11 16:27:10  Importing FeaturePacks.xml...
2012-09-11 16:27:10  Importing MicrosoftCorporation.xml...
2012-09-11 16:27:10  Importing SecurityUpdates.xml...
2012-09-11 16:27:10  Importing ServicePacks.xml...
2012-09-11 16:27:10  Importing Tools.xml...
2012-09-11 16:27:10  Importing UpdateRollups.xml...
2012-09-11 16:27:10  Importing Updates.xml...
2012-09-11 16:27:10  Importing Windows.xml...
2012-09-11 16:27:10  Importing Windows2000family.xml...
2012-09-11 16:27:10  Importing WindowsServer2003DatacenterEdition.xml...
2012-09-11 16:27:10  Importing WindowsServer2003Family.xml...
2012-09-11 16:27:10  Importing WindowsXPfamily.xml...
2012-09-11 16:27:10  Importing LocalPublisher.xml...
2012-09-11 16:27:10  Importing LocallyPublishedPackages.xml...
2012-09-11 16:27:10  Importing Applications.xml...
2012-09-11 16:27:10  Importing Exchange.xml...
2012-09-11 16:27:10  Importing Office.xml...
2012-09-11 16:27:10  Importing SQL.xml...
2012-09-11 16:27:10  Importing Exchange2000Server.xml...
2012-09-11 16:27:10  Importing ExchangeServer2003.xml...
2012-09-11 16:27:11  Importing OfficeXP.xml...
2012-09-11 16:27:11  Importing Office2003.xml...
2012-09-11 16:27:11  Importing SQLServer.xml...
2012-09-11 16:27:11  Importing WindowsXP64BitEditionVersion2003.xml...
2012-09-11 16:27:11  Importing DefinitionUpdateSusXml.xml...
2012-09-11 16:27:11  Importing ClientServicingApiDetectoid.xml...
2012-09-11 16:27:11  Importing default detectoids succeeded.
2012-09-11 16:27:11  Creating default subscription.
2012-09-11 16:27:11  Instantiating UpdateServer
2012-09-11 16:27:12  CreateDefaultSubscription failed. Exception: System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.
   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.Internal.ApiRemoting.GetServerVersion()
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.GetServerVersion()
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.CreateUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer..ctor(Boolean bypassApiRemoting)
   at Microsoft.UpdateServices.Setup.StartServer.StartServer.CreateDefaultSubscription()
2012-09-11 16:27:12  StartServer encountered errors. Exception=The request failed with HTTP status 503: Service Unavailable.
2012-09-11 16:27:12  Microsoft.UpdateServices.Administration.CommandException: Failed to start and configure the WSUS service
   at Microsoft.UpdateServices.Administration.PostInstall.Run()
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
Fatal Error: Failed to start and configure the WSUS service

Will blow away and try a fresh build

Thanks to all.I suspect this issue is related to the permission. Anyway,we are not likely to install the WSUS on the DC due to the security issue in the production environment.I hope this issue will be fixed when RTM is officially

Hi,

I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.

Regards,

Clarence

TechNet Subscriber Support

If you are TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.

As the error is Exception: System.Net.WebException: The request failed with HTTP status 503: Service Unavailable., please capture the process monitor, netmon and setup log when reproduce the issue.

Download the process monitor at http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
Download the network monitor at http://www.microsoft.com/en-us/download/details.aspx?id=4865

Use admin account to launch the process monitor.
Start network monitor in CMD windows (launch the CMD by admin account)
Cd C:\Program Files\Microsoft Network Monitor 3
NMCap.exe /network * /capture /file %computername%.chn:100M

Reproduce the issue.
Once failed, capture the screenshot.
Stop netmon by press Ctrl + C.
Stop process monitor by press Ctrl + E
Save All events in process monitor.
Provide process monitor log, netmon log and setup log files via your Skydrive or other online drive we can access.

As this was not production, I blew away the server I did have after my last comment so was not able to record any further errors or details.

FWIW

Built a new one, joined domain as member and installed WSUS - all good

DC Promoed to domain controller - still all good (surprisingly)

• Proposed as answer by Adam Morrison Monday, September 17, 2012 7:01 PM

I solved this issue by opening IIS Manager and deleting the old WSUS web site, then running the Complete WSUS Installation again.

• Proposed as answer by Matt StainlessX Friday, February 15, 2013 3:15 PM

I would, in a small environment, still put WSUS on a DC, along with file, print and DNS/DHCP, unless someone has some good reasons not to (been doing it for years without any issues)

I solved this issue by opening IIS Manager and deleting the old WSUS web site, then running the Complete WSUS Installation again.

I solved this issue by opening IIS Manager and deleting the old WSUS web site, then running the Complete WSUS Installation again.

I solved this issue by opening IIS Manager and deleting the old WSUS web site, then running the Complete WSUS Installation again.

Correct.

This fixed it for me :)

I solved this issue by opening IIS Manager and deleting the old WSUS web site, then running the Complete WSUS Installation again.

Yes thank you... that was our issue too. After clearing out IIS from the stale WSUS 3.0 websites and virtual directories the installation succeeded.

I solved this issue by opening IIS Manager and deleting the old WSUS web site, then running the Complete WSUS Installation again.

Thanks!

Delete the old WSUS web site was the solution for me!

Thanks for this. I was able to fix WSUS http error 503 now.

Steps:

• Uninstall WSUS
• Delete the SUSDB database from the internal database
• Delete the WSUS web site from IIS
• Delete WSUS application pool from IIS
• Reboot
• Re-Install the WSUS feature
• Configure WSUS

Thank you!