CLA2 Potential Error Cases

The following items can be used to troubleshoot your CLA2 implementation:

Table 1. Troubleshooting Tips
Symptom Possible Solution
You are using CLA2, and are having a problem with CLA2 (SWIFTNet or PGP). Make sure that the local CLA2 server is enabled. The following error message was probably displayed during startup: 
CmdLine2 Client is disabled. Not
starting CmdLine2 Client... If you 
wish to enable starting of the 
CmdLine2 Client be sure to set or 
add LAUNCH_CLA2_SERVER=true in 
sandbox.cfg.
This is the first thing that you should check for.
A service call failed with an error. The CLA2 server (local or remote) is configured to require authentication, but the adapter is not configured to sign the commands.
A service call failed with an error. The CLA2 server (local or remote) is configured to require SSL, but the adapter is not configured to use SSL.
The following error is displayed:
java.io.InvalidClassException: com.
sterlingcommerce.woodstock.services.
cmdline2.CmdLine2Result; local class
incompatible: stream classdesc 
serialVersionUID = 3543723007161392447, 
local class serialVersionUID = 42
 If the remote CLA2 server was not redeployed to pick up the latest classes, the CLA2 service call will fail with this error. Update the remote CLA2 server.
Issues reading the JKS file. The same major version of the JDK must be used on the CLA2 server that is used in Sterling B2B Integrator. If the JDKs do not match, the system will have trouble reading the JKS file.

If you change the default password or create a custom certificate in the keystore prior to upgrading Sterling B2B Integrator, you must back up and later restore the old keystore for the upgraded Sterling B2B Integrator instance.