|Applies To||RSA ACE/Server|
|Issue||RSA ACE/Server Primary and Replica synchronization fails occasionally|
Cannot Send Token to Replica 3620 (192.168.137.11) ace 1017 9. [perelt.c.2702.288448]
Trigger: TRIGERROR: ttk_usnm.p: user not found for token (192.168.137.10) ace CrossRealm ACM_OK 0. [Trigger.0.367358]
Token record is locked and cannot be updated. Will attempt to update at next replication pass.000073383003 (192.168.137.10) ace Progress General Failure 0. [tokmerge.c.241.367359]
Cannot Update(Create) Token On Replica 3614 (192.168.137.10) ace Progress General Failure 0. [perelt.c.3208.367360]
Error Modifying Record (192.168.137.10) ace Progress General Failure 0. [sloop.c.672.367361]
Trigger: TRIGERROR: ttk_usnm.p: user not found for token (192.168.137.10) ace CrossRealm ACM_OK 0. [Trigger.0.367362]
NOTE: All the above errors appear in sequence in the system log on the Primary ACE/Server, and the sequence is often repeated many times, causing the system log to fill quickly.
Database Inconsistency: Replica Rejecting EnabledGroup Delta Modify C 81 G 27
(126.96.36.199) CrossRealm ACM_OK 0. [perelt.c.10593.66095]
NOTE: The above error occurs many times in the system log on the Replica ACE/Server.
|Cause||The remote administration program occasionally applies database updates incorrectly such that the information cannot be sent to the replica(s).|
|Resolution||This issue is resolved in RSA ACE/Server 5.0 patch 3. The fix is also incorporated into ACE/Server 5.1 and will be part of all future releases.|
Note: this does not fix the information that is already in the database. After applying the patch, please synchronize the databases of the Primary and Replica manually by creating a replica package on the Primary. For more information on this, refer to the solution What is a Replica Packageand how togenerate one in RSA ACE/Server running on UNIX platforms?.
You should look for the following error in a popup message when administering the database after deploying the patch. It will read:
Database operation failed on trigger level.
If you see this message, the operation you are currently performing will fail. The benefit of this is that before application of the patch, the database modification was not failing on the administration level, but was causing replication to fail in the background. With the application of the fix, the administrator can take immediate remedial action by reapplying the changes, thus maintaining database integrity at all times.
|Legacy Article ID||a9576|