• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 11769
  • Last Modified:

McAfee VirusScan Enterprise 8 is not updating

We currently have about 25 desktops running McAfee VirusScan Enterprise v8. I noticed that after 2/12/09 the AutoUpdate is not updating. This is affecting all computers. We aren't running ePO. All installations are not managed. They are stand alone. See attached.

Any Ideas?

MC-AV-no-ud.jpg
0
PeretzSternACC
Asked:
PeretzSternACC
  • 6
  • 5
  • 5
  • +8
1 Solution
 
chemaoCommented:
If you manually select "Update", does the update fail or succeed? Have you tried modifying the schedule to the current time to see what is actually happening when the update takes place? Please advise
0
 
PeretzSternACCAuthor Commented:
Nothing changes. It still doesn't update.

Thanks,
MC-AV-no-ud2.jpg
0
 
chemaoCommented:
ATTENTION: I am going to recreate this Experts Exchange account with the name Justin_Chandler instead of my nickname "chemao". I will post again on this and you can apply points to that account, please. Thanks!
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Justin_W_ChandlerCommented:
The odd thing is that by looking at that screenshot it gives the impression that the update was successful. Has rebooting the machine helped at all? Also, go into the DAT folder for your Mcafee installation and delete all the update files then try to run the update again.
0
 
MesthaCommented:
Download the latest superDAT from McAfee's web site and run that on the machine. that will usually correct the updating engine.

-M
0
 
PeretzSternACCAuthor Commented:
I tried both suggestions. Nothing changed.

Thanks,
0
 
Justin_W_ChandlerCommented:
When you installed the SuperDAT did it actually change to the newest version? Also, try running the update while logged in as Administrator (Just to ensure no permissions issues)
0
 
PeretzSternACCAuthor Commented:
I updated the AV sDat, the update engine is still not updating. I'm running this under Administrator's rights.

Thanks,
0
 
ViruScanCommented:
Hello,
My suggestion is remove the Mcafee AV and re-install it. It might be a modification in the registry that got screwed.
Txs
0
 
PeretzSternACCAuthor Commented:
Hi,

Something must have changed on McAfee's side. I have over 25 desktops. All of them updated on 2/12; since then, none have.

Thanks,
0
 
ViruScanCommented:
Probably, that's why i suggested to remove it, and re-install it from scratch. Try first with 1 station of course.
It might be that the latest update changed sth in the registry.
0
 
warbringerCommented:
Just FYI ... I use McAfee Virus Scan 8.0 as well on 15 of my customers.  All 15 have not updated since 2/12/09 as well.  I think McAfee may have decided that 8.0 is now "too old".   I dont know, but I am having the same problem.
0
 
MesthaCommented:
According to this page it is EOL at the end of the year.
http://www.mcafee.com/us/products/mcafee/end_of_life.htm

I think a call to McAfee is required.

-M
0
 
ViruScanCommented:
Followinf the link that Mestha displayed, your current engine is still supported. it's the previous version (5200) that isn't supported anymore as of January 09.
I'd recommend you call McAfee and get the required help directly from them. They might have a patch to your problem.
Txs
0
 
PeretzSternACCAuthor Commented:
ViruScan - I installed the VSE onto a brand new machine. It still didn't upload. I think that Mestha" may be correct. I think the product is being dropped. it's not clear when the engine (5300) will stop on being supported. I guess the only option now is to work on a script which will update the AV until we decide if we should upgrade or move to Symantec.

Thoughts?
0
 
MesthaCommented:
It doesn't go end of life until the end of the year. McAfee should give plenty of warning if the product was going end of life and it wouldn't happen in the middle of the month.

I wouldn't go to Symantec though. Bloatware that is more expensive than anything else and for me at least, provides more problems than any other, out of proportion to the number of systems I work on.

-M
0
 
legalsrlCommented:
Did anyone try updating VSE manually ?

I know on the 19th, they released a 62MB update which caused a few problems as the updates are normally only 300K

Is there anything in the Event Viewer or in the logs to show any problems ?

Cheers
Si
0
 
ShinyDocCommented:
I think you will find what you are looking for here https://kc.mcafee.com/corporate/index?page=content&id=KB60060&actp=search&searchid=1235403639507

Not the best news though I'm afraid.

Cheers
0
 
PeretzSternACCAuthor Commented:
ShinyDoc - I'm unclear... I don't see my product listed. Am I missing something?
0
 
ViruScanCommented:
We're unclear as well as why you don't call Mcafee and try to find out what's going on...
Don't forget to keep us updated ...
Txs
0
 
ShinyDocCommented:
Basically, you need to update to VSE 8.5 and the problem will go away. I have confirmed this myself. This essentially upgrades the CMA to the 3.6.x version that is not EOL, like the 3.5.x version that is giving the autoupdate problems.

You can do the workarounds for the interim, but ultimately you are only delaying the inevitable in that McAfee want to move on from supporting a 5year old product. If you want to be downloading and deploying 120MB SDAT files everyday, then this really is a false economy in my opinion, compared with the cost of upgrade.
0
 
