From PC2wiki
Revision as of 00:23, 28 November 2018 by Doug Lane (talk | contribs) (On Server startup shows message configuration file corrupt: add text)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Frequently Asked Questions (FAQ) are maintained on the PC² web site.

If you are troubleshooting or trying to get PC² to work, read the Troubleshooting section.

Click here to view FAQ.

FAQ Sections

Unable to login as admin using Java 1.8

This problem has been found only with Java 1.8.0_161 and pc2 version 9.5.2 and earlier.

PC^2 Version 9.5.3 fixes this problem, download this version by clicking this link

The symptoms are as follows:

  1. The server startup seems to work
  2. When logging in the Admin is stuck with a busy (hourglass) cursor
  3. In the pc2 server log file there will be a an error (see below)

Java 1.8.0_161 and later have changed encryption and that causes a login problem and more. Since pc2 encrypts both network communications and files - both areas are affected.


This work around is for versions before 9.5.3

To work around this problem one must specify true for a system property jdk.crypto.KeyAgreement.legacyKDF. So in each pc2 script, ex pc2server or pc2admin one must add the java system property


just after the javaw command, thus

javaw -Djdk.crypto.KeyAgreement.legacyKDF=true 

In the pc2 server log there will be an error message

java.security.NoSuchAlgorithmException: Unsupported secret key algorithm: DES


PC2 Version 9.5.3 fixes this problem. Download the new version by clicking this link

The fix was to update the scripts to use the workaround described in the previous section.

On Server startup shows message configuration file corrupt

On server startup a message like this may appear on the console.

edu.csus.ecs.pc2.core.security.FileSecurityException: FAILED TO DECRYPT
at edu.csus.ecs.pc2.core.security.FileSecurity.readSealedFile(FileSecurity.java:458)
at edu.csus.ecs.pc2.core.security.FileSecurity.load(FileSecurity.java:626)
Halting server - configuration file corrupt check logs

See article: Server Diagnostics for more information about the FAILED TO DECRYPT message.

See Also