000014142 - Error 'Expected 1 parameters  given 0 in constructor for class com.rsa.keymanager.core.system.mode.DefaultServerMode...' after migrating RKM Server from 2.7.1.3 to 3.1.2

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 Number000014142
Applies ToRSA Key Manager Server 2.7.1.3
RSA Data Protection Manager 3.1.2
Microsoft Windows Server 2008 R2 (64-bit)
Tomcat 5.5
Microsoft SQL Server 2008
RSA Access Manager is NOT configured
IssueError "Expected 1 parameters, given 0 in constructor for class com.rsa.keymanager.core.system.mode.DefaultServerMode..." after migrating RKM Server from 2.7.1.3 to 3.1.2
After migrating from 2.7.1.3 to 3.1.2 (which includes updating db schema and deploying new KMS.war), Tomcat starts up fine. Going to /KMS, master password prompt comes up, master password is accepted and login page comes up, kmsadmin credentials are accepted but then the following error shows on the browser:
Expected 1 parameters, given 0 in constructor for class com.rsa.keymanager.core.system.mode.DefaultServerMode : [class com.rsa.keymanager.server.transport.core.action.DefaultActionProvider, class com.rsa.keymanager.server.mode.DefaultActionChecker]
key-manager.log shows the following:
03 Jul 2012 23:49:51,413 1341377391288 kmsadmin (1) ERROR TP-Processor3 - Client : ::1, Expected 1 parameters, given 0 in constructor for class com.rsa.keymanager.core.system.mode.DefaultServerMode : [class com.rsa.keymanager.server.transport.core.action.DefaultActionProvider, class com.rsa.keymanager.server.mode.DefaultActionChecker]
03 Jul 2012 23:49:51,432 1341377391288 ERROR TP-Processor3 - Client : Internal, Error: Expected 1 parameters, given 0 in constructor for class com.rsa.keymanager.core.system.mode.DefaultServerMode : [class com.rsa.keymanager.server.transport.core.action.DefaultActionProvider, class com.rsa.keymanager.server.mode.DefaultActionChecker]
03 Jul 2012 23:49:51,432 1341377391288 ERROR TP-Processor3 - Client : Internal, Error during transaction: null
CauseThis issue occurs if unattended restart is not configured (and lockbox binaries are not installed) at 2.7.1.3 level and server is migrated to 3.1.2. Installing lockbox binaries after migrating to 3.1.2 does not seem to resolve the issue.
ResolutionA workaround is to install lockbox binaries and configure unattended restart at 2.7.1.3 level and then migrate the server to 3.1.2.
WorkaroundUpgrading RKM Server 2.7.1.3 to 3.1.2
Legacy Article IDa59088

Attachments

    Outcomes