Asked by:
WSUS 2016 -> Fatal Error: No such host is known

Question
-
Hi
I'm getting this while configuring the WSUS
While doing the post installation , I'm getting the below error
Database : instantce name : WSUSDB (remote server )
OS: Windows server 2016
Port 8888
I tried the below command also but no luck
Logs :
2018-04-03 14:10:17 Postinstall started
2018-04-03 14:10:17 Detected role services: Api, Database, UI, Services
2018-04-03 14:10:17 Start: LoadSettingsFromXml
2018-04-03 14:10:17 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
2018-04-03 14:10:17 Value is true
2018-04-03 14:10:17 End: GetConfigValue
2018-04-03 14:10:17 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentDirectory
2018-04-03 14:10:17 Value is d:\WSUSpdates
2018-04-03 14:10:17 End: GetConfigValue
2018-04-03 14:10:17 Content directory is d:\WSUSpdates
2018-04-03 14:10:17 Start: GetConfigValue with filename=UpdateServices-DB.xml item=InstanceName
2018-04-03 14:10:17 Value is SCCMSRV,8888\WSUSDB
2018-04-03 14:10:17 End: GetConfigValue
2018-04-03 14:10:17 SQL instance name is SCCMSRV,8888\WSUSDB
2018-04-03 14:10:17 End: LoadSettingsFromXml
Post install is starting
2018-04-03 14:10:17 Start: Run
2018-04-03 14:10:17 Fetching WsusAdministratorsSid from registry store
2018-04-03 14:10:17 Value is S-1-5-21-645948518-4084393965-3100164076-1006
2018-04-03 14:10:17 Fetching WsusReportersSid from registry store
2018-04-03 14:10:17 Value is S-1-5-21-645948518-4084393965-3100164076-1007
2018-04-03 14:11:17 Configuring content directory...
2018-04-03 14:11:17 Configuring groups...
2018-04-03 14:11:17 Starting group configuration for WSUS Administrators...
2018-04-03 14:11:17 Found group in regsitry, attempting to use it...
2018-04-03 14:11:19 Writing group to registry...
2018-04-03 14:11:19 Finished group creation
2018-04-03 14:11:19 Starting group configuration for WSUS Reporters...
2018-04-03 14:11:19 Found group in regsitry, attempting to use it...
2018-04-03 14:11:19 Writing group to registry...
2018-04-03 14:11:19 Finished group creation
2018-04-03 14:11:19 Configuring permissions...
2018-04-03 14:11:19 Fetching content directory...
2018-04-03 14:11:19 Fetching ContentDir from registry store
2018-04-03 14:11:19 Value is d:\WSUSpdates
2018-04-03 14:11:19 Fetching group SIDs...
2018-04-03 14:11:19 Fetching WsusAdministratorsSid from registry store
2018-04-03 14:11:19 Value is S-1-5-21-645948518-4084393965-3100164076-1006
2018-04-03 14:11:19 Fetching WsusReportersSid from registry store
2018-04-03 14:11:19 Value is S-1-5-21-645948518-4084393965-3100164076-1007
2018-04-03 14:11:19 Creating group principals...
2018-04-03 14:11:19 Granting directory permissions...
2018-04-03 14:11:19 Granting permissions on content directory...
2018-04-03 14:11:19 Granting registry permissions...
2018-04-03 14:11:19 Granting registry permissions...
2018-04-03 14:11:19 Granting registry permissions...
2018-04-03 14:11:19 Configuring shares...
2018-04-03 14:11:19 Configuring network shares...
2018-04-03 14:11:19 Fetching content directory...
2018-04-03 14:11:19 Fetching ContentDir from registry store
2018-04-03 14:11:19 Value is d:\WSUSpdates
2018-04-03 14:11:19 Fetching WSUS admin SID...
2018-04-03 14:11:19 Fetching WsusAdministratorsSid from registry store
2018-04-03 14:11:19 Value is S-1-5-21-645948518-4084393965-3100164076-1006
2018-04-03 14:11:19 Content directory is local, creating content shares...
2018-04-03 14:11:19 Creating share "UpdateServicesPackages" with path "d:\WSUSpdates\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-04-03 14:11:19 Deleting existing share...
2018-04-03 14:11:19 Creating share...
2018-04-03 14:11:19 Share successfully created
2018-04-03 14:11:19 Creating share "WsusContent" with path "d:\WSUSpdates\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
2018-04-03 14:11:19 Deleting existing share...
2018-04-03 14:11:19 Creating share...
2018-04-03 14:11:19 Share successfully created
2018-04-03 14:11:19 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-04-03 14:11:19 Deleting existing share...
2018-04-03 14:11:19 Creating share...
2018-04-03 14:11:19 Share successfully created
2018-04-03 14:11:19 Finished creating content shares
2018-04-03 14:11:19 Stopping service WSUSService
2018-04-03 14:11:19 Stopping service W3SVC
2018-04-03 14:11:21 Configuring database...
2018-04-03 14:11:21 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
Help.Me
- Edited by help.me.please Tuesday, April 3, 2018 11:55 AM correction
Tuesday, April 3, 2018 10:26 AM
All replies
-
>>System.Net.Sockets.SocketException (0x80004005): No such host is known
According to the log, this error is caused by WSUS server can't find the database server.
Please try to use the following command to configure the WSUS database:
%programfiles%\update services\tools\wsusutil.exe postinstall CONTENT_DIR=C:\Wsus SQL_INSTANCE_NAME=<database server name>
For detailed information, please refer to the link below:
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Proposed as answer by Xin GuoMicrosoft contingent staff Friday, May 4, 2018 6:42 AM
Wednesday, April 4, 2018 7:15 AM