Root Path cannot be enabled because it conflicts with other root paths
When adding a new job with a new root path, overlapping paths can block enabling the path.
MFT groups root paths to share some processing to improve efficiency. This handling requires that parent root paths are created before creating subfolder references. If you create a parent folder reference after subfolders have already been defined, you can encounter a conflict.
One way to resolve the conflict is to use the Desktop program and the 'Manage Database History' feature to correct the database. This requires stopping the Hub service while making the changes,.
Another method to remedy the problem is to temporarily modify the root paths of the subfolder roots paths and then change them back.
As an example, let say you have root paths already defined for c:\FolderA\Sub1, c:\FolderA\Sub2. Your error occurs when trying to enable a new root for c:\FolderA. This might only be a problem if other new root paths were created with subfolders of FolderA.
To resolve the issue, change the root path for c:\FolderA\Sub1 to c:\xxx. Change the root path for c:\FolderA\Sub2 to c:\xxx. When all subfolders have been changed, you can then change them all back to their original values. This will recognize c:\FolderA as a parent group, resolving the issue.
Note that when you change a root path, history for that root path is deleted. A scan of the root path will performed when you enable the job again.