LiveUpdate encountered one or more errors. Return code=4
Hi Guys
Don’t we just luv that error message!
Ok, here’s the layout. Two Windows 2003 servers. One is running SBS and has ISA 2000 installed. (two NICs, one for WAN and the other for LAN) The second “member” server on the LAN is running Blackberry Enterprise software and Symantec Endpoint Protection Manager v 11.0.1. Everything is working fine apart from LiveUpdates from within SEPM. (Above error message after about 3minutes from initiating Download LiveUpdate Content within SEPM.
If we crank up the command line on the member server and run LUALL.exe, LiveUpdate works fine! Using Task Manager on the member server we can watch all the processes kicking in when we manually launch LUALL from the command line. All the LiveUpdate processes launch using the system account except for the LUCallbackProxy process. That authenticates with administrator account. (Reading through these forums we can see that the LUCallbackProxy uses this account because that’s the account we logon to the member server with. That account works great and passes through ISA without any problems!)
When we watch Task Manager Processes after launching Download LiveUpdate Content within SEPM we see the same processes all using the System account, including the LUCallbackProxy. We have to assume this service needs to authenticate with the admin account to succeed?
We have tried editing server properties within SEPM and configured the Proxy Server settings to match. Ie Configured authentication to use the admin account. It made no difference to accounts used when SEPM launches LiveUpdate. All the processes still use the System account still!
How on earth do we get SEPM to launch Liveupdate with the admin account...?
I know there are newer versions of SEPM out there but we are very reluctant to upgrade. Reading through these forums we can see others have upgraded without any improvement. In fact some of their problems have got worse! It was a hard slog to get this system working as is and I’m rather gun shy to upgrade now. We can run LUALL from the member server schedule once a day and that works fine but it would be nice to get this expensive product working as it should.
Thanks
Mike
Comments
Can Modify the Service.... And DEFINITELY Upgrade!
Hi Mike
LiveUpdate and ISA should play well together, when configured correctly. The following article may help:
How to allow LiveUpdate traffic for Symantec Endpoint Protection (SEP) through the Internet Security and Acceleration (ISA) Server 2000 configured as a public firewall
To answer your specific question about how to configure LU to run as an account other than Local SYSTEM.... open services.msc, find the LiveUpdate service and click on its Properties. On the Log On tab, choose to log on as an admin account . Again, this should not be necessary with ISA 2000. Some customers have changed the account as a workaround when working with non-standard proxies.
If you are running SEP 11 MR1, I encourage you to upgrade very strongly. The current release, SEP 11 MR4 MP2, contains several hundred improvements and enhancements over what was contained in that early version. It's much more stable and reliable, plus a better performer. Within the next few weeks, there will be another even more mature release: SEP 11 RU5. Migrating to a newer version will avoid many known issues that occured with MR1.
Hope this helps!
Thanks and best regards,
Mick
With thanks and best regards,
Mick
As Mick stated, upgrade your
As Mick stated, upgrade your SEP environment. i understand your reluctance to upgrade, but so many issues have been fixed since the MR1 build. Many users here will tell you to upgrade as well. The new build is just around the corner, so you might want to wait until that is out, then jump straight to RU5.
Cheers,
Thomas
I concur - you should upgrade...BUT
I can personally attest that the newer versions are way better so you should definitely upgrade, but be very, very careful. I have never had an SAV to SEP or SEP to SEP upgrade go well. I get all kinds of weird problems like clients never updating, hard-to-troubleshoot problems like server lockups, server hangs and crashes that don't at first seem related to SEP.
I don't ever upgrade anymore. I always run Symantec CleanWipe on every computer (servers and workstations). If EVERYTHING Symantec is not completely gone (it usually is after running CleanWipe), then I do manual cleanups (delete directories, run Ccleaner Portable - http://www.ccleaner.com). I have become a HUGE fan of CleanWipe after it completely solved some major problems with several customers.
I then download and install the latest version. If you have fewer than 100 machines, take a look at http://www.symantec.com/business/endpoint-protection-small-business-edition. I have installed it at a couple of customers and it seems a bit better in a smaller environment than the full SEP.
Hey thanks guys for your
Hey thanks guys for your suggestions.
Tried adding that Protocol Definition to ISA and then ran SEPM LiveUpdate. Rats,.. No improvement!
Tweaked the LiveUpdate service to start up using the admin account next. Cranked up LiveUpdate from within SEPM and observed that LUCallBackProxy was now authenticating with the admin account. (Cool, getting somewhere!) Alas it made no difference to download results. 3 or 4 minutes later up popped “LiveUpdate encountered one or more errors. Return code=4”
Worth a crack I suppose. Liveupdate still works fine from the Win2003 scheduler.
As for updating,..... Mmmmm, that could be a very long night but I suppose we will have to give it a whirl. I’ll be taking Ghost snap shots of both operating systems before we start that’s for sure...!
Thanks again for taking the time to reply.
Much appreciated.
Cheers
Mike
Live Update failing - Error code 4
My issue was the corporate web content filter. Once I allowed the source IP through, everything worked fine.
Would you like to reply?
Login or Register to post your comment.