Information is needed on the return codes seen in the Java LiveUpdate (JLU) logs for Symantec Endpoint Protection for Macintosh (SEP for Mac), Symantec AntiVirus for Linux (SAVFL) or other products that use JLU.
Technical Information
Below are the return codes you may see in a liveupdt.log from Java LiveUpdate. Any Result Code in BOLD print will only been seen in JLU 3.x, the others may be seen in previous versions.
Result Code
|
Description
|
0 | Java LiveUpdate ran successfully |
-1 or Unknown Error Code | Java LiveUpdate failed to run successfully. |
-2001 | Java LiveUpdate could not connect and download the catalog file from any server. |
100 | Java LiveUpdate ran successfully. One of the installed updates requires a reboot to complete. |
232 | Security files missing from the catalog file, so Java LiveUpdate could not validate the file. |
233 | Java LiveUpdate encountered a security related error. |
234 | The catalog file failed verification. |
235 | The catalog file failed verification. |
236 | The catalog file has expired. Running Java LiveUpdate again should correct this problem. |
237 | Java LiveUpdate could not load the system certificates, so it could not verify the catalog file. |
242 | The user aborted Java LiveUpdate. |
243 | Java LiveUpdate was already running on the machine when this session started |
244 | Java LiveUpdate could not find the Unix utilities it needs to validate the permissions on its files. |
245 | A package retrieved from the LiveUpdate server exceeded the maximum allowed size. |
246 | A package did not qualify for download due to lack of free space with respect to maximum cache limit set. |
247 | A package did not qualify for download as the corresponding precondition for that package could not be satisfied in this client. |
248 | CommandServer failed to authenticate user. |
-2002 | Java LiveUpdate was unable to process the catalog file. |
-4001 | Java LiveUpdate failed to update its Product Inventory due to invalid data from the calling application. |
-4002 | Java LiveUpdate failed to update its Product Inventory due to invalid data from the calling application. |
-4003 | Java LiveUpdate failed to update its Product Inventory due to invalid data from the calling application. |
4000 | Java LiveUpdate successfully updated its Product Inventory. |