none
WSUS install on Server 2012 Fails

    Question

  • 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)


    asdgfsdf

    Monday, September 03, 2012 3:53 AM

Answers

  • 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)


    Richard Parry

    • Marked as answer by RichardParry Thursday, September 13, 2012 4:03 AM
    Thursday, September 13, 2012 4:03 AM

All replies

  • Hi,

    First,I know that you just want to test the WSUS on server 2012.I haven't tested the WSUS role on the DC. In the produtcion enviroment, i suggest you install on a standalone server without any other great applications(DC,SQL,Exchange) installed.You can try to install on another server to see whether it is ok.

    Also, Server 2012 rc version is available right now. Beta version may have some bug issues.Pls also try to upgrade to see whether it works.

    Regards,

    Clarence

    TechNet Subscriber Support

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


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, September 04, 2012 3:29 AM
    Moderator
  • This issue is still present in the RTM version.  I am also trying to carry out this installation on a Domain Controller due to a lack of hardware.
    Wednesday, September 05, 2012 5:55 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.


    Louis Adam Markham


    • Edited by LouisM1979 Wednesday, September 05, 2012 7:41 PM *Edited to add the server version.*
    Wednesday, September 05, 2012 7:41 PM
  • 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 released.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, September 06, 2012 2:51 AM
    Moderator
  • My environment, WSUS is on its own server, NOT a DC.

    Louis Adam Markham

    Thursday, September 06, 2012 3:31 PM
  • 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
    Friday, September 07, 2012 10:38 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.


    asdgfsdf

    Tuesday, September 11, 2012 3:42 AM
  • 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


    Richard Parry

    • Proposed as answer by WillyStein Tuesday, April 26, 2016 3:28 PM
    • Unproposed as answer by WillyStein Tuesday, April 26, 2016 3:28 PM
    Tuesday, September 11, 2012 4:37 AM
  • 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 released.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


    FWIW, the failing serevr is RTM and 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)

    Richard Parry

    Tuesday, September 11, 2012 9:30 PM
  • 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.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, September 12, 2012 5:38 AM
    Moderator
  • 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.


    Thanks
    Zero

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Wednesday, September 12, 2012 10:20 AM
  • 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)


    Richard Parry

    • Marked as answer by RichardParry Thursday, September 13, 2012 4:03 AM
    Thursday, September 13, 2012 4:03 AM
  • I am also having this problem on a clean install of Server 2012, not a domain controller. I installed WSus, then decided uninstalled it, installed SQL Server 2012, then reinstalled WSus but using SQL server as the database. The error occurred during the post-install setup task. I've uploaded all the logs you've requested, you can download them here: www.qualitech.co.nz/wsuserror.zip (16Mb).
    Saturday, September 15, 2012 8:48 PM
  • I solved this issue by opening IIS Manager and deleting the old WSUS web site, then running the Complete WSUS Installation again.
    Saturday, September 15, 2012 10:15 PM
  • I solved this issue by opening IIS Manager and deleting the old WSUS web site, then running the Complete WSUS Installation again.

    This also fixed our issue on a fresh install of Windows Server Datacenter 2012 VM on top of Windows Server Datacenter 2012 Hyper-V system.  Hope it helps others.  I went into IIS and removed the WSUS website.  After that the post-installation task completed without error. 
    Monday, September 17, 2012 7:00 PM
  • Thanks, I followed your steps and it's working now.!!!

    C

    • Proposed as answer by Cristelo Thursday, November 01, 2012 3:29 AM
    Thursday, November 01, 2012 3:29 AM
  • No, didnt help. Still the Same error. Using Final 2012 Datacenter Server.
    Tuesday, November 06, 2012 4:36 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)
    Today, I would install HYPER-V on the physical box, and built TWO VMs -- one for the DC/DNS, and one for DHCP/WSUS/WDS/F&P.

    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

    Tuesday, November 20, 2012 11:34 PM
    Moderator
  • I solved this issue by opening IIS Manager and deleting the old WSUS web site, then running the Complete WSUS Installation again.
     Thanks, I followed your steps and it's working now.!!!
    Wednesday, February 27, 2013 2:25 PM
  • I solved this issue by opening IIS Manager and deleting the old WSUS web site, then running the Complete WSUS Installation again.

     Thanks! This is the correct answer :)
    Saturday, July 13, 2013 8:13 AM
  • If your using SQL. Login to Studio MGMT and delete the SUSDB. Restart the configuration tool from Server Manager - WSUS

    Patrick

    Monday, July 15, 2013 2:20 PM
  • 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 :)


    Andrew Huddleston | Hillsong Church | Sydney

    Thursday, August 15, 2013 3:42 AM
  • I solved this issue by opening IIS Manager and deleting the old WSUS web site, then running the Complete WSUS Installation again.

    Bingo! Thanks for this, worked as a charm.
    Tuesday, August 20, 2013 4:58 PM
  • Yep....worked for me as well
    Friday, September 13, 2013 6:38 PM
  • 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.

    Wednesday, October 23, 2013 2:39 PM
  • I followed all steps and in my case deployment was still failing. I had enabled "HTTP REDIRECT" on IIS and WSUS was also getting this configuration. As soon as I removed "HTTP REDIRECT" from WSUS website and performed deployment again, it worked right away. I just wanted to let you guys know this also fixed my problem in additions to the very helpful posts. Hope it helps you too.
    Sunday, December 29, 2013 6:18 PM
  • Thanks, it solved my problem too!
    Thursday, January 09, 2014 12:16 AM
  • I solved this issue by opening IIS Manager and deleting the old WSUS web site, then running the Complete WSUS Installation again.

    As I had also this Problem after reinstalling WSUS, deleting the WSUS Administration Website within the IIS Manager solved it.
    Wednesday, May 21, 2014 7:47 AM
  • Thanks!

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

    Friday, October 17, 2014 10:50 PM
  • This finally fixed it for me.  Thanks i was going mental!

    Cyndy

    Friday, October 31, 2014 12:39 AM
  • owowowowowo excellent , i solved too
    Wednesday, November 05, 2014 4:25 PM
  • I had the same problem. I fixed it by opening up IIS manager and editing the WSUS site permissions to allow the current user to have modify access to the site. In this case it may be best to log in as administrator and give access to a secure account when doing this to not allow other accounts to have access to modify the WSUS site.
    Sunday, January 04, 2015 5:35 AM
  • 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!


    ---Pat

    • Proposed as answer by Team Boreal Monday, July 11, 2016 2:30 PM
    Thursday, July 30, 2015 6:53 AM
  • The following worked for me.

    Focussing on this error:

    CreateDefaultSubscription failed. Exception: System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.

    Start IIS. Remove the  WSUS Website.

    Perform another 'Post Install Action via WSUS Wizard' 

    All up and running.

    Tuesday, September 08, 2015 7:41 AM
  • Thanks Ronny Holtmaat

    Worked great for me! Just a note, I installed the WSUS role before adding it to the domain. After joining is when I attempted the post-install jobs.

    After deleting the WSUS website in IIS the post-installation job completed successfully.


    • Edited by Pintail17 Tuesday, November 24, 2015 8:44 PM
    Tuesday, November 24, 2015 8:43 PM
  • First of all as Pat had stated earlier on in the thread he doesn't have WSUS and Domain Services on the same box.

    Secondly even in a lab environment I would never want put WSUS or any other roles on the same machine as one another, especially Active Directory Domain Services.

    Hypothetical: Let's say that you want to knock down Active Directory and rebuild it. He would have to also blow WSUS out of the water just because it exists on that server.

    IMHO opinion 1 role per server is better because if something breaks you aren't forced to reinvent the whole car, you just have to fix that one part.

    Tuesday, December 22, 2015 7:51 PM
  • This solutions worked perfectly for me! Didn't think to remove the WSUS Admin site.
    Tuesday, December 22, 2015 7:52 PM
  • Thanks, thats solved the problem.
    Monday, January 04, 2016 7:47 PM
  • Thanks I followed your step and it's go!!!!!!!!!!!!
    Wednesday, January 13, 2016 10:22 AM
  • I have tried all the suggestions in this thread, but I keep getting an error:

    2016-04-14 13:53:31  Fetching WsusAdministratorsSid from registry store
    2016-04-14 13:53:31  Value is S-1-5-21-163950919-807282812-3427720654-1001
    2016-04-14 13:53:31  Fetching account info for S-1-5-21-163950919-807282812-3427720654-1001
    2016-04-14 13:53:31  Found principal
    2016-04-14 13:53:31  Found account
    2016-04-14 13:53:31  Got binary SID
    2016-04-14 13:53:31  Setting content location...
    2016-04-14 13:53:31  Fetching ContentDir from registry store
    2016-04-14 13:53:31  Value is c:\WSUS
    2016-04-14 13:53:31  Swtching DB to multi-user mode......
    2016-04-14 13:53:32  Finished setting multi-user mode
    2016-04-14 13:53:32  Writing DB settings to registry...
    2016-04-14 13:53:32  Marking PostInstall done for UpdateServices-WidDatabase in the registry...
    2016-04-14 13:53:32  Starting service W3SVC
    2016-04-14 13:53:32  Configuring IIS...
    2016-04-14 13:53:32  Start: ConfigureWebsite
    2016-04-14 13:53:33  System.Runtime.InteropServices.COMException (0x80070003): The system cannot find the path specified.

       at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
       at System.DirectoryServices.DirectoryEntry.Bind()
       at System.DirectoryServices.DirectoryEntry.get_AdsObject()
       at System.DirectoryServices.PropertyValueCollection.PopulateList()
       at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)
       at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)
       at Microsoft.UpdateServices.Administration.UseCustomWebSite..ctor()
       at Microsoft.UpdateServices.Administration.PostInstall.ConfigureWebsite(Int32 portNumber)
       at Microsoft.UpdateServices.Administration.PostInstall.Run()
       at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
    Fatal Error: The system cannot find the path specified.

    The server only has a C drive and the WSUS path is c:\WSUS.

    Any suggestions?


    Gregory N. Brooks Secure Data Inc. gregory.brooks@securedatainc.com

    Thursday, April 14, 2016 7:03 PM
  • a simple answer to this

     change Wsuspool in Application Pools in IIS from .NET 2 to .NET 4 and repeated the post-installation configuration, which worked for me.

    Friday, April 22, 2016 5:46 AM
  • I tried it, but only .NET 4.51 installed. I add .NET 4.0 (no other viable options), but no change. It still will not complete the WSUS post installation tasks.

    Errors generated:

    2016-04-22 13:59:28  Install type is: Reinstall

    2016-04-22 13:59:28  Creating logins...

    2016-04-22 13:59:28  Fetching account info for S-1-5-20

    2016-04-22 13:59:28  Found principal

    2016-04-22 13:59:28  Found account

    2016-04-22 13:59:28  Got binary SID

    2016-04-22 13:59:28  Fetching WsusAdministratorsSid from registry store

    2016-04-22 13:59:28  Value is S-1-5-21-163950919-807282812-3427720654-1001

    2016-04-22 13:59:28  Fetching account info for S-1-5-21-163950919-807282812-3427720654-1001

    2016-04-22 13:59:28  Found principal

    2016-04-22 13:59:28  Found account

    2016-04-22 13:59:28  Got binary SID

    2016-04-22 13:59:28  Setting content location...

    2016-04-22 13:59:28  Fetching ContentDir from registry store

    2016-04-22 13:59:28  Value is F:\WSUS

    2016-04-22 13:59:28  Swtching DB to multi-user mode......

    2016-04-22 13:59:29  Finished setting multi-user mode

    2016-04-22 13:59:29  Writing DB settings to registry...

    2016-04-22 13:59:29  Marking PostInstall done for UpdateServices-WidDatabase in the registry...

    2016-04-22 13:59:29  Starting service W3SVC

    2016-04-22 13:59:29  Configuring IIS...

    2016-04-22 13:59:29  Start: ConfigureWebsite

    2016-04-22 13:59:30  System.Runtime.InteropServices.COMException (0x80070003): The system cannot find the path specified.

     

       at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)

       at System.DirectoryServices.DirectoryEntry.Bind()

       at System.DirectoryServices.DirectoryEntry.get_AdsObject()

       at System.DirectoryServices.PropertyValueCollection.PopulateList()

       at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)

       at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)

       at Microsoft.UpdateServices.Administration.UseCustomWebSite..ctor()

       at Microsoft.UpdateServices.Administration.PostInstall.ConfigureWebsite(Int32 portNumber)

       at Microsoft.UpdateServices.Administration.PostInstall.Run()

       at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)

    Fatal Error: The system cannot find the path specified.

     


    Gregory N. Brooks Intellinet Computing brooks@intellinet-computing.com


    Friday, April 22, 2016 6:59 PM
  • I had a similar run around.

    I then discovered the reason the 503 error came up was IIS was limiting connections to 0 connections. I increased to 2 and all these problems went away. The post install ran perfectly.

    CreateDefaultSubscription failed. Exception: System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.

    Tuesday, April 26, 2016 3:30 PM
  • I have struggled with this for ages too. The procedure to remove the WSUS site from IIS and re run the setup worked for me perfectly. 
    Wednesday, October 19, 2016 2:04 PM