search cancel

Scan Engine & Symantec Protection Engine Live Update Status: Unable to Update


Article ID: 159253


Updated On:


Protection Engine for Cloud Services Scan Engine Protection for SharePoint Servers Protection Engine for NAS


The Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files are a required component for Java LiveUpdate to run with Scan Engine/ Symantec Protection Engine
 Java LiveUpdate may exhibit abnormal behavior without the JCE installed.


  • Java LiveUpdate fails.
  • Unable to access the configuration utility (java -cp /path/to/jlu.jar ConfigEditor)
  • Zero Byte liveupdate.conf or configuration file not encrypted


  1. Installed Java version not supported (x86 or x64)
  2. Missing Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files


Download and replace the Java Cryptography Extension (JCE) from:

Download the needed JCE according to the JAVA JRE version installed
Example: Download JCE6 if you have JRE6 installed.


How to check if the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files are missing:

1. Compare policy file sizes
The policy files with the JCE are slightly different than the ones included with Java.

Compare the policy file sizes of what is downloaded from Oracle to those in the Java lib folder to the ones downloaded with the JCE. If the sizes are not the same the JCE is not installed.

Example for JRE6: 

  • Default Location
    <java-home>/lib/security   (Unix)
    <java-home>\lib\security   (Windows)
  • Typlcal Windows 32 bit Operating Systems
    C:\program files\java\jre6\lib\security\US_export_policy.jar
    C:\program files\java\jre6\lib\security\local_policy.jar
  • Typical Windows 64 bit Operating Systems
    C:\program files (x86)\java\jre6\lib\security\US_export_policy.jar
    C:\program files (x86)\java\jre6\lib\security\local_policy.jar
  • For information to locate the JAVA path within the Operating System used, please review the following:

2. Compare MD5 hash of the policy files.
Compare the policy file hashs values (MD5, SHA1, CRC32, etc) to those from the JCE. The JCE policy file size and hash data is not published here because it may change when Oracle updates Java or releases a new JCE.

3. Check liveupdt.log file
The liveupdt.log file contains the following lines:
<date & time> IdsEncodingFailed
<date & time> IdsCheckJCEPolicyFiles
<date & time> IdsEncodingFailed
<date & time> IdsCheckJCEPolicyFiles

The above is an indication the JCE files are missing.