The company I work for enables me to download and use on any personal PC or Laptop the Norton Antivirus Corporate Edition version 7.51.857. I have this loaded on my Windows 98 PC and all is well. It is also loaded on my Windows ME Laptop, but from today it is a bit sick.

The Liveupdate function (which I run weekly) is producing the following message "LU1844: LiveUpdate could not determine if there is an update for this product because the update list for this product is corrupted" againe the Avenge 1.5 MicroDefs and AV Engine 5.0 Definitions.

I have scoured the Symantecs site where the message number LU1844 not only relates to a different message, but also only to the Home / Small Business version of the software. I have also tried completely uninstalling and reinstalling it.

Can anyone help?

Are you running a firewall on your laptop, if so it might be blocking access to the update location. Please post back with the result.

thanks,

ach

Thanks for your reply. Yes, I use ZoneAlarm Pro. I've checked the log of hits, but I don't recognise anything related to Norton or the Liveupdate. Any further help would be appreciated.

Many thanks,

Neil

OK, I think that the Norton liveupdate program is called LUCOM...something. Could you check for that in your logs?

The module you are referring to is LuComServer.EXE. I've checked the alerts log and there is nothing on it for this module. Just to make absolutely certain. I ran the LiveUpdate as the first task after boot up today, then rechecked the logs - there was no alert! Further, I checked my laptop ZoneAlarm settings against my PC settings, where it is working, and they are the same.
I rather suspect that it is not the firewall because LiveUpdate is quite happy to download the virus definitions update, which it does at the same time as the Avenge 1.5 Microdefs.
There seems to be 2 components to this programs, LuComServer.exe and LuComServerPS.dll. My PC version is 1.70.22.0 dated 19/11/01. The version on the laptop, however, is 1.90.14.0 dated 18/06/2003. I don't know if the difference is because one is for Windows 98 and the other for Windows ME, or if my laptop is just more up-to-date than the PC and the new version is causing the problem. It is probably worth trying to check out this out of the Symantecs site, but I don't hold up too much hope as their site is not exactly users friendly for problem solving.
In the meantime if you can any further please let me know.

See if this article helps NeilR

Thank you for the link above to the recent Symantec support document. I too had a similar problem with running live update due to a corrupted file list. I have used the product for four years and only started getting problems since updating with the 2004 Systemworks version. Contacting a christmas cracker manufacturer would of probably been more use than Symantec support......after 5 responses from them where they just directed me to the obvious each time, I finally gave up and took the risk of running live update without Norton PF enabled and defeating the object of having the product in the first place!

After using the link in the post above, it appears that checking the "use http 1.1 through proxy connections" as mentioned by opening internet explorer, going to tools, going to internet options, going to advanced has finally solved my problem after 3 months!

Why is it that this has only had to be done with this latest version though? The previous versions never needed this?

Glad we could help martyn but why? Sorry, I dont know.

Thank you one and all for trying to help. I exhausted all the help that symantec could (or would give) to no avail; their final response being 'Failing the above, I cannot think of any additional steps to suggest
that have not already been suggested or tried' - gee thanks!

Somehow I managed to get into the logs of the update process and discovered that it was failing because it was not able to decode the downloaded files, due to some component missing from the Symantecs server.

I decided to revert back to an earlier version of the LiveUpdate program and, hey, surprise, surprise it works! So I'm happy now and will leave you all alone. Thanks again for your help.

NeilR

I'm glad that you found a satisfactory fix and thanks for posting back and letting us know the workaround NeilR.

As your problem is resolved, I'll close this thread. If you have any further problems and would like this thread re-opened, feel free to PM any of our staff.