Dear Community Members,
I would like to get support regarding VMWare Workstation. We are using the VMWare Workstation 9.0.1 (9.0.1 build-894247) to run tests directly on TFS build agents.
It means that our Team Foundation Server 2010 customized workflow executes a custom tool (as a separate process via Process.Invoke activity) that internally uses the VIX API (COM InterOp) to create, to fill and to run interactive tests on
virtual machines (8-24 VMs are going to be started parallel depending on the current build agent's performance).
The application itself is a console app written in C# (.NET Framework 4.0).
The virtual machines are created as linked clones in case of every new triggered build.
The whole build process is running as a Windows service in the name of a build service account with Power User privileges.
The other possible solution “Running the build service host as an interactive process” supported by TFS build service on build agents is not used.
Everything works fine, if there is no open user session on the given build agent. But if accounts are logged in (remotely disconnected sessions), then the VIX-API call “IVM2.PowerOn()” throws an exception.
Date:
16.07.2013 13:16:57 368 VM_1 Error: Node failed, exception
received:*****.XXX.TestController.VMWare.VmWareException: There was an error in communication
at *****.XXX.TestController.VMWare.VmWareInterop.Check(UInt64 errCode)
at *****.XXX.TestController.VMWare.VmWareVirtualMachine.PowerOn(Int32 powerOnOptions, Int32 timeoutInSeconds)
at *****.XXX.TestController.BusinessLogic.VMNode.Initialize()
at *****.XXX.TestController.BusinessLogic.VMNode.Execute()
Based on the support site (http://www.vmware.com/support/developer/vix-api/vix16_reference/errors/errors.html) of VMWare, this error is as follows:
14010 – VIX_E_HOST_TCP_SOCKET_ERROR There was an error in communication.
Has anyone an idea why remotely disconnected, but open user sessions cause such a strange behavior at all?
It would be very important for us, because our build farm is very huge and for maintenance purposes it is not acceptable, if remote sessions are not allowed at all………
Thanks in advance!
Best regards,
József Vadkerti
