000018552 - ACE/Server log shows error: 'Next Tokencode bad'

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

Article Content

Article Number000018552
Applies ToRSA ACE/Server
IssueError: "Next Tokencode bad"
Token in Next Tokencode mode
User attempted to answer the Next Tokencode prompt, but entered a code that was not valid for the token.
Error: "Access Denied"
CauseUser did not enter a valid Tokencode from a later time than the Tokencode used for the initial authentication.
ResolutionInstruct the end-user in the correct response to the ACE/Agent prompts.

End-user instructions can be found at RSA ACE/Server Documentation under "Other Documentation" in the following files:

Local Authentication with an RSA SecurID Standard Card or Key Fob

Local Authentication with an RSA SecurID PINPAD

Remote Authentication with an RSA SecurID Standard Card or Key Fob

ACE/Agent for Windows NT Remote Access Computers

Remote Authentication with an RSA SecurID PINPAD
The Administrator can manually resynchronize the token. This requires that the Administrator have access to the actual tokencodes displaying on the fob.

1. Open Start > Programs > ACE Server > Database Administration.

2. Select Token > Edit Token.

3. Enter token serial number, or select Tokens to choose from a list.

4. Select Resynchronize Token, and enter consecutive Tokencodes in the dialog windows.
Legacy Article IDa1602

Attachments

    Outcomes