000025593 - Error: '** FIND FIRST/LAST failed for table replace-token-buffer.(565)' when unassigning replacement token and 'this token is curently locked by another administrator.' appears.

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000025593
Applies ToReplacement token
RSA Authentication Manager 6.1.2
UNIX (AIX, HP-UX, Solaris)
Issue

Error: "** FIND FIRST/LAST failed for table replace-token-buffer.(565)" when unassigning replacement token and 

"this token is curently locked by another administrator." appears.


Error: "The token to be replaced has been deleted, possibly by another administrator"
Error :"cannot lock the token" appears on the log monitor
Cannot unassign replacement token
Cannot delete token
 If a replacement token does its initial authentication to a replica AM and the same token is modified in some way on the primary before the replica pushes  
over the changes then the token record can end up with invalid data in its iReplacing or iReplaced fields.
Observable results are conflicting views from the admin GUI (for example, edit user shows no tokens but edit token shows that token is assigned) or
"ACCESS DENIED, can't lock token" log messages on subsequent authentication attempts.
Resolution

This issue has been addressed in BugID 60303. A hot fix is available from RSA Customer Support.  

Please contact RSA Technical Support and request Authentication Manager 6.1 hotfix 60303.

The hot fix consists syncsrvc.exe (for RSA server running Windows) and it needs to be replaced in ace/prog directory.

The fix for server running on UNIX consists the file acesyncd and it needs to be replaced in ace/prog directory.

NotesHotfix rollup 3 (or higher) for AM6.1.2 contains the fix for 60303
Legacy Article IDa8248

Attachments

    Outcomes