legalsrlCommented:
Why not just upgrade the CMA from 3.5 to 3.6 ?

You can download the CMA from the McAfee site, you just need a valid grant number to login ?
0
 
ShinyDocCommented:
I haven't tried that myself, but you can do this at https://secure.nai.com/apps/downloads/my_products/login.asp?region=us&segment=medium with your Grant Number. It says only Patch 4 is supported on CMA 3.6.0.

I still think you are delaying the inevitable, particularly with VSE 8.7iRC now available!
0
 
ShinyDocCommented:
Sorry, also http://www.mcafee.com/us/enterprise/support/customer_service/end_life.html says that VSE8.0i is officially EOL as from December 31, 2009, so plan that upgrade now so you won't be in the same boat again.
0
 
BetaPictorisCommented:
I've experienced the exact same problem with several computers except mine all stopped updating on Feb 2, 2009. Here are my findings:

-Autoupdate continues to run at the scheduled time, except no updates are downloaded See log clipping - note how Feb 2 shows more entries than Feb 3 or Feb 4
-I successfully applied a Feb 17 SuperDAT, but Autoupdate still failed to update virus signatures past that day (Feb 17).
-I tried Control Panel -> Add/Remove Programs -> McAfeeVirusscan -> Change -> Repair, but that also failed to fix the problem.
-I successfully applied service pack 16 for Virusscan 8.0i but that didn't fix it either
-I tried completely uninstalling and reinstalling 8.0i and that fixed the problem. Autoupdate now functions correctly. ...This leads me to believe that the software was not disabled because it reached the end of its "product life", but rather it got damaged somehow. I supected malicious code (virus, trojan, etc) but haven't been able to find anything.

I've been installing Virusscan 8.7i on all the affected computers, but it doesn't tell me why 8.0 failed and that leaves me feeling a little uncomfortable.

