I'm having the same problem with a couple of my clients aswell.  I've had a case open with symantec for sometime with no luck.  The MR1 was supposed to fix the problem but it didn't.  I'm trying soooo hard not to flame the BETA release software. 

Has anyone got a fix for this? :smileyvery-happy:

Message Edited by roma on 01-21-2008 03:50 PM

I have the same error on one of our client PCs, too.  I un_installed then re_installed SEP 11 on the client that has the error.  It solved the problem.

I had this problem on a PC which could not be cleaned by re-installing or any such thing.

Check the LiveUpdate log file in "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate".  If you find that your log file has the following in it "> Account launching LiveUpdate is not a logged in user's account" then the following may work....

Open command prompt.  Go to "C:\Program Files\Symantec\LiveUpdate" dir and run lucheck.exe and then luall.exe.  This fixed the problem for me but whether this PC will get future updates is another question.

There is a knowledge base article that talks about this issue:

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008013109171848

It's a little light on help but reading it reminded me that I had changed the exceptions policy after creating the installation package.  So, I created a new one that contained my updated policy, uninstalled SEP on the problem machine, and then installed the package I had just created.  The TruScan protection is now running properly with the lastest definitions.