Error: Cannot commit object <object> '<object name>' (4294909)

Corporate policy requires that the service account cannot be used for logging onto the desktop, so a separate account that operates InTrust Manager is required to be created. The separate account has been added to the local group, "AMS Organization Servers."

InTrust is installed with the installation account and is running fine. When logging into the OS with the separate account, the user receives the following error whenever trying to commit any changes:

Error: Cannot commit object <object> '<object name>'
To be able to perform this operation, you must have the Modify permission on the Operator '<object name>' object.
To cancel only the operation on this object, refresh the contents of the Personnel node. This will update all the objects that it contains.
To cancel all modifications you have made since the last commit, refresh the InTrust Manager root node.

Reason: Updating collection failed. Reason: User <sam account> has no effective right 'WriteData'(4) on <object> (Guid='<object's guid>').

Two example error messages:

Error: Cannot commit object Operator 'netsend person'
To be able to perform this operation, you must have the Modify permission on the Operator 'netsend person' object.
To cancel only the operation on this object, refresh the contents of the Personnel node. This will update all the objects that it contains.
To cancel all modifications you have made since the last commit, refresh the InTrust Manager root node.

Reason: Updating collection failed. Reason: User S-1-5-21-1812075908-345333784-1466847840-1110 has no effective right 'WriteData'(4) on ADCNotificationOperator (Guid='{81BE4B26-6348-402D-AD99-20C5B00E587B}').

 

Error: Cannot commit object Job 'Trace Report'
To be able to perform this operation, you m