VMware Discovery Troubleshooting

• Problem. The following error message is displayed:

Required class %s not found. Verify VMware SDK jar files are present in probe. See documentation for details.

Cause. The SDK *.jar files are not copied to the Data Flow Probe.

Solution. Copy the *.jar files as described in VMware Prerequisites.

• Problem. The following error message is displayed:

User does not have required 'System.Read' permission

Cause. There is a lack of permissions from the user account when DFM connects to the ESX server's vCenter Server.

Solution.

1. Verify that credentials are defined for the VMware Infrastructure Management (VIM) protocol in the proper priority, so that credentials with full permissions have a lower index number than credentials with less permissions. For details, see "Index" in the Universal CMDB Data Flow Management Guide.

2. If DFM previously discovered connections using credentials with less than full permissions, you must rerun the connection job.

   • For ESX connection and topology: run VMware ESX Connection by VIM) to update the credentials ID attribute of ESX server, and then run the topology job VMware ESX Topology by VIM).

   • For vCenter topology: edit the integration point and choose credentials with more permissions.

• Problem. The VMware vCenter Connection by VIM or Manual VMware VIM Connection job fails with the following error message:

  java.security.cert.CertificateException: Certificates does not conform to algorithm constraints

  Cause. Java security policy has been changed in Java 7u40 or later. The key size restriction has been changed to 1024 bit or more but VMware vCenter 4.0 uses 512 bit key.

  Solution.

  1. Go to the <DataFlowProbe installation folder>\bin\jre\lib\security directory.

  2. Open the java.security file, and then find the following setting:

     jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 1024

  3. Change the value 1024 to 512 or less than 512.