Replication Job Cancelled - "Start of the remote replication job timed out. The job has been waiting a long time to start". (4038429)

After a replication job has been waiting in queue for more than two hours the job is automatically cancelled with the following error:

"Start of the remote replication job timed out. The job has been waiting for a long time to start."

Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.

Solution 1:

Increase the timeout to allow more time in queue before cancellation.

1. Stop all active jobs
2. Stop the core service
3. Open Regedit
4. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Replication\ReplicationService
5. Increase the RemoteReplicationJobStartTimeout to 10:00:00
6. Start the core service.

Solution 2:

The replication job may be in queue due to a long rollup job or a long list of backups and replication jobs. It may be best to schedule replication in such a way that it does not overlap with backups and rollup jobs.

• To Schedule Replication
• To Schedule Backups