Aria Automation Orchestrator workflows fail with "TypeError: Cannot read property 'id' from null"

Products

• VCF Automation

Issue/Introduction

 

• VMware Aria Automation workflows fail in the environment.

• The following error is observed in the workflow logs:

  Error in (Workflow:<workflow> / <workflow> (item3)#91) TypeError: Cannot read property "id" from null
  ...
  'attribute': name=instance type=VC:VirtualMachine value=__NULL__
  'attribute': name=enpoint type=VAPI:VAPIEndpoint value=dunes://service.dunes.ch/CustomSDKObject?id='ENDPOINT--https___<vcenter_hostname>_api'&dunesName='VAPI:VAPIEndpoint'
  

• In the VMware Aria Automation Orchestrator inventory, the vCenter Server plugin appears blank or empty.

• Running the Add a vCenter Server instance workflow fails with the error: Permission to perform this operation was denied.

• Logging into the vCenter Server UI directly with the integration service account results in permission errors.

 

Environment

 

• VMware Aria Automation

• VMware Aria Automation Orchestrator

• VMware vCenter Server

 

Cause

This issue is caused by insufficient permissions assigned to the service account used for the vCenter Server integration. Specifically, the account has been removed from the Administrators role (or the specific role required for the integration) within vCenter Server.

 

 

Resolution

To resolve this issue, restore the required permissions to the service account in vCenter Server.

1. Log in to the vCenter Server using the [email protected] account or another account with administrative privileges.

2. Navigate to Administration > Access Control > Global Permissions.

   • Note: If permissions were applied at a specific object level (e.g., Datacenter or Cluster), navigate to that object and select the Permissions tab.

3. Locate the service account used by Aria Automation Orchestrator.

4. Edit the user permissions and ensure the account is assigned the Administrators role.

5. Log in to the VMware Aria Automation Orchestrator client and re-run workflow "Add a vCenter Service instance".

6. Validate that the vCenter Server inventory is now visible.

7. Retry the failed workflow to confirm the issue is resolved.