Collections against one or more vCenter Server data centers fail

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• Collections against one or more vCenter Server data centers fail
• Collections against other vCenter Server data centers may succeed
• One ore more virtual machine templates are present in the affected data center
• In the $ALIVE_BASE/user/log/collector.log file on the Analytics VM, you see errors similar to:

462 ERROR [VMVI RetrieverThread Datacenter Connection 1:3] (14) com.integrien.adapter.vmware.PropertyRetriever.run - Exception occurred
com.vmware.vim.vmomi.client.exception.VmomiProtocolException: com.vmware.vim.vmomi.core.exception.UnmarshallException: Missing value for non-optional field fileKey
...
Caused by: com.vmware.vim.vmomi.core.exception.UnmarshallException: Missing value for non-optional field fileKey

Environment

VMware vRealize Operations Manager 6.0.x

Cause

This issue can occur when one ore more virtual machine templates are missing a value for the fileKey parameter.

Resolution

To resolve this issue, you must ensure that the fileKey parameter value for the template is set correctly.

To determine and ensure that the fileKey parameter value is set for a template:

1. Log in to the vCenter Server managed object browser (MOB). The URL for the MOB is https://VC_IP/FQDN/mob.
2. Click the Content link.
3. Click the group-d1 link.
4. Click the datacenter-# (datacenter_name) link corresponding to the affected datacenter.
5. Click the group-v3 (vms) link.
6. If the template is stored at the root of the data center, click the vm-# (template_name) link for the suspect template. If the template is stored in a folder under the root of the data center, click on the group-v# (folder_name) link and then on the vm-# (template_name) link.
7. Click the layoutEx link.
8. For each disk listed in the disk area, click the disk[<####>] link and then the chain link. If the fileKey item has no value, this template is causing the issue or is one of multiple templates that are causing the issue.
9. Repeat steps 1 to 7 to identify all templates that may be causing the issue.
10. After identifying all templates that are causing the issue, convert each of these templates to a virtual machine and then back to a template. This sets the fileKey attribute properly and allows collections against the parent data center to succeed.

Additional Information

If there are less number of templates, it may be faster to convert all templates to virtual machines and then back to templates.