locked
Unable to reinstall WSUS - windows server 2016 RRS feed

  • Question

  • Hi colleagues,

    i get this error message everytime i try to launch WSUS 

    Log file is located at C:\Users\Administrator.KENYA\AppData\Local\Temp\tmp1A5C.tmp
    Post install is starting
    Fatal Error: Time out has expired and the operation has not been completed.

    What happened is i deleted some files, some were under drive C - that were filling up space, i tried to change the updates storage place to another drive, but despite trying to remove and add the role WSUS, it doesnt go past the post installation

    the log file is as below

    2018-05-23 18:22:57  Postinstall started
    2018-05-23 18:22:57  Detected role services: Api, UI, WidDatabase, Services
    2018-05-23 18:22:57  Start: LoadSettingsFromParameters
    2018-05-23 18:22:57  Content local is: False
    2018-05-23 18:22:57  SQL instname is: 
    2018-05-23 18:22:57  End: LoadSettingsFromParameters
    2018-05-23 18:22:57  Start: Run
    2018-05-23 18:22:57  Fetching WsusAdministratorsSid from registry store
    2018-05-23 18:22:57  Value is S-1-5-21-2793531805-2532578334-2247915260-2621
    2018-05-23 18:22:57  Fetching WsusReportersSid from registry store
    2018-05-23 18:22:57  Value is S-1-5-21-2793531805-2532578334-2247915260-2620
    2018-05-23 18:23:56  Configuring content directory...
    2018-05-23 18:23:56  Configuring groups...
    2018-05-23 18:23:56  Starting group configuration for WSUS Administrators...
    2018-05-23 18:23:56  Found group in regsitry, attempting to use it...
    2018-05-23 18:23:56  Searching for existing group...
    2018-05-23 18:23:56  Existing group was found
    2018-05-23 18:23:56  Writing group to registry...
    2018-05-23 18:23:56  Finished group creation
    2018-05-23 18:23:56  Starting group configuration for WSUS Reporters...
    2018-05-23 18:23:56  Found group in regsitry, attempting to use it...
    2018-05-23 18:23:56  Searching for existing group...
    2018-05-23 18:23:56  Existing group was found
    2018-05-23 18:23:56  Writing group to registry...
    2018-05-23 18:23:56  Finished group creation
    2018-05-23 18:23:56  Configuring permissions...
    2018-05-23 18:23:56  Fetching content directory...
    2018-05-23 18:23:56  Fetching ContentDir from registry store
    2018-05-23 18:23:56  Value is F:\WSUS
    2018-05-23 18:23:56  Fetching group SIDs...
    2018-05-23 18:23:56  Fetching WsusAdministratorsSid from registry store
    2018-05-23 18:23:56  Value is S-1-5-21-2793531805-2532578334-2247915260-2621
    2018-05-23 18:23:56  Fetching WsusReportersSid from registry store
    2018-05-23 18:23:56  Value is S-1-5-21-2793531805-2532578334-2247915260-2620
    2018-05-23 18:23:56  Creating group principals...
    2018-05-23 18:23:57  Granting directory permissions...
    2018-05-23 18:23:57  Granting permissions on content directory...
    2018-05-23 18:23:59  Granting registry permissions...
    2018-05-23 18:24:00  Granting registry permissions...
    2018-05-23 18:24:00  Granting registry permissions...
    2018-05-23 18:24:00  Configuring shares...
    2018-05-23 18:24:00  Configuring network shares...
    2018-05-23 18:24:00  Fetching content directory...
    2018-05-23 18:24:00  Fetching ContentDir from registry store
    2018-05-23 18:24:00  Value is F:\WSUS
    2018-05-23 18:24:00  Fetching WSUS admin SID...
    2018-05-23 18:24:00  Fetching WsusAdministratorsSid from registry store
    2018-05-23 18:24:00  Value is S-1-5-21-2793531805-2532578334-2247915260-2621
    2018-05-23 18:24:00  Content directory is local, creating content shares...
    2018-05-23 18:24:00  Creating share "UpdateServicesPackages" with path "F:\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."
    2018-05-23 18:24:00  Deleting existing share...
    2018-05-23 18:24:00  Creating share...
    2018-05-23 18:24:00  Share successfully created
    2018-05-23 18:24:00  Creating share "WsusContent" with path "F:\WSUS\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
    2018-05-23 18:24:00  Deleting existing share...
    2018-05-23 18:24:00  Creating share...
    2018-05-23 18:24:00  Share successfully created
    2018-05-23 18:24:00  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."
    2018-05-23 18:24:00  Deleting existing share...
    2018-05-23 18:24:00  Creating share...
    2018-05-23 18:24:00  Share successfully created
    2018-05-23 18:24:00  Finished creating content shares
    2018-05-23 18:24:00  Stopping service WSUSService
    2018-05-23 18:24:00  Stopping service W3SVC
    2018-05-23 18:24:00  Configuring WID database...
    2018-05-23 18:24:00  Configuring the database...
    2018-05-23 18:25:31  System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed.
       at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)
       at Microsoft.UpdateServices.Administration.ConfigureDB.StartService(String serviceName)
       at Microsoft.UpdateServices.Administration.ConfigureDB.Configure()
       at Microsoft.UpdateServices.Administration.ConfigureDB.Run(String instanceName, Action`1 logWriter, Boolean contentLocal)
       at Microsoft.UpdateServices.Administration.PostInstall.Run()
       at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)

    Wednesday, May 23, 2018 3:35 PM

All replies

  • you have to clear the WID database on your machine for the previous instance of WSUS you had.
    Wednesday, May 23, 2018 3:54 PM
  • To remove WSUS completely, you need to:

    1. Remove WSUS Role and Windows Internal Database (WID) Feature.
    2. Remove C:\WSUS or where ever the WSUSContent folder resides.
    3. Remove C:\Windows\WID (specifically: delete the SUSDB.mdf and SUSDB_log.ldf in C:\Windows\WID\Data). If you don't remove the WID role and its files on a reinstall, it will re-attach to the same database.
    4. In IIS, remove the 'WSUS Administration' website and the 'WsusPool' Application Pool if they still exist.
    5. Restart the server and re-add the WSUS And WID Roles. Let it install, and then restart the server again.
    6. MAKE SURE .NET 4.7 IS NOT INSTALLED (it comes as a KB number for your server OS, not an add/remove programs installation.) The WSUS post-installer is not compatible with .NET 4.7 and will always error out. Once WSUS is installed and working, .NET 4.7 can be reapplied and WSUS should still work.

    Now try to do the post-installation configuration.

    If this doesn't work, disjoin the server from the domain, and restart. Try the post-installation steps again. If it works, the issue is a policy on your domain that is causing the issues. You can then rejoin the server to the domain.

    Adam Marshall, MCSE: Security
    http://www.adamj.org
    Microsoft MVP - Windows and Devices for IT

    Thursday, May 24, 2018 10:12 PM