Adding a New HA Standalone VM to an Existing Neverfail IT Continuity Engine v7.1 P2V DR Pair May Fail at the Configure Clone Operation Step



This Knowledgebase article provides a workaround for Creating/Adding a (new) HA standby server to an existing IT Continuity Engine v7.1 DR pair, when the Primary server is not a VMware virtual machine (for example, physical, Hyper-V, etc.) and the following symptom is seen:

More Information


During the creation of the new HA server (Secondary - which will be created from the Primary, thus a P2V conversion), the Engine Management Service may show that the deployment of the new HA server failed with the following message (Ref EN-1007):

ERROR: Failed configuring clone operation.

Also, the EMS C:\Program Files\Neverfail\tomcat\hblogs\HBWSLog.txt contain corresponding logged events like:

2015-05-25 05:58:58,550 INFO380293CloneOperationsSubmitter(com.neverfail.webservices.vcenter.web.VCenterSecondaryCloneSequencerResource) - VCenterCloneSequencer> informChangeCloningStatus(lj-hyv-en295.qawan.test), oldStatus=Configuring clone operation..., newStatus=Failed configuring clone operation

2015-05-25 05:58:58,550 WARN380293CloneOperationsSubmitter(com.neverfail.webservices.install.tasks.base.Task) - ClusterReconfigAndCloneSubmitTask> Task failed.


at com.neverfail.webservices.vcenter.install.tasks.steps.SubmitCloneOperationStep.execute(

at com.neverfail.webservices.install.tasks.base.Task.executeCurrentStep(

at com.neverfail.webservices.install.tasks.base.Task.execute(




at java.util.concurrent.ThreadPoolExecutor.runWorker(

at java.util.concurrent.ThreadPoolExecutor$


Caused by: com.neverfail.webservices.exceptions.InternalServerException

at com.neverfail.webservices.vcenter.install.clone.drivers.EngineVMWareConverterDriver.installAgent(

at com.neverfail.webservices.vcenter.install.clone.drivers.EngineVMWareConverterDriver.validateAndstartConversion(

at com.neverfail.webservices.vcenter.install.clone.drivers.EngineVMWareConverterDriver.startConversion(

at com.neverfail.webservices.vcenter.install.clone.drivers.AbstractVCenterConverterDriver.start(

at com.neverfail.webservices.vcenter.install.tasks.steps.SubmitCloneOperationStep.execute(

... 8 more

Caused by: Unable to complete Converter agent installation on 'lj-hyv-en295.qawan.test'. Error code: 1,603 .


This is a known VMware vCenter Converter Standalone 5.5 issue. Additional details about this issue can be found in VMware vCenter Converter Standalone 5.5 Release Notes.

Subsequent P2V conversions of remote source machines that run 64-bit Windows Vista or later might fail after a successful conversion

If you convert successfully a remote source machine that runs 64-bit Windows Vista, Windows Server 2008, or Windows 7 operating system and then try converting it again, the conversion fails with the error message Converter Standalone Agent installation failed on x.x.x.x Error code: 1603, where x.x.x.x is the IP address of the source machine.

This error message might occur if automatic uninstall of remote Converter Standalone agent has been enabled during the first successful conversion.


Restart the remote source machine and try running the conversion task again.

Applies To

Neverfail IT Continuity Engine v7.1 - P2V installations

VMware vCenter Converter Standalone 5.5

Related Information


0 out of 0 found this helpful



Please sign in to leave a comment.