SEPM Event 11.0.3001, 11.0.2020, and 11.0.2010 Win64 failed to update when 11.0.4000 is installed
I received the following logs:
12/19/2008 03:49:10 Legere SEP Test svr-septest Info Download is current Symantec Endpoint Protection Win64 11.0.4000.2295 (English) is up-to-date.
12/19/2008 03:49:06 Legere SEP Test svr-septest Warning Antivirus and antispyware definitions Win64 11.0 MicroDefsB.CurDefs failed to update Symantec Endpoint Protection Win64 11.0.2020 (English) failed to update.
12/19/2008 03:49:02 Legere SEP Test svr-septest Warning Antivirus and antispyware definitions Win64 11.0 MicroDefsB.CurDefs failed to update Symantec Endpoint Protection Win64 11.011.0.3001.2224 (English) failed to update.
12/19/2008 03:48:58 Legere SEP Test svr-septest Info New LiveUpdate content has been downloaded Antivirus and antispyware definitions Win32 11.0 MicroDefsB.CurDefs was successfully updated. 12/19/2008 03:48:41 Legere SEP Test svr-septest Warning Antivirus and antispyware definitions Win64 11.0 MicroDefsB.CurDefs failed to update Symantec Endpoint Protection Win64 11.0.2010 (English) failed to update.
The only installation files I have are for 11.0.4000. All my clients are running 11.0.4000 so I'm not sure where the setting to retreive updates for the previous versions is.
Thank you for any help.
Ned
Comments
I'm seeing the same thing here without the error message for MR3 not updating. We are running MR3 on most of our machines, with a few running MR4 and one at MR1. The AV definitions are updating for our MR1 and MR3 machines. It looks like the error messages are issues for install packages that are present on our installation but are not actually used. I haven't had the time to open a call with Symantec yet.
The only installation packages I had were for 32 and 64 bit 11.0.3001 when I upgraded to MR4 on the SEPM server. After SEPM was updated I assigned 10.0.4000 to my groups to update them to the current release and removed the 11.0.3001 packages.
According to Symantec these messages are normal and can be ignored.
So how do I make it stop emailing me error logs for that specific event if this is considered normal? I still want real errors sent to me but this "normal" error should be ignored.
I know, how about SEPM stops producing the alert. That would be a fix.
Did you ever get a fix?
I have the messages too. Did you ever find a way to fix it?
I'm reading your comments and I see that SEPM MR4 has the same problems that MR3.
I upgraded from MR2 to MR3 and I have a lot of machines with the signatures out of date.
I tried to update groups with the new packages but it doesn't work. I tried a lot of things but no one works.
I had to upgrade everyone of my machines with the SEPM Migrating and Implementating tool, and waste a lot a lot of time
If MR4 has the same BIG problems than earlier versions, I think that I can trust in SEPM new versions.
That sounds like a different problem. All my clients upgraded successfully and receive signature updates from the SEPM server fine, however the server reports that versions that don't exist in my installation have signatures that are out of date and are unable to update. These server errors are sent as email alerts along with legitimate alerts, so fixing this problem would be nice.
To update my clients, I just applied the 11.0.4000.2295 installation to each of the groups without specifying a installation time and the clients received the installation notification over the next day or so.
Would you like to reply?
Login or Register to post your comment.