Symantec Scan Engine (SSE) 5.2.x, Symantec Protection Engine (SPE) 7.0.x won't start if Java Runtime Environment (JRE) is updated AFTER the SSE/SPE installation
Last Updated November 25, 2013
You installed Symantec Scan Engine (SSE) 5.2.x / Symantec Protection Engine (SPE) 7.0.x on a Linux host. Later, when you update the server-side Java Runtime Environment (JRE), you cannot start symcscan any longer.
SSE/SPE does not automatically recognize the new path to updated JRE.
Best practice for the initial installation is to always install JRE first. However, if you need to update JRE after SSE/SPE installation, manually update the JRE path information, which is referred by SSE/SPE.
1. Login to the SSE/SPE host as root via SSH with an SSH client or with the local terminal program.
2. Stop SSE/SPE.
# /etc/init.d/symcscan stop
3. cd to the SSE/SPE's product root, which is by default /opt/SYMCSCan/bin
Note that if you explicitly changed the install location you need replace the following path with your own.
# cd /opt/SYMCScan/bin
4. Open symcscan.sh with the text editor of your choice.
IMPORTANT: It's always a good idea to backup symcscan.sh before you edit the file.
5. Edit the JRE's path location which is referred by SSE/SPE as follows.
PATH=%NEW JRE ROOT PATH%/bin:/usr/bin:/bin
JavaJRELib=%NEW JRE ROOT PATH%/lib/i386
6. Save symcscan.sh
7. Start SSE/SPE.
# /etc/init.d/symcscan start
how to update server-side JRE after SSE/SPE installation
Imported Document ID: TECH212732
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe