vRA 7.3 PhysicalHostPingService: ignoring exception. IAAS Service error MSDTC Issue

Pretty much EVERY time I install vRA Version 7.* I always get an error relating to the vRA IAAS Service.

It stops Endpoint Compute Services from being displayed, stops data collection of all added endpoints and generally makes vRA a paperweight.

The error can be found under Infrastructure>Monioring, you’ll know you have issues if you have hundreds\thousands of the same error!


The full error looks like this…


The error is related to the MS DTC service, if your Windows SQL Server and Windows IAAS Manager Servers have been rolled out from the same vSphere template then you will likely get the error, I read a large number of blogs that say this only happens if Sysprep hasn’t been run, however I see this issue whether SYSPREP is run or not. The GUID of MS DTC doesn’t seem to change and the duplicate GUID entries of the SQL & IAAS Manager Server results in the issue.

Uninstalling\Re-Installing\Re-Configuring MS DTC seems to be the most appropriate resolution to this issue, I run the following commands on all IAAS Manager Servers and SQL Servers. I then restart The SQL, IAAS MAnager & vRA Appliance for good measure.

Uninstall-Dtc -confirm:$false


Set-DtcNetworkSetting -DtcName "Local" -RemoteAdministrationAccessEnabled:$False -RemoteClientAccessEnabled:$True -InboundTransactionsEnabled:$True -OutboundTransactionsEnabled:$True -LUTransactionsEnabled:$True -XATransactionsEnabled:$False -AuthenticationLevel Mutual -Confirm:$False


VMware vCenter Workflow Manager service not starting

I had an issue where a vCenter update to 6.0u2a failed and rolled back, after a restart we were unable to power on VMs there were in a powered off state.

On further inspection we found that the “VMware vCenter workflow manager” service wasn’t started and would not start.

In the Workflow-manager.log log located here C:\ProgramData\Vmware\vcenter\logs\workflow\ I could see error relating to the service not starting and “Error Creating bean with name ‘jmxconnectorstarter’”


Scroll a little further in the Workflow-manager.log and you should see the phrase “Caused by”


My error stated “Port value out of range: -1”

Browsing to the workflow.properties file located here C:\ProgramData\Vmware\vCenterServer\cfg\vmware-vpx-workflow\conf


In this file the workflow.jmx.port was set to -1, this was changed to 19999 by VMware support and hey presto, the service started!

Powering on all VMs was then possible within the VC.

Moral of this story… name your beans!