Symantec Protection Engine (SPE) 8.2 does not start correctly after importing a certificate via the certinstall.jar. When restarting the service, the filesize of keystore.public is 0 bytes.
In Windows, the service hangs in a "starting" state.
In Linux, the service appears to start but is not listening on its expected ports (by default: 1344, 8004, 8006)
An internal issue causes keystore.public to be written as a 0 byte file, causing the service to fail to start correctly.
This issue will be fixed in an upcoming release of SPE. If a newer version than 8.2 is available, please upgrade to that version. If not, you can follow the steps below to restore functionality.
This is applicable only for certificates imported for use with the local Java UI. It does not affect Secure ICAP. The steps above will cause SPE to generate a new certificate to use. SPE will not be using your imported certificate.
Managing SPE without the local Java console
SPE can also be managed either through the commandline or through the centralized console.
See the following link for information on managing SPE from the commandline:
See the following link for information on using the Centralized Console: