Last week I had a problem with VMware vCAC 6.1. After installing the vCAC successfully, It came to the time where I should add a new Endpoint. In my case, I was using a VMware vCloud Director Organization as an Endpoint.
Once I added the vCD Organization endpoint to vCAC, I was not able to run Data collection, Data Collection was stuck in “In Queue” state as shown below:
I logged in as IaaS administrator to check the logs, Infrastructure> Monitoring> Log. The errors were obviously something related to the SQL database.
[UTC:2014-11-20 00:33:20 Local:2014-11-19 16:33:20] [Warning]: <?xml version="1.0" encoding="utf-16"?>
Error on Orchestrator Task Preprocess Workflows
System.Data.Services.Client.DataServiceQueryException: An error occurred while processing this request. ---> System.Data.Services.Client.DataServiceClientException: <Fault xmlns="http://schemas.microsoft.com/ws/2005/05/envelope/none"><Code><Value>Receiver</Value><Subcode><Value xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:InternalServiceFault</Value></Subcode></Code><Reason><Text xml:lang="en-US">The underlying provider failed on Open.</Text></Reason><Detail><ExceptionDetail xmlns="http://schemas.datacontract.org/2004/07/System.ServiceModel" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><HelpLink i:nil="true"/><InnerException><HelpLink i:nil="true"/><InnerException><HelpLink i:nil="true"/><InnerException i:nil="true"/><Message>The network path was not found</Message><StackTrace i:nil="true"/><Type>System.ComponentModel.Win32Exception</Type></InnerException><Message>A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I checked VMware KBs for this issue and I found KB2089503 which reports similar errors related to SQL database
As per the article and a discussion with VMware Support the MSDTC should be enabled on all SQL and IaaS servers. In fact this is a hard requirement for vCAC 6.1.x
The steps for enabling MSDTC is detailed in the above KB article. The MSDTC should look like this for a successful run of vCAC 6.1.x
After enabling MSDTC, I ran the data collection for vCD endpoint one more time and this time it completed successfully.