"Unable to get destination directory" error in liveupdt.log when running JLU from command line

Article:TECH132772  |  Created: 2010-01-27  |  Updated: 2014-08-08  |  Article URL http://www.symantec.com/docs/TECH132772
Article Type
Technical Solution



LiveUpdate fails with error "Unable to get destination directory" when it's run from the command line


Destination directory for component is not set


Depending on the component giving the error , please follow one of these 2 cases:

  • In case component is SmsVspPkgInstaller run the following command:
    • WINDOWS (x86 & x64): set VSPDIRECTORY=C:\Program Files\Symantec\SMSDOM\VSP
    • *NIX (x86 & x64): export VSPDIRECTORY=/opt/Symantec/SMSDOM/VSP
  • In case component is SmsDefInstaller, run the following command:
    • WINDOWS (x86): set SmsDefsInstall=C:\Program Files\Common Files\Symantec Shared\VirusDefs\incoming
    • WINDOWS (x64): set SmsDefsInstall=C:\ProgramData\Symantec\Definitions\VirusDefs\incoming
    • *NIX (x86 & x64): export "SmsDefsInstall"=/opt/Symantec/virusdefs/incoming
      • Note: it's very important to use the double quotes above!

Then run LiveUpdate again.

Scan Engine
Run the manual JLU session as follows:

"C:\Program Files (x86)\Java\jre7\bin\java" -cp "C:\Program Files (x86)\Common Files\Symantec Shared\Java LiveUpdate\jlu.jar;C:\Program Files (x86)\Symantec\Scan Engine\definitions\AntiVirus\tmpIncoming" com.symantec.liveupdate.LiveUpdate -c "C:\Documents and Settings\All Users\Application Data\Symantec\Java LiveUpdate\liveupdate.conf" [ -p SPE AV Definitions for x86-windows -v 7.0 -l SymAllLanguages -t virusdef -z 2012062408 ]


Run the manual JLU session as follows:

java -cp "C:\Program Files\Common Files\Symantec Shared\Java LiveUpdate\jlu.jar;C:\Program Files\Symantec\SMSSMTP\scanner\rules\AntiVirus\tmpIncoming" com.symantec.liveupdate.LiveUpdate -d [ -p SMS for SMTP Avenge Definitions for x86-winnt4 -v 5.0 -l SymAllLanguages -t VirusDef ]

Technical Information
Once the LiveUpdate process is completed successfully, there is no longer need of these environment variables.


Legacy ID


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

Terms of use for this information are found in Legal Notices