Symantec Connect
  • Login
  • Register
  • Security
    • All of Connect
    • Backup and Archiving
    • Clustering and Replication
    • Endpoint Management & Virtualization
    • Storage Management
    • Security
    • Inside Symantec
    • Vision User Conference
    • Partners
    • Developers
    •  
  • Overview
  • Forums
  • Articles
  • Blogs
  • Downloads
  • Events
  • Videos
  • Groups
  • Ideas
Login to participate
Security Community BlogRSS

Disk Full Message Erroneously Appears when Downloading LiveUpdate Definitions

Kedar Mohile's picture
Kedar Mohile
June 20th, 2009
Filed under: Endpoint Protection (AntiVirus), Basics, Basics, Best Practice, Best Practice, Configuring, Configuring, Evolution of Security, Evolution of Security, Features, Features, Installing, Installing, LiveUpdate, LiveUpdate, Performance, Performance, Reporting, Reporting, Security, Tip/How to, Tip/How to, Upgrade, Upgrade, Security Community Blog

Disk full message erroneously appears when downloading LiveUpdate updates

If your network environment already supports the proxy servers that are compliant with the HTTP 1.1 protocol or later, you can disregard this entry.

After you have tried to download LiveUpdate for the first time, the following message might appear:

"LU1863: Insufficient free disk space
There is not enough free disk space for LiveUpdate to operate properly. Please free up disk space on your computer and run LiveUpdate again."

You might have insufficient disk space. However, it is much more probable that this message appears in error because the proxy server is unable to send the correct Contents-Length header field.

This error message might appear on Symantec Endpoint Protection Manager, a Symantec Endpoint Protection client, or a Symantec Network Access Control client.

You should verify that the disk drive to which you downloaded LiveUpdate has sufficient disk space. If you verified that the disk drive has sufficient space, then most likely a proxy server caused the problem.

If a proxy server receives an HTTP reply that does not include a Content-Length header field, then the above-listed message erroneously appears. The erroneous message appears on the computer on which the LiveUpdate has been downloaded.

The proxy servers that are compliant with HTTP 1.1 protocols automatically include Content-Length header-entity fields. The proxy servers that are compliant with HTTP 1.0 protocols do not automatically include Content-Length header-entity fields.

You should ensure that the proxy servers in your network are compliant with the HTTP 1.1. protocol.

Now we need to look at how to make a proxy server compliant with HTTP 1.1 protocols. The answer here is that the configuration differs from the Proxy software/device we are using. For example if we are working with Microsoft ISA Server this link should help

HTTP 1.1 Support in ISA Server

Reference: "Readme.txt" from "Symantec_Endpoint_Protection_11.0.4000_MR4_AllWin_EN_CD1",</pre>

+3 (3 votes)
  • Kedar Mohile's blog
  • Login or register to post comments
  • Comments RSS Feed
Nel Ramos's picture
Nel Ramos
32 weeks 4 days ago

thanks for this good

thanks for this good preparation of facts..
this helps.

Nel Ramos

+2 (2 votes)
  • Login or register to post comments
Kadoneng's picture
Kadoneng
31 weeks 5 days ago

yes I also encountered such

yes I also encountered such problems. its nice to know some possible solutions!!!

+1 (1 vote)
  • Login or register to post comments

Would you like to reply?

Login or Register to post your comment.

About Security Community Blog

The Security Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Security community. Any authenticated Connect member can contribute to this blog.
Filter by:

Recent Blog Posts

  • Take the Shortest Survey Ever - REALLY!
    Hear4U - February 08, 2010
  • SEP 11.0.X Unable to apply the SEP server patch on this computer
    sezam - February 02, 2010
  • Need Help Deploying Symantec Data Loss Prevention?
    desert_lady - February 01, 2010
  • Defrag your SEPM Server Regularly
    snekul - February 01, 2010
  • Slides and Notes from the South Florida Security & Compliance User Group Meeting -1/28/10
    rcarela - February 01, 2010

Blog Tags

Best Practice Installing Reporting Security SecurityExpressions
© 2010
  • Symantec Corporation
  • Contact Us
  • Get RSS
  • Newsletter
  • Privacy Policy
  • Symantec.com