Quantcast
Channel: VMware Communities : All Content - vRealize Automation Tools
Viewing all articles
Browse latest Browse all 9859

vRA 7.1 - Error when provisioning VM - Error processing [PowerOn]

$
0
0

I am receiving this error when provisioning a VM from vRA.

Error Message:

Error processing [PowerOn], error details:

[] - A general system error occurred: No connection could be made because the target machine actively refused it


Stack Trace:

at DynamicOps.Vrm.Agent.vSphere.VSphereTaskRequest`1.WaitForTaskToComplete(ManagedObjectReference taskMoRef, TimeSpan timeout)

at DynamicOps.Vrm.Agent.vSphere.VSphereTaskRequest`1.ExecuteImpl()

at DynamicOps.Vrm.Agent.vSphere.VSphereHypervisorServiceProvider.PowerOn(VSphereVirtualMachine machine)

at DynamicOps.Vrm.Agent.BaseHypervisorAgent`3.PowerOn(WorkItem workItem, PropertyBagHelper propertyBagHelper)

at DynamicOps.Vrm.Agent.BaseHypervisorAgent`3.ProcessWorkitem(WorkItem workItem, String task, PropertyBagHelper propertyBag)

at DynamicOps.Vrm.Agent.vSphere.VSphereAgentService.ProcessWorkitem(WorkItem workItem, String task, PropertyBagHelper propertyBag)

at DynamicOps.Vrm.Agent.BaseAgent.ProcessWorkitem(WorkItem workItem)

 

 

It was initially working fine and I was able to provision the VMs successfully. However, this error came after the Infra team renamed the clusters in the vCenter.

I am not sure if this error is related to vCenter changes?

 

From the vCenter, I can see that the VM has been provisioned (cloned) successfully. However, it is not able to POWER ON.

Error from vCenter:

NameTargetStatus
Power On virtual machineTMD004    

A general system error occurred:

No connection could be made because the target machine actively refused it

 

After this error, the vCenter will delete the VM.


Viewing all articles
Browse latest Browse all 9859

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>