[Discovery\vCenter] vCenter discovery fails with error "java.lang.NullPointerException: None of url, username can be null" - Support and Troubleshooting
During the vCenter discovery, "VMWarevCenterDatacentersProbe" probe fails with the error,
<result error="Unable to establish connection to https://xx.xx.xx.xx/sdk: java.lang.NullPointerException: None of url, username can be null.">
Also, the test credential will give the error "Invalid target specified"
The respective "ecc_queue" input will have the below exception,
com.snc.automation_common.integration.exceptions.UnknownException: None of url, username can be null. at
com.snc.core_automation_common.util.AKeyedConnectionFactory.getConnection(AKeyedConnectionFactory.java:158) at
com.snc.core_automation_common.util.AKeyedConnectionFactory.getConnection(AKeyedConnectionFactory.java:122) at
com.snc.core_automation_common.util.AKeyedConnectionFactory.getConnection(AKeyedConnectionFactory.java:110) at
com.service_now.mid.pipeline.command.TestCredentialCommandImpl.executeRawCommand(TestCredentialCommandImpl.java:141) at
com.snc.core_automation_common.pipeline.ACommand.execute(ACommand.java:114) at com.service_now.mid.probe.CommandPipeline.probe(CommandPipeline.java:63)
at com.service_now.mid.probe.AProbe.process(AProbe.java:103) at com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:122) at
com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.NullPointerException:
None of url, username can be null. at com.vmware.vim25.mo.ServiceInstance.constructServiceInstance(ServiceInstance.java:115) at
com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:79) at com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:69) at
com.service_now.mid.probe.vmware.VMWareConnectionFactory.getConnection(VMWareConnectionFactory.java:57) at
com.service_now.mid.probe.vmware.VMWareConnectionFactory.getConnection(VMWareConnectionFactory.java:27) at
com.snc.core_automation_common.util.AKeyedConnectionFactory.getConnectionUseOneCred(AKeyedConnectionFactory.java:228) at
com.snc.core_automation_common.util.AKeyedConnectionFactory.getConnectionIterateOverCreds(AKeyedConnectionFactory.java:182) at
com.snc.core_automation_common.util.AKeyedConnectionFactory.getConnection(AKeyedConnectionFactory.java:135) ... 11 more
When analyzing the MID server agent logs with ("mig.log.level" - "debug") enabled could find the below log entries,
(928) Worker-Interactive:VMWareProbe-31922c47db0a54d4276a15784b961912 SEVERE *** ERROR *** The specified credential 'xxx-svcServiceNowDiscove' does not exist in the specified vault. Specific Error: PDKTC006E Failed to connect to provider (Reason=[Connection refused: connect], Rc=[-1]) (928) Worker-Interactive:VMWareProbe-31922c47db0a54d4276a15784b961912 SEVERE *** ERROR *** The specified credential 'xxx-svcServiceNowDiscove' does not exist in the specified vault. Specific Error: PDKTC006E Failed to connect to provider (Reason=[Connection refused: connect], Rc=[-1]) (928) Worker-Interactive:VMWareProbe-31922c47db0a54d4276a15784b961912 SEVERE *** ERROR *** Problem with client's CredentialResolver: Problem resolving the credential: java.lang.RuntimeException: class javapasswordsdk.exceptions.PSDKException: The specified credential 'xxx-svcServiceNowDiscove' does not exist in the specified vault. Specific Error: PDKTC006E Failed to connect to provider (Reason=[Connection refused: connect], Rc=[-1])
Release
Any release
Cause
CyberArk Base Agent will not be installed/running in the target servers due to which discovery fails with the error, "The specified credential 'xxx-svcServiceNowDiscove' does not exist in the specified vault. Specific Error: PDKTC006E Failed to connect to provider (Reason=[Connection refused: connect], Rc=[-1]"
Resolution
To resolve the issue install/restart the CyberArk Base Agent in the target servers.
Related Links
Refer CyberArk online document for related errors and solution.
The world works with ServiceNow.
Sign in for more!There's more content available only to authenticated users