locked
Post the installation failed with error- (0x80004005): No such host is known RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    14-05-12 22:04:29  Creating share "WsusContent" with path "H:\WindowsUpdateServices\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
    2014-05-12 22:04:29  Deleting existing share...
    2014-05-12 22:04:29  Creating share...
    2014-05-12 22:04:29  Share successfully created
    2014-05-12 22:04:29  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."
    2014-05-12 22:04:29  Deleting existing share...
    2014-05-12 22:04:29  Creating share...
    2014-05-12 22:04:29  Share successfully created
    2014-05-12 22:04:29  Finished creating content shares
    2014-05-12 22:04:29  Stopping service WSUSService
    2014-05-12 22:04:29  Stopping service W3SVC
    2014-05-12 22:04:29  Configuring database...
    2014-05-12 22:04:31  System.Net.Sockets.SocketException (0x80004005): No such host is known
       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.PostInstall.Run()
       at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
    Tuesday, May 13, 2014 5:42 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Check your Database Name and SPN in Domain if you are using a domain user account. The issue is that database host cannot be found during post-installation.

    Juke Chou

    TechNet Community Support

    • Marked as answer by Kevin Lan Tuesday, May 13, 2014 6:10 AM
    Tuesday, May 13, 2014 6:01 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Check your Database Name and SPN in Domain if you are using a domain user account. The issue is that database host cannot be found during post-installation.

    Juke Chou

    TechNet Community Support

    • Marked as answer by Kevin Lan Tuesday, May 13, 2014 6:10 AM
    Tuesday, May 13, 2014 6:01 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    yes, juke, use the FQDN fixed this issue
    Tuesday, May 13, 2014 6:11 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    use the FQDN fixed this issue

    The necessity of having to use the FQDN to fix this issue strongly suggests that the DNS environment for this system is not properly configured.

    I would suggest reviewing the domain configuration and DNS Suffix configurations to ensure that the system is capable of resolving names within its own domain (or other domains that may host needed resources).

    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Monday, May 19, 2014 1:30 AM