Popular Knowledge Base Articles

Top 20 vRealize Automation articles for December 2016

Top 20Here is our Top 20 vRealize Automation (vRA) articles list for December 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. How to remove a virtual machine from Management in vRA or vCAC
  2. vRA appliance runs out of disk space
  3. Removing a virtual machine from vRealize Automation 7.x using Cloud Client
  4. Various tasks fail while calling stored procedures with errors: “Error executing query usp_”
  5. Error ‘Unable to authenticate user. Please try again’ when logging to vRA 6.2.x VAMI page
  6. Troubleshooting 404 and 401 errors in vRA 6.x by validating component configuration
  7. Confirming and bench testing MSDTC communication for vRA
  8. vRA 7.x services fail when modifying the vIDM database
  9. Directory sync in vRA 7.x fails with error ‘Connector Communication failed with Response’
  10. Provisioning a machine in VMware vRealize Automation fails with the error: CloneVM : Sequence contains no matching element
  11. Renaming the VMware vSphere Cluster used in a VMware vRealize Automation environment
  12. Joining the VMWare vCenter Server Appliance or VMware vRealize Automation Identity Appliance to a domain fails with the error: Error trying to join AD, error code [31]
  13. Using the VMware vRealize Production Test Tool to validate and test your vRealize Automation configuration
  14. vRA 7.0 installation wizard prerequisite checker halts on error: “Waiting for host to trigger a restart”
  15. Error ‘BadCredentialsException’ when connecting to the embedded vRO instance on a clustered or HA distribution of vRA 7.0
  16. After the vRA update, Infrastructure tab fails with 401 Error
  17. Status of TLSv1.1/1.2 Enablement and TLSv1.0 Disablement across VMware products
  18. Logging in to embedded vRealize Orchestrator fails
  19. ASD day 2 action is executed on the wrong VM in vRA
  20. How to move the vRA SQL database to a new server