locked
WSUS on Server 2012 R2 fails postinstall RRS feed

  • Question

  • We recently upgraded a Windows Server 2008 R2 VM (vmware) running WSUS 3.2 SP1 to Windows 2012 R2. We made sure to follow the steps on the documentation (https://technet.microsoft.com/en-us/library/hh852345.aspx) and uninstalled WSUS 3.2 prior to upgrading the OS. After upgrading the OS, we then install the WSUS Role Services, which succeeds. The issue occurs when we attempt to run the postinstall tasks; they continually and repeatedly fail with no apparent error messages left behind to determine what caused the failure.

    We are using WID for WSUS (as we had been in 2008R2). We have tried running postinstall via the Server Manager and via PowerShell (Admin mode) with the same results. We have removed the role services, removed WID database, deleted all Update Services and WID folders (rebooting as prompted), all with the same result. At one point we also tried using SQL for the db, but that also failed (unfortunately we did not make note of the failure message for SQL)

    The log file created by the postinstall task appears to just stop when the postinstall fails, without displaying any error message. Below are the contents of our postinstall log file:

    2017-01-30 12:51:55  Postinstall started
    2017-01-30 12:51:55  Detected role services: Api, UI, WidDatabase, Services
    2017-01-30 12:51:55  Start: LoadSettingsFromParameters
    2017-01-30 12:51:55  Content local is: True
    2017-01-30 12:51:55  Content directory is: D:\WSUS
    2017-01-30 12:51:55  SQL instname is:
    2017-01-30 12:51:55  End: LoadSettingsFromParameters
    2017-01-30 12:51:55  Start: Run
    2017-01-30 12:51:55  Fetching WsusAdministratorsSid from registry store
    2017-01-30 12:51:55  Value is S-1-5-21-3391955741-873502902-1140955730-1069
    2017-01-30 12:51:55  Fetching WsusReportersSid from registry store
    2017-01-30 12:51:55  Value is S-1-5-21-3391955741-873502902-1140955730-1070
    2017-01-30 12:51:56  Configuring content directory...
    2017-01-30 12:51:56  Configuring groups...
    2017-01-30 12:51:57  Starting group configuration for WSUS Administrators...
    2017-01-30 12:51:57  Found group in regsitry, attempting to use it...
    2017-01-30 12:51:59  Writing group to registry...
    2017-01-30 12:51:59  Finished group creation
    2017-01-30 12:51:59  Starting group configuration for WSUS Reporters...
    2017-01-30 12:51:59  Found group in regsitry, attempting to use it...
    2017-01-30 12:51:59  Writing group to registry...
    2017-01-30 12:51:59  Finished group creation
    2017-01-30 12:51:59  Configuring permissions...
    2017-01-30 12:51:59  Fetching content directory...
    2017-01-30 12:51:59  Fetching ContentDir from registry store
    2017-01-30 12:51:59  Value is D:\WSUS
    2017-01-30 12:51:59  Fetching group SIDs...
    2017-01-30 12:51:59  Fetching WsusAdministratorsSid from registry store
    2017-01-30 12:51:59  Value is S-1-5-21-3391955741-873502902-1140955730-1069
    2017-01-30 12:51:59  Fetching WsusReportersSid from registry store
    2017-01-30 12:51:59  Value is S-1-5-21-3391955741-873502902-1140955730-1070
    2017-01-30 12:51:59  Creating group principals...
    2017-01-30 12:51:59  Granting directory permissions...
    2017-01-30 12:52:00  Granting permissions on content directory...
    2017-01-30 12:52:10  Granting registry permissions...
    2017-01-30 12:52:10  Granting registry permissions...
    2017-01-30 12:52:10  Granting registry permissions...
    2017-01-30 12:52:10  Configuring shares...
    2017-01-30 12:52:10  Configuring network shares...
    2017-01-30 12:52:10  Fetching content directory...
    2017-01-30 12:52:10  Fetching ContentDir from registry store
    2017-01-30 12:52:10  Value is D:\WSUS
    2017-01-30 12:52:10  Fetching WSUS admin SID...
    2017-01-30 12:52:10  Fetching WsusAdministratorsSid from registry store
    2017-01-30 12:52:10  Value is S-1-5-21-3391955741-873502902-1140955730-1069
    2017-01-30 12:52:10  Content directory is local, creating content shares...
    2017-01-30 12:52:10  Creating share "UpdateServicesPackages" with path "D:\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."
    2017-01-30 12:52:10  Deleting existing share...
    2017-01-30 12:52:10  Creating share...
    2017-01-30 12:52:10  Share successfully created
    2017-01-30 12:52:10  Creating share "WsusContent" with path "D:\WSUS\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
    2017-01-30 12:52:10  Deleting existing share...
    2017-01-30 12:52:10  Creating share...
    2017-01-30 12:52:10  Share successfully created
    2017-01-30 12:52:10  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."
    2017-01-30 12:52:10  Deleting existing share...
    2017-01-30 12:52:10  Creating share...
    2017-01-30 12:52:10  Share successfully created
    2017-01-30 12:52:10  Finished creating content shares
    2017-01-30 12:52:10  Stopping service WSUSService
    2017-01-30 12:52:10  Stopping service W3SVC
    2017-01-30 12:52:13  Configuring WID database...
    2017-01-30 12:52:13  Configuring the database...
    2017-01-30 12:52:14  Establishing DB connection...
    2017-01-30 12:52:14  Checking t

    That is actually where the postinstall log ends; we did not truncate it in any way.

    Any ideas what may be causing this or where we may begin looking for a resolution? We've tried searching Windows Updates but our GP forces all computers to use the WSUS so it won't check with the Microsoft site.

    We are about to revert the server back to our 2008R2 VM snapshot if we can't get this resolved today.

    Many thanks in advance for any recommendations.

    Best,

    Valerie

    Monday, January 30, 2017 6:16 PM

All replies

  • hmmm.

    the next few lines of the log, are supposed to go like this...

    a problem with your WID ? check using SSMS/SSDT/SQLCMD ? (has SUSDB been created/attached)

    2016-05-17 08:16:52  Finished creating content shares
    2016-05-17 08:16:52  Stopping service WSUSService
    2016-05-17 08:16:52  Stopping service W3SVC
    2016-05-17 08:16:55  Configuring database...
    2016-05-17 08:16:55  Configuring the database...
    2016-05-17 08:16:55  Establishing DB connection...
    2016-05-17 08:16:55  Checking to see if database exists...
    2016-05-17 08:16:55  Database exists
    2016-05-17 08:16:55  Switching database to single user mode...
    2016-05-17 08:16:58  Loading install type query...
    2016-05-17 08:16:58  DECLARE @currentDBVersion       int


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Monday, January 30, 2017 8:35 PM
  • Hi Val_C,

    Please remove the WSUS role and all related components and folders.

    Then use SQL server 2012 management studio on the server 2012R2, with \\.\pipe\MICROSOFT##WID\tsql\query to connect to WID. Enable to original SUSDB is deleted or detached.

    https://blogs.msdn.microsoft.com/vedvyas/2014/08/19/following-is-the-steps-to-connect-to-these-windows-internal-database-on-windows-2012-machine-this-to-access-the-wap-configuration-from-the-adfs-configuration-database/

    Then re-install WSUS role and do post-installation again.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, January 31, 2017 4:56 AM
  • Hi,

    Have you got any progress with the issue? Welcome to feedback.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, February 7, 2017 3:08 AM
  • I have same problem. And i cannot connect to WID. Domain admin or local admin. And i cannot delete folder c:\windows\WID after uninstall WSUS role

    


    • Edited by ILKMAN78 Thursday, February 16, 2017 8:11 PM more
    Thursday, February 16, 2017 8:09 PM