vRealize Automation MSB3073 Installation Error

Last week I was working on installing a distributed vRealize Automation (vRA) installation for a customer. The installation went smooth until I had to install the first Website and Model Manager Web Service component, then the dreadful “Error Configuring vRealize Automation Server. Open the log?” message appeared.

vRA-Error

And when I opened the vCAC-Config.log the following error was logged :

OK so lets fix this badboy, first things first.

MS DTC

Start with checking the MS DTC settings

Open Component Services and select :

Component Services –> Computers -> My Computer -> Distributed Transaction Coordinator ->
Local DTC.

Or if you have a clustered MS DTC select :

Component Services -> Computers -> My Computer -> Clustered DTCs -> Clustered DTC Name.

Right-click and select Properties
Select the Security tab and check the settings :

vRealize Automation

If you used the same template for deploying the MSSQL server (where the vRA database will be run on!) and vRA components, be sure to reinstall MS DTC on the MSSQL server AND vRA component servers:

Open a command prompt and run the following commands :

And reboot the server.

.NET 4.5.2

If a Windows 2012 R2 server is used for the vRA components make sure to install the latest .NET 4.5.2 + latest updates.

DNS

Double check all the DNS A and PTR records for the vRA components. Like database cluster, load balancing addresses etc etc.

Certificates

Double check your SSL certificates. If you are using a load-balancer be sure to use the proper FQDN’s, Short-names and IP’s of all the components in the “Subject Alternative Names” of the certificates that are behind the load-balancer.

Still not solved?

But after going through all the pre-req’s and best / common practices the same error kept appearing. Suddenly it popped up in my head that I saw this 401.1 IIS error before and I had something to do with the loopback check. I went through my notes and found the solution from the last time I had this issue. Here can you find the link to the KB article from Microsoft regarding the issue.

To fix this issue I chose method 1 “Specify host names” instead of the less-recommended one “Disable the loopback check” on the vRA component servers.

Open regedit, and then click OK.
Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0

Right-click MSV1_0, click New, and then click Multi-String Value.
In the Name column, type BackConnectionHostNames.
Right-click BackConnectionHostNames, and then click Modify.
In the Value data box, fill in the DNS alias (iaasweb.customer.com) on one line press ENTER and the server name on another (iaasweb01.customer.com) that is used for the local shares on the computer and click OK.

vRA-Regedit

If the BackConnectionHostNames registry entry already exists as a REG_DWORD type delete the BackConnectionHostNames registry entry and recreate it.

Reboot your server just to be sure (don’t forget to uninstall the vRA component and remove the HTTPS binding) and try the installation again and hopefully you’re rewarded with the same message as below :

vRA-Success

Marco van Baggum

Marco van Baggum

Marco is a Staff Consulting Architect at VMware. Want to learn more about Marco? Check out Marco's About page.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.