Applies to
- Riva On-Premise for Exchange.
- Riva On-Premise for Notes.
In rare circumstances, Riva admins have reported conflicting entity errors after moving users between sync policies using one of the following procedures:
- Move target Exchange/Notes users to another sync policy using identical category names
- Move target Exchange/Notes users to another sync policy using different category names
- Move target Exchange/Notes users to a duplicate sync policy
In this example, the user Ian Sample is moved between Sync Policy East to Sync Policy West. When Riva attempts to sync the user, a conflicting entity error is reported:
2015-02-23 12:18:46,359 ERROR [38] [(null)] Sync aborting - conflicting entity detected - EntityName: ian.sample@example.com, Policy: Sync Policy East, Conflicting Policy: Sync Policy West
Cause
This error occurs because the user's original sync destination is still in the Riva Global metadata.
Resolution
To resolve this error, the Riva Admin can perform an Override Conflicting Policy Safety re-initialization.
- Double-click the target policy to edit it.
- Select the users that were moved.
- Set Modules to All.
- Set Categories to All.
- Set Type to Override Conflicting Policy Safety.
- If a Policy Save Change Detection window appears, select Yes.
- Monitor user sync activity and confirm that there is no Sync aborting - conflicting entity detected error.