VMWARE Probe - <HostName> is not responding (reason: Connection and/or inventory update failure)

Document ID : KB000111661
Last Modified Date : 20/08/2018
Show Technical Document Details
Issue:
When we are testing the connection in the vmware probe GUI we are getting the below error:
 
VMWARE Probe throwing error, when Testing credentials through IM: Exception Log: (12) Login Failed, VMWare API is unavailable, 
Exception caught trying to invoke method RetrieveServiceContent;Nested exception is java.net.UnknownHostException: 
lnsrv205: Exception caught trying to invoke method RetrieveServiceContent

This same probe works with two other VMWARE hosts.
Credentials verified correct and API at /MOB is functional and navigates without error.

Below is the output we are getting in the vmware log file at loglevel 3:
 
java.net.UnknownHostException: <HOSTNAME> at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:103) 
at com.vmware.vim25.ws.VimStub.retrieveServiceContent(VimStub.java:1675)
 at com.vmware.vim25.mo.ServiceInstance.retrieveServiceContent(ServiceInstance.java:246) 
at com.vmware.vim25.mo.ServiceInstance.constructServiceInstance(ServiceInstance.java:126)
 at com.vmware.vim25.mo.ServiceInstance.(ServiceInstance.java:79)
 at com.vmware.vim25.mo.ServiceInstance.(ServiceInstance.java:69) 
at com.nimsoft.probe.application.vmware.sdk.VmwareEnvAdaptor$ServiceInstanceFactory.getServiceInstance(VmwareEnvAdaptor.java:201) 
at com.nimsoft.probe.application.vmware.sdk.VmwareEnvAdaptor.login(VmwareEnvAdaptor.java:259) ... 
11 more Caused by: java.net.UnknownHostException:<HOSTNAME>
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184) 
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) 
at java.net.Socket.connect(Socket.java:589) 
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668) 
at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173) 
at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:432) 
at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:264) 
at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) 
at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1105) 
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:999) 
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177) 
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1283)
at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1258) 
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:250) 
at com.vmware.vim25.ws.WSClient.post(WSClient.java:165) 
at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:91) ... 
18 more Aug 19 18:17:05:250 [Data Collector - <HOSTNAME>, vmware] PERF: START: Vmware setup graph with resource <HOSTNAME>
Aug 19 18:17:05:250 [Data Collector - <HOSTNAME>, vmware] PERF:DONE: Vmware setup graph with resource lnsrv205 {Seconds=0.000} 
Aug 19 18:17:05:250 [Data Collector - <HOSTNAME>, vmware] Inventory update failed. Sending resource alarm 
Aug 19 18:17:05:251 [Data Collector - <HOSTNAME>, vmware] (12) login failed, VMWare API is unavailable. 
Aug 19 18:17:05:251 [Data Collector - <HOSTNAME>, vmware] PERF: DONE: ----- Pass-1446 --- Data Collector Check Interval for: <HOSTNAME> {Seconds=0.003} 
Aug 19 18:17:05:251 [Data Collector - <HOSTNAME>, vmware] PERF: Memory Status: Max=3641 CurrentAllocated=1067 Free=455 Used=612 MB 
Aug 19 18:17:05:251 [Data Collector - l<HOSTNAME>, vmware] DataCollector for <HOSTNAME> finished collecting data
Environment:
UIM 9.0 and earlier
VMWARE probe 6.87 and earlier
robot 7.95 and earlier
Cause:
There was a problem with the local DNS entries for the host name being used for the connection
string in the vmware probe.
 
Resolution:
Correct the DNS entry for the hostname or FQDN being used in the vmware probe.
or add an entry in the local hosts file so the name can be properly resolved.