A Job will fail if it has less than 2 paths online. This article covers common causes of this error.
In SureSync, a Job (in SureSync 6 and older, a Job is called a Relation) must have a minimum of two paths online to execute (a source and a destination). The "Job [name of Job] is being skipped because it does not have the minimum required root paths needed to execute" error occurs when only one path is online. Often, this error will occur when running a Job that contains only two paths. If one of the paths is offline you will receive this message.
The error can occur with Jobs containing more than 2 paths but is much rarer because you need multiple paths down at the same time to bring the total online paths down to 1 to see the error.
If you’re receiving this error you should investigate the following:
-
Look in the Log Viewer to determine which path is offline
-
For SureSync 8 and newer, if this path is being accessed with the Communications Agent, launch the SureSync Desktop. Expand Computers, locate the problem machine and on the General tab click the "Test Connections to Agent" button. Does it succeed? If not, consult the steps outlined here (SureSync 8) or here (SureSync 9).
- For SureSync 7, if using a Communications Agent, launch the SureSync Desktop. Click on Home, "Communications Agent" and "Configure Communications Agents." Select the problem machine from the drop-down and click "Test Default Connection." Does it succeed? If not, you will need to investigate if the service is running and if the necessary port is open.
-
For SureSync 6 and older, if the path is being accessed with the SPIAgent, go to the Tools menu, select SPIAgent Setup, select the problem machine from the list and attempt to test to it. Does it succeed? If not, you will need to investigate if the service is running and if the necessary ports are open.
-
If the path is a UNC path, can you access it from the SureSync machine via Windows Explorer?
-
Explore potential connectivity problems
-
Explorer if the machine in question was taken offline for expected reasons. For example, a reboot for maintenance.
Once two or more paths for the Job are available it will execute properly the next time it is run.