vCenter discovery fails - "None of url, username can be null"

Tone2
Giga Contributor

‎06-14-2018 04:43 PM

I have a problem discovering a particular vCenter. I have VMware credentials, and when I test these credentials against the vCenter they are successfully validated. But when I attempt discovery of the vCenter, it fails.

The input payload to the VMWareProbe contains these results:

error="Unable to establish connection to https://xx.xx.xx.xx/sdk: java.lang.NullPointerException: None of url, username can be null." probe_time="6345" result_code="900000"

The vCenter is on SUSE Linux - most of our other vCenters are on Windows so possibly there's some requirement I'm missing here?

 

Labels:
Preview file
15 KB
Preview file
72 KB
0 Helpfuls
  • 2,806 Views
7 REPLIES 7

Juanjo
Tera Contributor

‎05-13-2019 06:23 AM

Hi all, i have solve same problem with vCenters.

If you have multiple credentials for vCenter, disable all credentials and enable only the credential what you are sure to be used and with the correct mid server. After that, it should be discovered and a credential affinity will be created for your mid server, then you can enable all other credentials.

Firs of that, it is better that you test the correct credential in the credentials form (related link Test credential).

Regards

Juanjo

SN Arch Guy
Giga Guru

‎09-28-2023 10:49 AM

This worked for me when I deactivated a second vCenter credential in ServiceNow. The earlier threads weren't clear whether to deactivate them on the vCenter side or the ServiceNow side.

 

This resolved the "Unable to establish connection to https://xx.xx.xx.xx/sdk: java.lang.NullPointerException: None of url, username can be null." error for me.

0 Helpfuls