Replications fail with " Start of remote replication job timed out" error message. (4039731)

On a Rapid Recovery/AppAssure core, it may be noticed that  replication jobs are failing with the following error message:

"System.TimeoutException: Start of remote replication job timed out.Job is waiting for start during long time."

One possible cause of this error message, is that replication jobs for certain agents are being held up by rollup jobs on either the source or target cores. 

For the failing agent, confirm the start time of the job on the source core, and the time of the failure.

Once this information is known, search source and target core event logs specific to the failing agent, and investigate when rollup jobs ran for that agent, and also their start and finish times.

Confirm if rollups were happening during time of the failed replication jobs.

Possible resolutions:

• Ensure the core with the issue is correctly speced, and has enough RAM for these rollup jobs to complete in a timely fashion.
• Adjust the replication schedule to allow a window for rollups to complete.
• Adjust the backup schedule on the source core to allow a window for nightly jobs to run.
• Increase the "RemoteReplicationJobStartTimeout" setting in the registry to a time that will allow for long queuing replication jobs to run. (default is 2 hours)

           HKEY_LOCAL-MACHINE\SOFTWARE\AppRecovery\Core\Replication\ReplicationService\RemoteReplicationJobStartTimeout

Windows Registry Disclaimer:

Quest Software 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.