BusObjectService fails to start with error 'No such host is known' in EngageOne Designer



BusObjectService fails to start with error message :

User-added image

Windows->Application error event logs from the same time shows:
Service cannot be started. System.Exception: Service startup error:
Configuration File Path: "C:\Program Files (x86)\PBBI CCM\DOC1\Designer\Server\BusObj.config"
Please run the Repository Configuration Tool.
Remoting configuration failed with the exception 'System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Net.Sockets.SocketException: 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 System.Runtime.Remoting.Channels.CoreChannel.GetMachineIp()
   at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.SetupMachineName()
   at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(IDictionary properties, IServerChannelSinkProvider sinkProvider, IAuthorizeRemotingConnection authorizeCallback)
   at System.Runt...


This could be caused due to following:
  • Machine not being part of any Domain and Workgroup.
  • Hostname not getting resolved to any IP address which is important for service to run. This can be verified by using command nbstat command as follows which would show 'Host not found' . <IP> is placeholder for IP on which BusObjectService is installed.    
// This should be IPV4 address for that machine.nbtstat -a <IP>
Ideally, output of this command should point to hostname of machine where service is failing however results shows it was not getting resolved:
Local Area Connection:
Node IpAddress: [] Scope Id: []
Host not found.
Local Area Connection 2:
Node IpAddress: [] Scope Id: []
Host not found.
Wireless Network Connection:
Node IpAddress: [] Scope Id: []
Host not found.


UPDATED: June 7, 2017
  • Server machine is part of a Domain or Workgroup.
  • DNS lookup is functioning appropriately.
If issue is not resolved, contact Client Support.