000023717 - how to resolve 'Command has expired' error

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 Number000023717
Applies Topassmark server standalone version, with .net client

 "Command has expired!" error message in pmw_server.log, user could not login and receive timeout error.

2007-06-01 15:12:14,609 DEBUG [http-443-Processor22] [] [PM-78C546917033-6499a8aa] [com.passmarksecurity.client.generic.ProtocolAdapterBase] - <Command has expired>
2007-06-01 15:12:14,609 ERROR [http-443-Processor22] [] [PM-78C546917033-6499a8aa] [com.passmarksecurity.client.generic.ProtocolAdapterBase] - <ProtocolAdapterBase failed: Command has expired!>
com.passmarksecurity.PassMarkException: Command has expired!
            at com.passmarksecurity.client.generic.ProtocolAdapterBase.handleClientRequest(ProtocolAdapterBase.java:213)
            at com.passmarksecurity.action.support.ActionUtil.initPmSession(ActionUtil.java:177)
            at com.passmarksecurity.action.SigninStartAction.doExecute(SigninStartAction.java:138)

2007-06-01 15:12:14,609 ERROR [http-443-Processor22] [] [PM-78C546917033-6499a8aa] [com.passmarksecurity.action.support.PassMarkActionBase] -
<Invalid Message Couldn't interpret message - check logs>
com.passmarksecurity.action.support.ActionUtil$InvalidMsgException: Couldn't interpret message - check logs
            at com.passmarksecurity.action.support.ActionUtil.initPmSession(ActionUtil.java:183)
            at com.passmarksecurity.action.SigninStartAction.doExecute(SigninStartAction.java:138)
            at com.passmarksecurity.action.support.PassMarkActionBase.execute(PassMarkActionBase.java:197)


CauseIn .net client configuration file, the default cookie timeout is 2 mins, if IIS webserver and passmark server has time difference more than 2 mins, the cookie will be expired when it reaches passmark server. "Command has expired" error will  be showing up and users could not login.
ResolutionPlease make sure the server time and timezone in all  IIS webservers  and passmark servers are in sync.
Legacy Article IDa35197