search cancel

Unable to login to vCenter to monitor VM's - vmware] (12) login failed, VMWare API is unavailable


Article ID: 254054


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


vmware probe is installed on the Primary Hub but the defined account to access vCenter is getting errors:

 at com.nimsoft.probe.application.vmware.sdk.VmwareEnvAdaptor$ServiceInstanceFactory.getServiceInstance( 
 at com.nimsoft.probe.application.vmware.sdk.VmwareEnvAdaptor.login( 
 ... 14 more 
[Data Collector -, vmware] PERF: START: Vmware setup graph with resource
[Data Collector -, vmware] PERF: DONE:  Vmware setup graph with resource   {Seconds=0.000} 
[Data Collector -, vmware] Inventory update failed. Sending resource alarm 
[Data Collector -, vmware] (12) login failed, VMWare API is unavailable. 
 at com.nimsoft.probe.application.vmware.sdk.VmwareSession.updateInventory( 
 at com.nimsoft.probe.common.ctd.CtdSession.doInventoryUpdate( 
 at com.nimsoft.probe.application.vmware.collector.VmwareDataCollector.executeSessionUpdateInventory( 
 at com.nimsoft.probe.common.ctd.ProbeDataCollector.execute( 
 at java.util.concurrent.Executors$ 
 at java.util.concurrent.FutureTask.runAndReset( 
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301( 
 at java.util.concurrent.ScheduledThreadPoolExecutor$ 
 at java.util.concurrent.ThreadPoolExecutor.runWorker( 
 at java.util.concurrent.ThreadPoolExecutor$ 
Nov 09 16:26:28:973 [Data Collector -, vmware] PERF: DONE:  ----- Pass-008 --- Data Collector Check Interval for:   {Seconds=5.446} 
Nov 09 16:26:28:973 [Data Collector -, vmware] PERF: Memory Status: Max=1820   CurrentAllocated=191   Free=170   Used=21 MB 
Nov 09 16:26:28:973 [Data Collector -, vmware] DataCollector for finished collecting data 


  • Release: UIM 20.3
  • vmware probe 6.87


Best practice is to deploy the vmware probe on a separate hub and not the Primary hub since it can end up requiring significant java memory allocation and you don't want to overload the Primary with a storage probe that requires a lot of resources/processing.

Also, vmware version 6.87 is a very old version of the vmware probe. The current GA version is 7.18 which is far superior in terms of VMware monitoring, reliability, scalability, and performance.

The error-> vmware] (12) login failed, VMWare API is unavailable, is usually caused by

- incorrect user credentials, and/or
- permission issues for the configured user

Check the vmware.cfg file or vmware probe via raw configure mode and make sure that the username and password are current, valid/what you expect.

From a web browser running on the robot where the vmware probe is deployed, try accessing the Managed Object Browser (MOB) of the configured vCenter or ESX server using the user and password configured in the failing probe profile:

https://<FQDN (or the IP address) for the ESX/ESXi or vCenter Server>/mob

If there are access issues for the configured user, they can be determined here.  Once these issues are resolved on the vCenter or ESX/ESXi server, test the connection again from the vmware probe.

Last but not least, check the release notes and most importantly the vmware probe requirements which are many and can be found here: