locked
Post-deployment failed in wsus RRS feed

All replies

  • Hi,
      

    Please add the installation log file for the WSUS feature role, which is usually found in the add/remove wizard results screen.
    Or adjust the show hidden folder first, then browse to the following path: "C:\Users\<your_username>\AppData\Local\Temp\" to find the WSUS PostInstall log.
      

    Reply back with the results would be happy to help.
      

    Regards,
    Yic


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

    Wednesday, May 15, 2019 2:15 AM
  • No logs showing on that name fille.

    Please check below error.

    

    Wednesday, May 15, 2019 3:49 AM
  • Hi,

    if it is possible for you, go to c:\users\administrator\AppData\Local\Temp and upload a file that its name is tmp1EDE.tmp

    remember that AppData location is hidden and you must check "show hidden file" option to see the folder and temp file that mentioned above.

    Wednesday, May 15, 2019 4:19 AM
  • Please let me know how to upload temp file in forum.
    Wednesday, May 15, 2019 4:30 AM
  • it is simple. just open that log file that i mentioned above with notepad then select all log and paste it here
    Wednesday, May 15, 2019 4:49 AM
  • We have already done that thing but its showing blank only.

    So kindly give us other option.

    Wednesday, May 15, 2019 4:57 AM
  • can you see other tmp file in that folder? sort them as date and open the last created file to see what is in that file. also check its size of these tmp file
    Wednesday, May 15, 2019 5:04 AM
  • temp file size shows 1kb only.

    

    Wednesday, May 15, 2019 5:13 AM
  • Ok. It must contains information and logs. check to see which one has logs and error code.

    is it a reinstallation of WSUS? do you use WID or SQL?

    Wednesday, May 15, 2019 5:27 AM
  • Hi NNMRAO,
      

    As you can see in the screenshot, this is the log file you need to provide, and post the contents of it.
      


      

    Regards,
    Yic

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

    Wednesday, May 15, 2019 5:32 AM
  • We use WID no error found related to wsus.
    Wednesday, May 15, 2019 5:56 AM
    1. From powershell run 

      Remove-WindowsFeature -Name UpdateServices,UpdateServices-DB,UpdateServices-RSAT,UpdateServices-API,UpdateServices-UI -IncludeManagementTools

    2. Delete registry key if exist hklm\software\microsoft\update services

    3. Clear out WSUS MMC Cache if exist %appdata%\microsoft\mmc

    4. Reboot the Server

    5. Reinstall WSUS

    6. Run postinstall via command line

      cd "c:\program files\update services\tools"
      wsusutil.exe postinstall SQL_INSTANCE_NAME=<SQL SERVER FQDN> CONTENT_DIR=<WSUS DIR>


    Wednesday, May 15, 2019 6:07 AM
  • Hi,

    Now temp logs generated.

    Please check below.

    2019-05-15 11:56:36  Postinstall started
    2019-05-15 11:56:36  Detected role services: Api, UI, WidDatabase, Services
    2019-05-15 11:56:36  Start: LoadSettingsFromXml
    2019-05-15 11:56:36  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
    2019-05-15 11:56:36  Value is true
    2019-05-15 11:56:36  End: GetConfigValue
    2019-05-15 11:56:36  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentDirectory
    2019-05-15 11:56:36  Value is C:\wsus_updates
    2019-05-15 11:56:36  End: GetConfigValue
    2019-05-15 11:56:36  Content directory is C:\wsus_updates
    2019-05-15 11:56:36  Database roleservice is not installed
    2019-05-15 11:56:36  End: LoadSettingsFromXml
    2019-05-15 11:56:36  Start: Run
    2019-05-15 11:56:36  Fetching WsusAdministratorsSid from registry store
    2019-05-15 11:56:36  Value is (null)
    2019-05-15 11:56:36  Configuring content directory...
    2019-05-15 11:56:36  Configuring groups...
    2019-05-15 11:56:36  Starting group configuration for WSUS Administrators...
    2019-05-15 11:56:36  Group does not already exist in the registry
    2019-05-15 11:56:36  Searching for existing group...
    2019-05-15 11:56:36  Existing group was found
    2019-05-15 11:56:36  Writing group to registry...
    2019-05-15 11:56:36  Finished group creation
    2019-05-15 11:56:36  Starting group configuration for WSUS Reporters...
    2019-05-15 11:56:36  Group does not already exist in the registry
    2019-05-15 11:56:36  Searching for existing group...
    2019-05-15 11:56:36  Existing group was found
    2019-05-15 11:56:36  Writing group to registry...
    2019-05-15 11:56:36  Finished group creation
    2019-05-15 11:56:36  Configuring permissions...
    2019-05-15 11:56:36  Fetching content directory...
    2019-05-15 11:56:36  Fetching ContentDir from registry store
    2019-05-15 11:56:36  Value is C:\wsus_updates
    2019-05-15 11:56:36  Fetching group SIDs...
    2019-05-15 11:56:36  Fetching WsusAdministratorsSid from registry store
    2019-05-15 11:56:36  Value is S-1-5-21-1012477879-504156097-2023583330-1002
    2019-05-15 11:56:36  Fetching WsusReportersSid from registry store
    2019-05-15 11:56:36  Value is S-1-5-21-1012477879-504156097-2023583330-1003
    2019-05-15 11:56:36  Creating group principals...
    2019-05-15 11:56:41  Granting directory permissions...
    2019-05-15 11:56:41  Granting permissions on content directory...
    2019-05-15 11:56:41  Granting registry permissions...
    2019-05-15 11:56:41  Granting registry permissions...
    2019-05-15 11:56:41  Granting registry permissions...
    2019-05-15 11:56:41  Configuring shares...
    2019-05-15 11:56:41  Configuring network shares...
    2019-05-15 11:56:41  Fetching content directory...
    2019-05-15 11:56:41  Fetching ContentDir from registry store
    2019-05-15 11:56:41  Value is C:\wsus_updates
    2019-05-15 11:56:41  Fetching WSUS admin SID...
    2019-05-15 11:56:41  Fetching WsusAdministratorsSid from registry store
    2019-05-15 11:56:41  Value is S-1-5-21-1012477879-504156097-2023583330-1002
    2019-05-15 11:56:41  Content directory is local, creating content shares...
    2019-05-15 11:56:41  Creating share "UpdateServicesPackages" with path "C:\wsus_updates\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system."
    2019-05-15 11:56:41  Creating share...
    2019-05-15 11:56:41  Share successfully created
    2019-05-15 11:56:41  Creating share "WsusContent" with path "C:\wsus_updates\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
    2019-05-15 11:56:41  Creating share...
    2019-05-15 11:56:41  Share successfully created
    2019-05-15 11:56:41  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."
    2019-05-15 11:56:42  Creating share...
    2019-05-15 11:56:42  Share successfully created
    2019-05-15 11:56:42  Finished creating content shares
    2019-05-15 11:56:42  Stopping service WSUSService
    2019-05-15 11:56:42  Stopping service W3SVC
    2019-05-15 11:56:44  Configuring WID database...
    2019-05-15 11:56:44  Configuring the database...
    2019-05-15 11:56:44  Establishing DB connection...
    2019-05-15 11:57:44  Re-Establishing Connection to execute Multi User Query ...
    2019-05-15 11:57:44  System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
       at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect(String connectionString)
       at Microsoft.UpdateServices.Administration.ConfigureDB.CreateDBConnection()
       at Microsoft.UpdateServices.Administration.ConfigureDB.TryEnsureDatabaseIsInMultiUserMode()
    ClientConnectionId:00000000-0000-0000-0000-000000000000
    Error Number:2,State:0,Class:20
    2019-05-15 11:57:44  System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling, SqlAuthenticationProviderManager sqlAuthProviderManager)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
       at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
       at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect(String connectionString)
       at Microsoft.UpdateServices.Administration.ConfigureDB.CreateDBConnection()
       at Microsoft.UpdateServices.Administration.ConfigureDB.ConnectToDB()
       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)
    ClientConnectionId:00000000-0000-0000-0000-000000000000
    Error Number:2,State:0,Class:20

    Wednesday, May 15, 2019 6:52 AM
  • 2019-05-15 11:57:44  System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) 

    did you try to post-install via command line or GUI? 

    Wednesday, May 15, 2019 7:08 AM
  • Both way i have tried.
    Wednesday, May 15, 2019 7:11 AM
  • Wednesday, May 15, 2019 7:11 AM
  • 2019-05-15 11:57:44  System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) ---> System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified

    ......

    Please following the steps below to remove and re-install WSUS:
      

    1. Remove WSUS role in server manager.
    2. Delete SUSDB.mdf and SUSDB_log.ldf in C:\Windows\WID\Data.
    3. Install SQL server management studio (Download link), then connect to WID (How to connect to WID), check if SUSDB is still in the WID, if yes, detach it and remove it.
    4. Delete WSUS content folder and WSUS site in IIS Manager;
    5. Then restart the WSUS server and re-install WSUS role.
        

    Also, I noticed that your WSUS Content directory is C:\wsus_updates, make sure this folder was created by WSUS itself.
    Reply back with the results would be happy to help.
      

    Regards,
    Yic


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

    Wednesday, May 15, 2019 7:35 AM
  • There is problem with connecting to the database, make sure WID is installed properly and you can connect to that. to make sure the WID is functional, install SQL management studio as Yic Lv told us. if you couldn't  continue the process, follow the steps again (steps that i told you above and has 6 steps or do Yic Lv steps) but this time post install by GUI only. if you have more question about this process feel free to ask.
    Wednesday, May 15, 2019 9:33 AM
  • I have installed sql express server and sql management studio in server but its not connecting with given artical.
    Wednesday, May 15, 2019 10:19 AM
  • is there any error that stand in front of connecting to WID?
    Wednesday, May 15, 2019 10:22 AM
  • Wednesday, May 15, 2019 10:27 AM
  • Wednesday, May 15, 2019 10:33 AM
  • We have installed wsus server on different system and installed successfully but client not showing on console.

    We have checked all the ports and entry for wsus but its not showing on console.

    kindly suggest for the same. 

    Thursday, May 16, 2019 3:40 AM
  • Hi NNMRAO,
      

    The following two articles describe the troubleshooting steps for such failures, please try to check:
      

    Also, if the issue raised in the current thread has been resolved, please help find the help response to you and mark as answer, and the new question suggests that open a new thread. 
      

    Thank you for your cooperation.
      

    Regards,
    Yic


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

    Thursday, May 16, 2019 5:37 AM
  • Mention issue not resolve we have checking with other resource.
    Thursday, May 16, 2019 7:56 AM
  • Follow my guide.

    https://www.ajtek.ca/wsus/how-to-remove-wsus-completely-and-reinstall-it/

    99.999% of the time the issue is that .NET 4.7 is installed.


    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Monday, May 27, 2019 10:13 PM
  • Also,

    https://www.ajtek.ca/wsus/how-do-i-connect-to-the-windows-internal-database-wid/

    since I noticed you were trying to connect to the WID and were getting errors.


    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Monday, May 27, 2019 10:14 PM