All deployments failing with error 'Internal Server Error [Error Reference ID:]'

Products

• VCF Automation

Issue/Introduction

• When attempting to deploy a new Virtual Machine (VM), the deployment fails and displays a generic "internal error".
• Users also observe that the configured cloud zones appear to be unavailable in the deployment interface.
• The provisioining-service-app.log shows the following error, or one similar:
  provisioning/requests/compute-active-directory-tasks/<UUID>] [ad-integration] Active Directory Action null for request <Request ID> failed with errors:Action run failed with the following error: "Unable to connect - please verify your server credentials and connectivity to the server via LDAP."
• Some additional error codes related to LDAP errors could also be:
  
  • 'Cannot establish ldap connection with URI'
  • 'ServerDownLdapException'
  • 'CommunicationException: Connection Timed Out'
  • 'Error received by LDAP client'
  • 'Cannot contact LDAP server'

Environment

• Aria Automation 8.x
• Identity Management integration with Active Directory (AD)

Cause

The issue is caused by the system's identity configuration pointing to an Active Directory (AD) LDAP server that has become isolated (inaccessible) from the environment.

• The deployment process cannot perform the required authorization check because it is unable to contact the configured LDAP server.

• The connection failure prevents the system from correctly retrieving or displaying available resources (like cloud zones), leading to the internal error.

This is confirmed in the application logs:

In the provisioning-service-app.log the error was seen: Action null for request <UUID> failed with errors: Action run failed with the following error: "Unable to connect - please verify your server credentials and connectivity to the server via LDAP."

Resolution

Update the Identity Management configuration to point to a reachable Active Directory LDAP server.

1. Access the Identity Management configuration section for your product.

2. Locate the Active Directory or LDAP integration settings.

3. Change the server address(es) configured for LDAP/AD to a Domain Controller that is known to be accessible and reachable by the product (i.e., not isolated).

4. Save the changes.

5. Test the VM deployment process to confirm that cloud zones are now visible and deployment proceeds normally.

Additional Information

This situation often occurs when a configured Domain Controller is decommissioned, moved, or becomes unreachable due to a network or firewall change. The error is logged as an "internal error" because a critical external dependency (LDAP connectivity) failed, causing the core service to abort the deployment process.