'Officer Number' is already assigned to a different object
Last Updated: 2019-07-23
- Guard1 Real Time versions: 6.34 SP3 and newer
When using Active Directory Officer sync, one or more Officer records is not added/updated, and a System Maintenance Agent alert is displayed:
- Account: <Domain\UserName>: OfficerLast, OfficerFirst Id: OfficerId, 'Officer Number' is already assigned to a different object.
You have enabled Active Directory Officer sync, but have one or more manually-entered Officer records with the same Officer Number as the Active Directory employeeId values.
Delete all manually-entered Officer records and allow Guard1 Real Time to recreate them via Active Directory sync.
Alternately, disable Active Directory sync and manually enter and maintain all Officer records in Guard1 Real Time.
See topic about enabling Active Directory Officer sync.