Troubleshooting Java LiveUpdate (JLU) 3.6 installed with Symantec Mail Security for Domino (SMSDOM) 8.x on Windows

Article:TECH97627  |  Created: 2009-01-20  |  Updated: 2011-06-16  |  Article URL http://www.symantec.com/docs/TECH97627
Article Type
Technical Solution


Environment

Issue



JLU is not working as expected.

Symptoms
As a result of the JLU not working correctly virus definitions are not being updated.
 


Cause



There are multiple reasons that this condition can occur.


Solution



Note: Keep in mind that file/folder paths could be different if different installation paths are used. If any of the paths in this document are not matching the environment which is under investigation then it may be necessary to do a little research to find the correct paths. The ones listed here are default paths.


    1. If the following files exists please delete prior to trying LiveUpdate from GUI.
    C:WINDOWSTempJlu.Session.End.dat
    C:WINDOWSTempsmsdulck
    %USERPROFILE%Local SettingsTempsmsdulck
     

    2. Go to folder C:\Documents and Settings\All Users\Application Data\Symantec\Java LiveUpdate  

    3. If liveupdate.conf file is 0 bytes then this is a sign that Java Cryptography Extension (JCE) is not installed.
    Determine which version of Java you are using by opening a command window and typing java -version  and then get and install JCE that matches the installed Java version.
    Or download and install the latest Java and Java Cryptography Extension by going here   http://java.sun.com/javase/downloads/index.jsp
    At the least it is necessary to download the Java SE Runtime Environment (JRE) and the Java Crytpography Extension which is down near the bottom of the page under Other.
    If an internal LiveUpdate Administrator server is being used to get definitions it would then be necessary to remove all of the hosts lines in the below liveupdate.conf text except the first one which begins with hosts/0/url . On that line it is necessary to change the address to the IP or FQDN of the LiveUpdate Administrator server and by default that software uses port 7070 which may be different if changed. There is usually also a default folder path of clu-prod.
    An example may look like this   host/0/url=http://192.168.10.10:7070/clu-prod
    The text in this file is CASE SENSITIVE: 
    ############################################################
    #                                                          #
    # livepdate.conf - Symantec LiveUpdate configuration file  #
    #                                                          #
    # This file is used to configure the settings used by      #
    # LiveUpdate                                               #
    #                                                          #
    ############################################################

    hosts/0/url=http://liveupdate.symantecliveupdate.com:80
    hosts/1/url=http://liveupdate.symantec.com:80
    hosts/2/login:ENC=b3effdd10d982d2c7339c9604c67c34c
    hosts/2/password:ENC=18d2e2d4c1445548f8a5ef124ed20bfd
    hosts/2/url=ftp://update.symantec.com/opt/content/onramp
    logfile=C:\Documents and Settings\All Users\Application Data\Symantec\Java LiveUpdate\liveupdt.log
    serverlogging=true
    workdir=C:\Documents and Settings\All Users\Application Data\Symantec\Java LiveUpdate\Downloads

    4. If using a Proxy it is necessary to add the following lines as needed also to the liveupdate.conf file. Not everyone who uses a proxy needs a proxy username and password and so in those cases do not add the last two lines.
    Minimally you need to add the proxy server IP Address and port.
    Example would be proxy=198.162.10.10:80. Here are the lines:
    proxy=IP:PORT
    proxyusername=
    proxypassword=

    5. There is one more setting that can be added to the liveupdate.conf file that can be useful.
    By default JLU will keep 2gigs of cache data in the downloads folder.
    This can be disabled by adding the following line in the liveupdate.conf file. 
    cacheMode=false

    6. Make a backup copy of the liveupdate.conf file.
    Configurations can be changed from the JLU ConfigEditor but it is real handy having a text version of the liveupdate.conf file.
    For example if the same settings are to be used by JLU on other machines then copy this file over to the secondary machine where they should be applied.
    Once JLU runs the liveupdate.conf file will become encrypted by newer versions of JLU and it will no longer be readable without using the JLU ConfigEditor.
    Also, the encrypted file will not work if moved over to other machines. 

    7. Check the file size of Product.Catalog.JavaLiveUpdate.
    If this is 0 bytes then this is another sign that something went wrong with the previous installation.
    If this is not 0 bytes there still could be a problem with the information in it.
    The following text is the default lines. If this file is 0 bytes or you suspect something else is wrong with this file make the file look like this:  
    [{6B9B12D6-93E0-460e-BF4E-0A7251925D80}]
    MONIKER={6B9B12D6-93E0-460e-BF4E-0A7251925D80}
    PRODUCTNAME=SMSDOM Windows Virus Definitions
    PRODUCT=SMSDOM Windows Virus Definitions
    VERSION=8.0
    LANGUAGE=English
    SEQ.VirusDef=0
    [{C498C4FD-B2DE-4415-BE68-5CA2BD9D113F}]
    MONIKER={C498C4FD-B2DE-4415-BE68-5CA2BD9D113F}
    PRODUCTNAME=SMSDOM VSP
    PRODUCT=SMSDOM VSP
    VERSION=2.0
    LANGUAGE=SymAllLanguages
    SEQ.VSP=0

    8. Now try running LiveUpdate from the GUI of the product that is installed.

    9. If LiveUpdate still does not work create a text file in the same folder as your liveupdate.conf called symc-defutils.conf and then add the following text.
    [defutillog]
    defutillog_name=file1.log

    10. Now try running LiveUpdate from the GUI again. Collect the following files and send them to us for review:
    C:\Documents and Settings\All Users\Application Data\Symantec\Java LiveUpdate \ Product.Catalog.JavaLiveUpdate
    C:\Documents and Settings\All Users\Application Data\Symantec\Java LiveUpdate \ liveupdate.conf
    C:\Documents and Settings\All Users\Application Data\Symantec\Java LiveUpdate \ liveupdt.log
    C:\Program Files\Common Files\Symantec Shared\VirusDefs\file1.log

     
     
    Links to other KB articles that may be of interest:
    Troubleshooting JLU 3.2 installed with SMSDOM 8.x on AIX
    Troubleshooting JLU 1.10 installed with SMSDOM-MPE 3.2.x
    Installing and Configuring Symantec LiveUpdate Administrator Server for SMSDOM 8.x
    How to configure SMSDOM 8.x to retrieve Virus Definitions from LiveUpdate Administrator Server  




 

 



Legacy ID



2009112013315254


Article URL http://www.symantec.com/docs/TECH97627


Terms of use for this information are found in Legal Notices