WSUS Post Installation Failed

Question

Dear All,

Hope all are doing well.

I am configuring a new SCCM primary site, DB server on remote SQL Always on with the instance of the SQL AAG Database.

During WSUS post-installation got the error configuration failed for WSUS. I have verified the WSUS post-installation log and found that System.Net.Sockets.SocketException (0x80004005): No such host is known.

Any suggestion would be appreciated.

in progress 0
Sagar 2021-04-13T13:03:19+05:30 4 Answers 574 views Beginner
0

Answers ( 4 )

  2. Anoop C Nair
    0
    2021-04-13T14:10:22+05:30
    Reply

    I have a similar issue during the video recording

    Can you make sure the exact steps are followed?

    https://www.anoopcnair.com/install-wsus-for-configmgr-software-update-point-role-sup-sccm/

    • Sagar
      0
      2021-04-13T16:51:28+05:30
      Reply

      Yes Sir, Mentioned steps are being followed. However, getting error.
      2021-04-13 14:58:29 System.Net.Sockets.SocketException (0x80004005): No such host is known
      at System.Net.Dns.GetAddrInfo(String name)
      at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
      at System.Net.Dns.GetHostEntry(String hostNameOrAddress)
      at Microsoft.UpdateServices.Internal.SetupInfo.IsServerRemote(String serverName)
      at Microsoft.UpdateServices.Administration.ConfigureDB..ctor(String instanceName, Action`1 logWriter, Nullable`1 contentLocal)
      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)
      Fatal Error: No such host is known

      • Anoop C Nair
        0
        2021-04-13T17:04:02+05:30
        Reply

        Well this “Fatal Error: No such host is known” DNS issue?

        Have you tried to check the DNS resolution with NSLookup?

        nslookup WSUSServer.HTMD
        nslookup SQLServer.HTMD
        nslookup SCCMPrimary.HTMD

        Please don’t forget to change the names with your server names (FQDN)

        • Sagar
          0
          2021-04-16T13:27:26+05:30
          Reply

          Hello Anoop Sir,

          The issue has been fixed. Actually, the DB was configured as SQL always on. We have moved the DB into the single instance and remove the wsus role completely and install it again.

          It was successfully installed. Thanks for your time and support.

Leave an answer

Sorry, you do not have permission to answer to this question .