cancel
Showing results for 
Search instead for 
Did you mean: 

ePO console sees DAT files up to date but virusscan console says something different

When a customer opens the virus scan console on a client, it says that the definitions have not been updated since March. However, when I look in the ePO console for those specific workstations/laptops, it does show the client as having the latest update on our master repository, DAT version 6113.0000.

What could be causing the discrepancy?

PG

4 Replies

Re: ePO console sees DAT files up to date but virusscan console says something different

What version of VirusScan is on the client and what version of ePO are you using?

It sounds like the client has v8.0 on it which went EOL on march 31st as it doesn't support V2 dats.  You will need to upgrade VirusScan on this machine if this is the case to  (preferably) 8.7

HTH

Re: ePO console sees DAT files up to date but virusscan console says something different

The Virus scan version is Enterprise 8.7.0.570. ePO version is 4.0, Build 1333.

Re: ePO console sees DAT files up to date but virusscan console says something different

Have a look at the mscript.log and mscript_error.log files in c:\docssettings\allusers\application data\mcafee\common framework\db\ and see what errors you can find/ post logs.

what happens when you do a manual update?

apoling
Level 14
Report Inappropriate Content
Message 5 of 5

Re: ePO console sees DAT files up to date but virusscan console says something different

Hello,

when you open the http://localhost:8081 on the client and look for messages regarding agent-server contact, do you see any error message, like "Failed to connect to ePO server" ?

Your problem could simply just be this: client is able to update but fails to report new properties to ePO server.

If you don't see such messages and see that agent is able to connect, then you could simultaneously view server.log on the ePO server and agent_computername.log on the client after you did a manual update on the client (or waited the managed update task to run) and then initiate an agent wakeup call (or wait the ASCI to happen), and then look for messages in server.log regarding any failures for his client.

Attila