locked
WSUS Post Deployment Tasks Configuration Failed RRS feed

  • Question

  • Good Evening, I am system administrator setting up WSUS with SQL Integration in a single server environment with the AD DS, DNS, File and Storage Services, IIS, WDS roles already installed. While I realize this is not best practice, due to limited financial resources it is a necessity. I am installing WSUS as a prequisite for SCCM. I was able to "install" the role but post deployment configuration fails. The log file is as follows:

    2018-01-17 08:33:41  Postinstall started
    2018-01-17 08:33:41  Detected role services: Api, Database, UI, Services
    2018-01-17 08:33:41  Start: LoadSettingsFromXml
    2018-01-17 08:33:41  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
    2018-01-17 08:33:41  Value is true
    2018-01-17 08:33:41  End: GetConfigValue
    2018-01-17 08:33:41  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentDirectory
    2018-01-17 08:33:41  Value is C:\WSUS
    2018-01-17 08:33:41  End: GetConfigValue
    2018-01-17 08:33:41  Content directory is C:\WSUS
    2018-01-17 08:33:41  Start: GetConfigValue with filename=UpdateServices-DB.xml item=InstanceName
    2018-01-17 08:33:41  Value is SERVER\WSUSSQLSERVER
    2018-01-17 08:33:41  End: GetConfigValue
    2018-01-17 08:33:41  SQL instance name is SERVER\WSUSSQLSERVER
    2018-01-17 08:33:41  End: LoadSettingsFromXml
    2018-01-17 08:33:41  Start: Run
    2018-01-17 08:33:41  Fetching WsusAdministratorsSid from registry store
    2018-01-17 08:33:41  Value is S-1-5-21-2425858870-2372749687-2678149568-1183
    2018-01-17 08:33:41  Fetching WsusReportersSid from registry store
    2018-01-17 08:33:41  Value is S-1-5-21-2425858870-2372749687-2678149568-1184
    2018-01-17 08:33:41  Configuring content directory...
    2018-01-17 08:33:41  Configuring groups...
    2018-01-17 08:33:41  Starting group configuration for WSUS Administrators...
    2018-01-17 08:33:41  Found group in regsitry, attempting to use it...
    2018-01-17 08:33:41  Searching for existing group...
    2018-01-17 08:33:41  Existing group was found
    2018-01-17 08:33:41  Writing group to registry...
    2018-01-17 08:33:41  Finished group creation
    2018-01-17 08:33:41  Starting group configuration for WSUS Reporters...
    2018-01-17 08:33:41  Found group in regsitry, attempting to use it...
    2018-01-17 08:33:41  Searching for existing group...
    2018-01-17 08:33:41  Existing group was found
    2018-01-17 08:33:41  Writing group to registry...
    2018-01-17 08:33:41  Finished group creation
    2018-01-17 08:33:41  Configuring permissions...
    2018-01-17 08:33:41  Fetching content directory...
    2018-01-17 08:33:41  Fetching ContentDir from registry store
    2018-01-17 08:33:41  Value is C:\WSUS
    2018-01-17 08:33:41  Fetching group SIDs...
    2018-01-17 08:33:41  Fetching WsusAdministratorsSid from registry store
    2018-01-17 08:33:41  Value is S-1-5-21-2425858870-2372749687-2678149568-1183
    2018-01-17 08:33:41  Fetching WsusReportersSid from registry store
    2018-01-17 08:33:41  Value is S-1-5-21-2425858870-2372749687-2678149568-1184
    2018-01-17 08:33:41  Creating group principals...
    2018-01-17 08:33:42  Granting directory permissions...
    2018-01-17 08:33:42  Granting permissions on content directory...
    2018-01-17 08:33:42  Granting registry permissions...
    2018-01-17 08:33:42  Granting registry permissions...
    2018-01-17 08:33:42  Granting registry permissions...
    2018-01-17 08:33:42  Configuring shares...
    2018-01-17 08:33:42  Configuring network shares...
    2018-01-17 08:33:42  Fetching content directory...
    2018-01-17 08:33:42  Fetching ContentDir from registry store
    2018-01-17 08:33:42  Value is C:\WSUS
    2018-01-17 08:33:42  Fetching WSUS admin SID...
    2018-01-17 08:33:42  Fetching WsusAdministratorsSid from registry store
    2018-01-17 08:33:42  Value is S-1-5-21-2425858870-2372749687-2678149568-1183
    2018-01-17 08:33:42  Content directory is local, creating content shares...
    2018-01-17 08:33:42  Creating share "UpdateServicesPackages" with path "C:\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-01-17 08:33:42  Deleting existing share...
    2018-01-17 08:33:42  Creating share...
    2018-01-17 08:33:42  Share successfully created
    2018-01-17 08:33:42  Creating share "WsusContent" with path "C:\WSUS\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
    2018-01-17 08:33:42  Deleting existing share...
    2018-01-17 08:33:42  Creating share...
    2018-01-17 08:33:42  Share successfully created
    2018-01-17 08:33:42  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-01-17 08:33:42  Deleting existing share...
    2018-01-17 08:33:42  Creating share...
    2018-01-17 08:33:42  Share successfully created
    2018-01-17 08:33:42  Finished creating content shares
    2018-01-17 08:33:42  Stopping service WSUSService
    2018-01-17 08:33:42  Stopping service W3SVC
    2018-01-17 08:33:42  Configuring database...
    2018-01-17 08:33:42  Configuring the database...
    2018-01-17 08:33:42  Establishing DB connection...
    2018-01-17 08:33:43  Checking to see if database exists...
    2018-01-17 08:33:43  Database exists
    2018-01-17 08:33:43  Switching database to single user mode...
    2018-01-17 08:33:43  Loading install type query...
    2018-01-17 08:33:43  DECLARE @currentDBVersion       int
    DECLARE @scriptMajorVersion     int = (14393)
    DECLARE @scriptMinorVersion     int = (0)
    DECLARE @databaseMajorVersion   int 
    DECLARE @databaseMinorVersion   int 
    DECLARE @databaseBuildNumber    nvarchar(10)
    IF NOT EXISTS(SELECT * FROM sys.databases WHERE name='SUSDB')
    BEGIN
        SELECT 1
    END
    ELSE
    BEGIN
        SET @currentDBVersion = (SELECT SchemaVersion FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
        SET @databaseBuildNumber = (SELECT BuildNumber FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
        DECLARE @delimiterPosition INT = CHARINDEX('.', @databaseBuildNumber)
        IF (@delimiterPosition = 0)
        BEGIN
            RAISERROR('Invalid schema version number', 16, 1) with nowait
            return 
        END 
        SET @databaseMajorVersion = SUBSTRING(@databaseBuildNumber, 1, @delimiterPosition - 1)
        SET @databaseMinorVersion = SUBSTRING(@databaseBuildNumber, (@delimiterPosition + 1), (10 - @delimiterPosition))
        IF @currentDBVersion < 926
        BEGIN
            SELECT 3
        END
        ELSE
        BEGIN
            IF (@scriptMajorVersion > @databaseMajorVersion OR
               (@scriptMajorVersion = @databaseMajorVersion AND @scriptMinorVersion > @databaseMinorVersion))
            BEGIN
                SELECT 2
            END
            ELSE IF (@scriptMajorVersion = @databaseMajorVersion AND
                     @scriptMinorVersion = @databaseMinorVersion)
            BEGIN
                SELECT 0
            END
            ELSE
            BEGIN
                SELECT 4
            END
        END
    END

    2018-01-17 08:33:43  Install type is: Reinstall
    2018-01-17 08:33:43  Creating logins...
    2018-01-17 08:33:43  Fetching account info for S-1-5-20
    2018-01-17 08:33:43  Found principal
    2018-01-17 08:33:43  Found account
    2018-01-17 08:33:43  Got binary SID
    2018-01-17 08:33:43  Fetching WsusAdministratorsSid from registry store
    2018-01-17 08:33:43  Value is S-1-5-21-2425858870-2372749687-2678149568-1183
    2018-01-17 08:33:43  Fetching account info for S-1-5-21-2425858870-2372749687-2678149568-1183
    2018-01-17 08:33:43  Fetching account info for S-1-5-21-2425858870-2372749687-2678149568-1183
    2018-01-17 08:33:43  Found principal
    2018-01-17 08:33:43  Found account
    2018-01-17 08:33:43  Got binary SID
    2018-01-17 08:33:43  Setting content location...
    2018-01-17 08:33:43  Fetching ContentDir from registry store
    2018-01-17 08:33:43  Value is C:\WSUS
    2018-01-17 08:33:43  Swtching DB to multi-user mode......
    2018-01-17 08:33:43  Finished setting multi-user mode
    2018-01-17 08:33:43  Writing DB settings to registry...
    2018-01-17 08:33:43  Disposing Connection
    2018-01-17 08:33:43  Clearing Connection Pools
    2018-01-17 08:33:43  Marking PostInstall done for UpdateServices-Database in the registry...
    2018-01-17 08:33:43  Starting service W3SVC
    2018-01-17 08:33:43  Configuring IIS...
    2018-01-17 08:33:43  Start: ConfigureWebsite
    2018-01-17 08:33:44  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)

    Wednesday, January 17, 2018 2:02 PM

Answers

  • On the note for removing WSUS...

    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.

    After you've removed WSUS completely following the instructions above, you can then go ahead and install it again if you so choose.


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

    • Marked as answer by michaelsoher Friday, January 19, 2018 2:56 AM
    Friday, January 19, 2018 2:54 AM

All replies

  • Hi,

    2018-01-17 08:33:43  Configuring IIS...
    2018-01-17 08:33:43  Start: ConfigureWebsite
    2018-01-17 08:33:44  System.Runtime.InteropServices.COMException (0x80070003): The system cannot find the path specified.

     

    It seems that issue is related to IIS configuration part .

    Also , you have mentioned "I am system administrator setting up WSUS with SQL Integration in a single server environment with the AD DS, DNS, File and Storage Services, IIS, WDS roles already installed. " .

    If it is possible , I'd suggest you try to re-install IIS (role) and Windows Process Activation Service (Feature) .

     

    Best Regards,

    Elton


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

    Thursday, January 18, 2018 7:04 AM
  • On the note for removing WSUS...

    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.

    After you've removed WSUS completely following the instructions above, you can then go ahead and install it again if you so choose.


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

    • Marked as answer by michaelsoher Friday, January 19, 2018 2:56 AM
    Friday, January 19, 2018 2:54 AM