2/2/2009	5:05:03 PM	NT AUTHORITY\SYSTEM	Starting VirusScan task: AutoUpdate
2/2/2009	5:05:04 PM	NT AUTHORITY\SYSTEM	Checking update packages from repository NAIHttp.
2/2/2009	5:05:04 PM	NT AUTHORITY\SYSTEM	Initializing update...
2/2/2009	5:05:04 PM	NT AUTHORITY\SYSTEM	Downloading catalog.z.
2/2/2009	5:05:04 PM	NT AUTHORITY\SYSTEM	Verifying catalog.z.
2/2/2009	5:05:04 PM	NT AUTHORITY\SYSTEM	Extracting catalog.z.
2/2/2009	5:05:04 PM	NT AUTHORITY\SYSTEM	Loading update configuration from: Catalog.xml
2/2/2009	5:05:05 PM	NT AUTHORITY\SYSTEM	Verifying datdet.mcs.
2/2/2009	5:05:06 PM	NT AUTHORITY\SYSTEM	Searching available updates for DATs.
2/2/2009	5:05:09 PM	NT AUTHORITY\SYSTEM	Downloading PkgCatalog.z.
2/2/2009	5:05:09 PM	NT AUTHORITY\SYSTEM	Verifying PkgCatalog.z.
2/2/2009	5:05:09 PM	NT AUTHORITY\SYSTEM	Extracting PkgCatalog.z.
2/2/2009	5:05:09 PM	NT AUTHORITY\SYSTEM	Loading update configuration from: PkgCatalog.xml
2/2/2009	5:05:11 PM	NT AUTHORITY\SYSTEM	Starting DAT update.
2/2/2009	5:05:11 PM	NT AUTHORITY\SYSTEM	Verifying delta.ini.
2/2/2009	5:05:11 PM	NT AUTHORITY\SYSTEM	Downloading delta.ini.
2/2/2009	5:05:11 PM	NT AUTHORITY\SYSTEM	Verifying 55135514.upd.
2/2/2009	5:05:11 PM	NT AUTHORITY\SYSTEM	Downloading 55135514.upd.
2/2/2009	5:05:12 PM	NT AUTHORITY\SYSTEM	Backing up file(s) SCAN.DAT, NAMES.DAT, CLEAN.DAT
2/2/2009	5:06:12 PM	NT AUTHORITY\SYSTEM	Pre-notifying for DAT update.
2/2/2009	5:06:12 PM	NT AUTHORITY\SYSTEM	Copying SCAN.DAT, NAMES.DAT, CLEAN.DAT.
2/2/2009	5:06:13 PM	NT AUTHORITY\SYSTEM	Post-notifying for DAT update.
2/2/2009	5:06:20 PM	NT AUTHORITY\SYSTEM	Update succeeded to version 4.0.5514.
2/2/2009	5:06:20 PM	NT AUTHORITY\SYSTEM	Verifying EngDet.mcs.
2/2/2009	5:06:21 PM	NT AUTHORITY\SYSTEM	Searching available updates for Engine.
2/2/2009	5:06:24 PM	NT AUTHORITY\SYSTEM	Product(s) running the latest Engine.
2/2/2009	5:06:24 PM	NT AUTHORITY\SYSTEM	Verifying VSE850Det.McS.
2/2/2009	5:06:24 PM	NT AUTHORITY\SYSTEM	Verifying VSE870Det.McS.
2/2/2009	5:06:24 PM	NT AUTHORITY\SYSTEM	Verifying EceptCntDet.mcs.
2/2/2009	5:06:25 PM	NT AUTHORITY\SYSTEM	Verifying AUEngineContentDetection.McS.
2/2/2009	5:06:25 PM	NT AUTHORITY\SYSTEM	Verifying MPEMSBCKDet.McS.
2/2/2009	5:06:26 PM	NT AUTHORITY\SYSTEM	Verifying MPEPRDCKDet.McS.
2/2/2009	5:06:26 PM	NT AUTHORITY\SYSTEM	Verifying MPESVRUPDet.McS.
2/2/2009	5:06:26 PM	NT AUTHORITY\SYSTEM	Verifying MPEVIRCKDet.McS.
2/2/2009	5:06:26 PM	NT AUTHORITY\SYSTEM	Verifying PatchTmpDet.McS.
2/2/2009	5:06:26 PM	NT AUTHORITY\SYSTEM	Verifying PatchTmpDet.McS.
2/2/2009	5:06:26 PM	NT AUTHORITY\SYSTEM	Verifying PUPDet.mcs.
2/2/2009	5:06:27 PM	NT AUTHORITY\SYSTEM	Verifying SK_det.mcs.
2/2/2009	5:06:27 PM	NT AUTHORITY\SYSTEM	Downloading SK_det.mcs.
2/2/2009	5:06:28 PM	NT AUTHORITY\SYSTEM	File SK_det.mcs is corrupt. Downloading complete file again.
2/2/2009	5:06:33 PM	NT AUTHORITY\SYSTEM	Update Finished
2/2/2009	5:06:33 PM	NT AUTHORITY\SYSTEM	Closing the update session.
2/3/2009	5:16:03 PM	NT AUTHORITY\SYSTEM	Starting VirusScan task: AutoUpdate
2/3/2009	5:16:03 PM	NT AUTHORITY\SYSTEM	Checking update packages from repository NAIHttp.
2/3/2009	5:16:04 PM	NT AUTHORITY\SYSTEM	Initializing update...
2/3/2009	5:16:04 PM	NT AUTHORITY\SYSTEM	Downloading catalog.z.
2/3/2009	5:16:04 PM	NT AUTHORITY\SYSTEM	Verifying catalog.z.
2/3/2009	5:16:04 PM	NT AUTHORITY\SYSTEM	Extracting catalog.z.
2/3/2009	5:16:04 PM	NT AUTHORITY\SYSTEM	Loading update configuration from: Catalog.xml
2/3/2009	5:16:05 PM	NT AUTHORITY\SYSTEM	Update Finished
2/3/2009	5:16:05 PM	NT AUTHORITY\SYSTEM	Closing the update session.
2/4/2009	5:21:03 PM	NT AUTHORITY\SYSTEM	Starting VirusScan task: AutoUpdate
2/4/2009	5:21:04 PM	NT AUTHORITY\SYSTEM	Checking update packages from repository NAIHttp.
2/4/2009	5:21:04 PM	NT AUTHORITY\SYSTEM	Initializing update...
2/4/2009	5:21:04 PM	NT AUTHORITY\SYSTEM	Downloading catalog.z.
2/4/2009	5:21:04 PM	NT AUTHORITY\SYSTEM	Verifying catalog.z.
2/4/2009	5:21:04 PM	NT AUTHORITY\SYSTEM	Extracting catalog.z.
2/4/2009	5:21:04 PM	NT AUTHORITY\SYSTEM	Loading update configuration from: Catalog.xml
2/4/2009	5:21:05 PM	NT AUTHORITY\SYSTEM	Update Finished
2/4/2009	5:21:05 PM	NT AUTHORITY\SYSTEM	Closing the update session.

Open in new window

0
 
ShinyDocCommented:
You might start by actually reading some of the above links as they clearly explain the problem, particularly https://kc.mcafee.com/corporate/index?page=content&id=KB60060&actp=search&searchid=1235403639507

This should not have been a shock and McAfee did delay this from 23rd November 2008 to allow people to get their installs in order.
0
 
BetaPictorisCommented:
ShinyDoc, you're right.The URL you gave does explain my problem. If this is also the solution to PeretzSternACC's problem, then I think your comment ID#23712387 should be flagged as a solution. Thanks.
0
 
ViruScanCommented:
Hey guys,
It has been more than 10 days that we didn't hear from our friend here. WE gave all kinds of solutions and propositions... but no answer back.
PLease let us know of your status and issue the points to the right answer...
Txs
0
 
catknowsCommented:
Thanks for the info guys.  My system, Windows 2003 Adv server stop updating on 2/2/09 also.  I need to update later version.
0
 
ispartCommented:
Issue will be resolved by upgrading the CMA to 3.6.x.
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 6
  • 5
  • 5
  • +8
Tackle projects and never again get stuck behind a technical roadblock.
Join Now