LiveUpdate Administrator 2.x (LUA 2.x) returns the message "No Updates are currently available for the products selected in this schedule" when attempting to download new updates.

Products

• Endpoint Protection

Issue/Introduction

Why does LiveUpdate Administrator fail to download new updates?   

LUA is installed and running. Downloads are configured correctly. Manual or scheduled shows as failing. Subsequent attempts indicate that there are no updates to obtain.

 

Symptoms

The content on the LiveUpdate Administrator (LUA) server is out of date.

• A proxy server is used to access HTTP servers outside the local area network.
• lua-application.log contains the following (or similar) lines:
  20xx-xx-xx xx:xx:xx,xxx [pool-1-thread-42] ERROR com.symantec.lua.util.rcl.HttpHelper - 
  Fatal protocol violation in download: The server liveupdate.symantecliveupdate.com failed to respond with a valid HTTP response
  ...
  ...
  20xx-xx-xx xx:xx:xx,xxx [pool-1-thread-4] INFO com.symantec.lua.util.rcl.HttpHelper - Released connection for HTTP Get Method
  20xx-xx-xx xx:xx:xx,xxx [pool-1-thread-4] ERROR com.symantec.lua.handler.download.DownloadHelper - Failed to validate file : C:\TempDownload\Downloads\1258640402390\1\minitri.flg
  20xx-xx-xx xx:xx:xx,xxx [pool-1-thread-4] ERROR com.symantec.lua.handler.download.DownloadCatalog - Mini tri file not found for server, SourceServer ( BaseServer ( com.symantec.lua.mdl.server.SourceServer@20 id = 1 name = Symantec LiveUpdate username = admin connectionStatus = null deleted = false updatedTimeStamp = null connectionInfo = ConnectionInfo ( com.symantec.lua.mdl.server.ConnectionInfo@1f599d2 id = 1 hostName = liveupdate.symantecliveupdate.com hostPort = 80 protocol = HTTP contentDir = login = readOnlyLogin = null proxyName = null proxyPort = null proxyProtocol = null proxyUser = null usingWriteOnlyLogin = false ) ...

 

Cause

This issue will occur when LiveUpdate Administrator (LUA) is running in an environment where direct connections to Internet HTTP/FTP servers are blocked. It is standard practice to allow connections to Internet HTTP/FTP servers via a proxy server in such environments.

Resolution

LiveUpdate Administrator (LUA) must be configured to ultilze the HTTP/FTP proxy in order to download updates from the Internet.

Note: LiveUpdate Administrator does not support PASV mode FTP connections.

To configure LUA to connect to the LiveUpdate Source Servers through a proxy:
The following steps walk through the process of modify the default Source Servers list to add proxy information to the HTTP and FTP

1. Click on the Configure tab in the LUA interface
2. Click on the Source Servers tab from the Configure menu
3. Select Symantec LiveUpdate from the Source Servers list and click the Edit button
4. Configuring the default HTTP connection:
   1. Check the Use proxy checkbox
   2. Enter the hostname/IP address for the proxy server in the Proxy hostname/IP textbox
   3. Enter the username/password required to authenticate to the proxy server (if the proxy doesn't require authentication, leave these fields blank).
   4. Select the Proxy protocol used by the proxy server (HTTP or HTTPS)
   5. Click the Test button to ensure connectivity through the proxy
5. Configuring the failover HTTP connection:
   1. Click on the Symantec LiveUpdate - HTTP Fai... entry in the Failover Servers list and click the Edit button
   2. Check the Use proxy checkbox
   3. Enter the hostname/IP address for the proxy server in the Proxy hostname/IP textbox
   4. Enter the username/password required to authenticate to the proxy server (if the proxy doesn't require authentication, leave these fields blank).
   5. Select the Proxy protocol used by the proxy server (HTTP or HTTPS)
   6. Click the Test button to ensure connectivity through the proxy
   7. Click the OK button once connectivity is confirmed
6. Configuring the failover FTP connection:
   1. Click on the Symantec LiveUpdate - FTP Fai... entry in the Failover Servers list and click the Edit button
   2. Check the Use proxy checkbox
   3. Enter the hostname/IP address for the proxy server in the Proxy hostname/IP textbox
   4. Enter the username/password required to authenticate to the proxy server (if the proxy doesn't require authentication, leave these fields blank).
   5. Select the Proxy protocol used by the proxy server (FTP)
   6. Click the Test button to ensure connectivity through the proxy
   7. Click the OK button once connectivity is confirmed
7. Click the OK button on the Edit Source Server page to save the settings changes made

Important note: after any changes are made to the proxy configuration, do stop and restart the LUA Tomcat service of the LUA 2.x server.  This will confirm that new credentials and other details about the proxy are in effect at all levels of networking.