000014404 - AxM 'Bad Message Format' error when attempting to start aserver.

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 Number000014404
Applies ToRSA Access Manager 6.2
IssueAxM "Bad Message Format" error when attempting to start aserver.
dispatcher.log (or lserver.log if using the log server) shows the following error:
sequence_number=3,remote_client=192.168.206.170,2013-10-21 08:07:21:215 PDT,messageID=-2,event_type=Internal Error,internal_error=Bad Message Format client address: 127.0.0.1:60218

aserver.out standard output file in DDEBUG modeof the aserver shows the following message:
08:09:21:227 [*] [KeyServerPool] - Keyserver returned an error - unable to get session key.

dispatcher.out standard output file in DDEBUG mode of the dispatcher shows the following message:
08:09:21:228 [*] [KeyMessageHandler-2] - Sent failure message.
CauseThis error indicates that the aserver registration key in the keyclient.sec file of the aserver does not match the key stored in the keyclient.sec file on the dispatcher machine.   The key used by the aserver must be registered against the keyserver, and must exist in the keyserver.sec file.
ResolutionCopy over a valid keyclient.sec file to the aserver machine.  If you do not have one, use the keygen utility to create one. 
Legacy Article IDa62820

Attachments

    Outcomes