LiveUpdate (3.3.0.69) stops downloading after 3500 KB within Backup Exec 2010 MP1 (13.0.2896) => LU1835: Connection to the LiveUpdate server failed

Here is our Setup:

Hardware:    W3K Server

Software:     New BE2010R2 install

                     BorderManager Firewall/Proxy Server

History:

Liveupdate on Backexec 2010 would fail at stages when downloading updates. As suggested above, I cleared the cache in liveupdate, I customized settings (porxy) but nothing resolved the issue. After 3 hours I decided that maybe the firewall had something to do with it.

I was hesitant but I decided to disabled the filters. Although the Update would start an error was always returned, "not enough disk space". With 23 GB free I did A disk cleanup but to my disapointment the process would continue to fail.  I didnt like the idea of exposing all of my ports to the world so I quickly abandoned that idea after a brief exposure.

Next, I zero'ed in on the Proxy server and the Cache. So I downed the proxy server. That process took 3 minutes. Then I reloaded the proxy server with the -cc (Clear Cache) command. Reloading the Proxy Server took longer than usuual as the this Firewall/Proxy server was operating without incident for 465 days (I love Novell Products they run without fail forever).  After I proxy loaded correctly I tried liveupdate and It worked!

So, if you have a software Firewall/Proxy server, like Novell's BorderManager, look to reset/empty the Cache.

It worked for us!

Just for info of Ryan.H - by default running LiveUpdate from within the Backup Exec console is configured to ONLY let you see the Backup Exec updates - it should not show you the updates for other Symantec products when you start LiveUpdate in this way.

Similarly by defaulty if you run luall.exe directly from the folder it should not show you Backup Exec updates but show you the updates for other Symantec products.

The above comments relate to the more recent versions of Backup Exec some of the earlier versions worked differently and we received complaints that the schedule for updating Anti-Virus would try and update Backup Exec as well - often causing backup job failues if this happened overnight. Hence we seperated Backup Exec's registration in LiveUpdate from that of other applications as a default.

You can change this behaviour using BEUpdateOps.exe

For others closer to my situation:

I was having the same problem with it stopping at 3500, then 7000, then immediately, and then it would repeat that cycle.  We do not use a proxy.  It only occurs on 2k8 servers.  2k3 servers have no issues updating through LiveUpdate.  I found that checking the option under the HTTP tab of LiveUpdate Config (in control panel) for "I want to use my Internet Options HTTP settings" caused all Win2k8 servers with BE 2010 or BE 2010R2 to fail.  It seems that choosing this option, which is the default after installation, is the same as choosing "I want to customize my HTTP settings for LiveUpdate" and then not entering in any proxy address or port number.  It's basically taking that first selection to mean you do use a proxy server, whether you do or not and then giving no addressing since there's none to give.  Based on what others have said above, it looks to me like the selection to take settings from Internet options isn't working whether you use a proxy server or not.  So if you're like me, change it specifically to "I do not use a proxy server for HTTP."  I did the same on the FTP tab.  Essentially, the "I want to use my Internet Options HTTP settings" isn't working at all so pick one of the other two option depending on whether or not you use a proxy in your environment.

Also, I've been finding that LiveUpdate run from within BE 2010 increasingly does not see any Symantec products installed that can be updated.  However running luall.exe from outside of BE causes it to see all installed products and updates them properly.

LiveUpdate under 64bit 2008 servers seems to be not at all ready for prime time.  I know many others having these exact same problems, plus all the people who have posted here.

Kudos guys! => Indeed!

The customers must help themselves as the technical Support from Symantec is not efficient anymore. I could tell you stories about the support which no one would believe me. Reaction time of 10 (!) days on critical cases... callbacks on midnight on my voicebox...

Thanks SG for the compliments. We admins are responsible to keep our community thriving. Hence our actions. I' happy to see your issue resolved, which paved path for many other users looking for a solution related to similar issues. Kudos guys!

Hi Hamster1066,

Thank you very much. This finaly solved also my issue I had with LiveUpdate!

@Swathi: Wow, you're fast if you want something from me/the customer. But where were you/was Symantec in the last month to help me/the customer to solve this issue?? All the (few) Symantec employees who respond to that threat either didn't read my detailed explanation on what I already tested and suggested me to do the same again or they just told me it's a "firewall issue" means it's the fault of the customer itself!

Sorry but this sucks, Symantec!

Best regards,
 SG

This solved the issue for me immediately, thanks heaps.

Funny how this thread has be here for almost 6 months and the day that I run into this issue it got an answer...

Definite bug in the way LiveUpdate handles proxies under 2008R2. I put some logging on the firewall and as soon as the file size hits 3500kb LiveUpdate disregards the proxy and attempts to go direct to the internet (which won't work if you have a half-way serious firewall configuration)

@SG, can you please close this thread off by marking a comment as a solution? Thanks!

Just some scrolls upwards...

https://www-secure.symantec.com/connect/forums/liveupdate-33069-stops-downloading-after-3500-kb-within-backup-exec-2010-mp1-1302896-lu1835-c#comment-4554831

A modification of the "Settings.LiveUpdate" didn't change anything. Furthermore we do have a Proxy Server, so disabling it will not work...

Best regards,
 SG