Data Copy Access (DCA) job power-on timeout failure


Data copy access (DCA) job fails to detect the heart beat for one or many instant recovery VMs.


A Data Copy Access (DCA) job inaccurately reports one or many instant recovery VMs fail to boot. Review of the state of each VMIR reveals that they have booted up successfully.


To work around this problem, modify the registry for the production VM to increase the default time-out value for the service control manager. To increase this value to 1800 seconds (30 minutes), follow these steps:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:
  3. In the right pane, locate the ServicesPipeTimeout entry.

    Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
    1. On the Edit menu, point to New, and then click DWORD Value.
    2. Type ServicesPipeTimeout, and then press ENTER.
  4. Right-click ServicesPipeTimeout, and then click Modify.
  5. Click Decimal, type 1800000, and then click OK.

    This value represents the time in milliseconds before a service times out.    Note This change does not take effect until the computer is restarted.
  6. Take another backup (new full not necessary)
  7. Wait for the backup to replicate If running the DCA job from a target appliance.
  8. Re-attempt the Data Copy Access (DCA) job.


Either VMware tools or Hyper-V integration services did not start which has prevented the VM guest heart beat from being detected.


A slow service does not start due to time-out error in Windows

Copy Data Management (CDM/DCA) test fails to detect VMWare Tools


Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section