Lucomserver_3_0

Hi. For the past 2 days I have gotten this error message
Lucomserver_3_0 has caused an error in unknown
Lucomserver_3_0 will now close

I am wondering if anyone here knows what it means and how to fix it. Thanks
DBJoans

It's caused by Norton/Symantec Live Update. Disable the service, there
is no need to have it running automatically and all the time. Your
version must be pretty old, Symantec has issued new versions of Live
Update that corrects the problem. You can just do a search for
Lucomserver on the Symantec site for more information, example:
http://search.symantec.com/custom/up...r=sup&x=21&y=7

John


DBJoans wrote:
Hi. For the past 2 days I have gotten this error message
Lucomserver_3_0 has caused an error in unknown
Lucomserver_3_0 will now close

I am wondering if anyone here knows what it means and how to fix it. Thanks
DBJoans

John John wrote:

It's caused by Norton/Symantec Live Update. Disable the service,
there is no need to have it running automatically and all the time. Your
version must be pretty old, Symantec has issued new versions of
Live Update that corrects the problem. You can just do a search for
Lucomserver on the Symantec site for more information, example:
http://search.symantec.com/custom/up...r=sup&x=21&y=7

Let's hope that this is the only error caused by Live Update. Given the
age of their Symantec software the OP would be very well advised to check
out that system restore is functioning correctly and that the state
manager is discarding older files and checkpoints as newer ones are
archived so as to keep the size of the archive within the user defined
limits.
--
Mike Maltby

Mike M wrote:

Let's hope that this is the only error caused by Live Update. Given the
age of their Symantec software the OP would be very well advised to
check out that system restore is functioning correctly and that the
state manager is discarding older files and checkpoints as newer ones
are archived so as to keep the size of the archive within the user
defined limits.

Indeed. I was going to suggest that maybe the OP get rid of
Norton/Symantec but then I thought that if I tell him/her to do that
he/she will probably post back saying that the removal broke something
else. g

John

"John John" wrote in message
...
It's caused by Norton/Symantec Live Update. Disable the service, there
is no need to have it running automatically and all the time. Your
version must be pretty old, Symantec has issued new versions of Live
Update that corrects the problem. You can just do a search for
Lucomserver on the Symantec site for more information, example:

http://search.symantec.com/custom/up...r=sup&x=21&y=7

At least for some of us, it was CAUSED by a recent (as in "within the last few
weeks") update. My kids machine started doing this several days after an
update about three weeks back. Mine started it a week later. The fixes noted
on the page you reference didn't fix the kids system, so I just turned it off.
When mine started it, I didn't bother trying the fix, I shut it off. When a
third machine did it, I uninstalled Nortons and put up McAfee.

The problem (I was seeing) is that lucomserver (and something else I forget at
the moment) is started by the automatic live update, but never exits. When
another instance comes along (even a manual invocation) and tries to run, it
gets fouled up by the one that's already running. Killing it (I used Process
Explorer) allows others to run. If the "other" is another automatic one, it'll
also leave lucomserver (and the other thing) running, and you're back to the
same problem. Running a manual live update doesn't leave cruft behind.

Now, as I said, I tried the procedures on the site and they didn't work. But
it's been a couple of weeks, so I just tried a manual download of Live Update
(the first suggestion on the fix list) again. To may surprise, this time it
worked. As in "solved the problem." The manual download/install succeeded
before. I've watched two automatic updates run since I did it, and in both
cases, lucomserver exited when it was done.

- Bill