Users are not reporting any problems accessing applications.
Both of these objects have identical RPID values, but this value must be unique per Account Provider. The first object in the list is the one that cannot be saved, and thus is the one that is not currently in use.
Release: MSPSSO99000-12.8-Single Sign-On-for Business Users-MSP Component:
Modifying the conflicting RPID of the object causing the error resolved the problem and allowed a clean XPSSweeper run. The Admin UI can be used to make this change.
As the Policy Server and XPS Tools are continually being enhanced, newer versions of tools like XPSSweeper may be capable of detecting error conditions that previous releases did not find.