While setting up vCAC 6.0 in my home lab, I encountered the following error when trying to deploy a machine from a blueprint.
Error requesting machine. Inner Exception: Exception has been thrown by the target of an invocation. Base Exception: The partner transaction manager has disabled its support for remote/network transactions. (Exception from HRESULT: 0x8004D025)
I found a VMware KB article for an earlier version along similar lines which requires configuring some MSDTC settings on the SQL server holding the vCAC database.
Update 30/10/2013: There’s an updated post on the PowerShell Team Blog which now describes this situation with .NET 4.5 as a pre-requisite in more detail.
-———————————————————————————————-
PowerShell 4.0 which shipped as part of Windows Server 2012 R2 and Windows 8.1 is now available for down-level Windows versions via the downloadable Windows Management Framework 4.0.
WMF 4.0 contains updated versions of the following features:
Windows PowerShell Windows PowerShell Integrated Scripting Environment (ISE) Windows PowerShell Web Services (Management OData IIS Extension) Windows Remote Management (WinRM) Windows Management Infrastructure (WMI)
I sincerely hope this saves somebody else some time because I had a fair amount of head scratching with this today. Installed a Windows Server 2012 VM on vSphere 5.0 U2, pretty standard install with a C:\ drive for OS, Software etc and D:\ for data. This particular server needed to run SQL Server 2012, however the install kept repeatedly failing with the error “Could not find the Database Engine startup handle”.