none
System.Net.Sockets.SocketException (0x80004005): No such host is known

    Question

  • Post-deployment configuration for WSUS on Server 2012 Standard fails.  When reviewing the log file, I see the following error:

    2014-01-09 10:58:39  Configuring database...
    2014-01-09 10:58:41  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)
    Fatal Error: No such host is known

    This is a dev SCCM 2012 R2 stand alone primary server with SQL Server 2012 Standard installed.  Can anyone offer assistance?  Thanks.

     

    Thursday, January 09, 2014 5:10 PM

Answers

  • I was actually able to resolve the issue. 

    1) I had to open the UpdateServices-Services.xml located in System32\ServerManager\ComponentConfiguration and manually enter a value for the directory "ContentDirectory" property.

    2) Then I had to open the UpdateServices-DB.xml in the same location and manually enter the local server name value for the "InstanceName" property.

    NOTE: I originally entered the SQL instance for the value which by default is MSSQLSERVER for item 2.  This gave me the system socket error.

    I launched the post install process and it completed successfully.  Not sure why the wizard did not automatically configure these files during the installation of the WSUS role.  Oh well. 

    • Marked as answer by Marshal21 Monday, January 13, 2014 3:11 PM
    Monday, January 13, 2014 3:11 PM

All replies

  • Here is the posting of the entire log file:

    2014-01-09 10:58:37  Postinstall started
    2014-01-09 10:58:37  Detected role services: Api, Database, UI, Services
    2014-01-09 10:58:37  Start: LoadSettingsFromXml
    2014-01-09 10:58:37  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
    2014-01-09 10:58:37  Value is true
    2014-01-09 10:58:37  End: GetConfigValue
    2014-01-09 10:58:37  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentDirectory
    2014-01-09 10:58:37  Value is D:\WSUSContent
    2014-01-09 10:58:37  End: GetConfigValue
    2014-01-09 10:58:37  Content directory is D:\WSUSContent
    2014-01-09 10:58:37  Start: GetConfigValue with filename=UpdateServices-DB.xml item=InstanceName
    2014-01-09 10:58:37  Value is MSSQLSERVER
    2014-01-09 10:58:37  End: GetConfigValue
    2014-01-09 10:58:37  SQL instance name is MSSQLSERVER
    2014-01-09 10:58:37  End: LoadSettingsFromXml
    Post install is starting
    2014-01-09 10:58:37  Start: Run
    2014-01-09 10:58:37  Configuring content directory...
    2014-01-09 10:58:37  Configuring groups...
    2014-01-09 10:58:37  Starting group configuration for WSUS Administrators...
    2014-01-09 10:58:37  Found group in regsitry, attempting to use it...
    2014-01-09 10:58:39  Writing group to registry...
    2014-01-09 10:58:39  Finished group creation
    2014-01-09 10:58:39  Starting group configuration for WSUS Reporters...
    2014-01-09 10:58:39  Found group in regsitry, attempting to use it...
    2014-01-09 10:58:39  Writing group to registry...
    2014-01-09 10:58:39  Finished group creation
    2014-01-09 10:58:39  Configuring permissions...
    2014-01-09 10:58:39  Fetching content directory...
    2014-01-09 10:58:39  Fetching ContentDir from registry store
    2014-01-09 10:58:39  Value is D:\WSUSContent
    2014-01-09 10:58:39  Fetching group SIDs...
    2014-01-09 10:58:39  Fetching WsusAdministratorsSid from registry store
    2014-01-09 10:58:39  Value is S-1-5-21-94965983-1388671492-3746375027-1010
    2014-01-09 10:58:39  Fetching WsusReportersSid from registry store
    2014-01-09 10:58:39  Value is S-1-5-21-94965983-1388671492-3746375027-1011
    2014-01-09 10:58:39  Creating group principals...
    2014-01-09 10:58:39  Granting directory permissions...
    2014-01-09 10:58:39  Granting permissions on content directory...
    2014-01-09 10:58:39  Granting registry permissions...
    2014-01-09 10:58:39  Granting registry permissions...
    2014-01-09 10:58:39  Granting registry permissions...
    2014-01-09 10:58:39  Configuring shares...
    2014-01-09 10:58:39  Configuring network shares...
    2014-01-09 10:58:39  Fetching content directory...
    2014-01-09 10:58:39  Fetching ContentDir from registry store
    2014-01-09 10:58:39  Value is D:\WSUSContent
    2014-01-09 10:58:39  Fetching WSUS admin SID...
    2014-01-09 10:58:39  Fetching WsusAdministratorsSid from registry store
    2014-01-09 10:58:39  Value is S-1-5-21-94965983-1388671492-3746375027-1010
    2014-01-09 10:58:39  Content directory is local, creating content shares...
    2014-01-09 10:58:39  Creating share "UpdateServicesPackages" with path "D:\WSUSContent\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system."
    2014-01-09 10:58:39  Deleting existing share...
    2014-01-09 10:58:39  Creating share...
    2014-01-09 10:58:39  Share successfully created
    2014-01-09 10:58:39  Creating share "WsusContent" with path "D:\WSUSContent\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
    2014-01-09 10:58:39  Deleting existing share...
    2014-01-09 10:58:39  Creating share...
    2014-01-09 10:58:39  Share successfully created
    2014-01-09 10:58:39  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-01-09 10:58:39  Deleting existing share...
    2014-01-09 10:58:39  Creating share...
    2014-01-09 10:58:39  Share successfully created
    2014-01-09 10:58:39  Finished creating content shares
    2014-01-09 10:58:39  Configuring database...
    2014-01-09 10:58:41  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)
    Fatal Error: No such host is known

    Thursday, January 09, 2014 5:26 PM
  • "No such host is known" is pretty self-explanatory. This happens right after the Configuring database entry so is probably related to the DB.

    Are you using a local or remote SQL Instance?

    Are you using the default SQL Instance and the default port?


    Jason | http://blog.configmgrftw.com

    Thursday, January 09, 2014 6:17 PM
    Moderator
  • The SQL instance is local and yes I am using the default instance. 
    Thursday, January 09, 2014 6:59 PM
  • I am still stuck on this.  The db is local and the ports as well but I continue to get the no such host is known error.  I've even removed the WSUS role and added it back.  If anyone has an idea of what things to check it would be greatly appreciated. 
    Saturday, January 11, 2014 12:42 AM
  • Hi,

    Did you provide the FQDN of the existed database server when you install WSUS?

    If you use the default instance, please try not to specify the instance name.

    Best Regards,

    Joyce Li


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Monday, January 13, 2014 6:37 AM
    Moderator
  • I was actually able to resolve the issue. 

    1) I had to open the UpdateServices-Services.xml located in System32\ServerManager\ComponentConfiguration and manually enter a value for the directory "ContentDirectory" property.

    2) Then I had to open the UpdateServices-DB.xml in the same location and manually enter the local server name value for the "InstanceName" property.

    NOTE: I originally entered the SQL instance for the value which by default is MSSQLSERVER for item 2.  This gave me the system socket error.

    I launched the post install process and it completed successfully.  Not sure why the wizard did not automatically configure these files during the installation of the WSUS role.  Oh well. 

    • Marked as answer by Marshal21 Monday, January 13, 2014 3:11 PM
    Monday, January 13, 2014 3:11 PM
  • What values did you enter? Can you post examples please.
    Tuesday, March 11, 2014 10:47 PM
  • I wish I could post examples but i'm no longer on site.  But this is the thread that helped me figure it out.  You would need to specify a string type and for value enter the path where your updates will download.  Here's the link with an example:

    http://social.technet.microsoft.com/Forums/en-US/e1003863-e331-46da-8803-e8625bb6324b/server-2012-wsus-postdeployment-configuration-fails-comprehending-the-log-file

    Tuesday, March 25, 2014 8:10 PM