cancel
Showing results for 
Search instead for 
Did you mean: 

Re: VSE 8.8 update fail - reason unknown

Jump to solution

tao, good idea! As I'm investigating the effect with single machine, I tried to re-install actual VSE using Your parameters just from installer forder. After reinstall the update process still hangs, but closer to finish than previously. The corresponding log messages, which I found are in my previous reply to chealey

vse_inst_07.png

Reliable Contributor tao
Reliable Contributor
Report Inappropriate Content
Message 12 of 24

Re: VSE 8.8 update fail - reason unknown

Jump to solution

Couple of options:  perform an uninstall - yea, I know sounds wacky - but if there was any corruption or failed registry entries in the orginial install then the reinstall may have corrected the corruption and missing registry entries.  So, start from scratch - after successfully uninstall / then proceed with a fresh insall . 

OR

Since the updater is part of the agent - toggle on verbose/debug logging for McAfee Agent 5.x for Windows:
https://kc.mcafee.com/corporate/index?page=content&id=KB82170

 

If this information was helpful or has answered your question, please select Accept as Solution. This will assist other memebers
nashcoop
Level 10
Report Inappropriate Content
Message 13 of 24

Re: VSE 8.8 update fail - reason unknown

Jump to solution

I would love to hear if this problem gets fixed since I am having a similar issue with an Exchange Server.  The server stopped updating VScan DAT files.  I couldn't get it to update when initiating an update task from EPO 5.9.1, and when I logged into the server locally and chose the Update Security or Update Now options nothing happened.  Literally, nothing happened. The "Update Now" button doesn't even press down when I move my mouse arrow over it and click on it.  I have updated the McAfee agent from 5.5.1.388 to 5.6.0.702.  I have tried removing the VirusScan 8.8 Patch 11 installation and installing VirusScan 8.8 Patch 12.  I have tried removing and reinstalling the McAfee Agent and VScan, running MCPR, and reinstalling them after rebooting the server.  The update function still doesn't work.  Everything else about the agent and VScan functionality appear to work fine.  I've spent a lot of time installing, uninstalling, rebooting, running MCPR, wash, rinse, do it again.  I had a few other servers with the same update issue, all Exchange, Lync, or Sharepoint related.  There is not a network communication problem, it is a functionality problem since the update options don't initiate.

updatenow2.jpgupdatenow1.jpg

Re: VSE 8.8 update fail - reason unknown

Jump to solution

tao, I already tried the 'total uninstall (with MPR utility) - install' method previously. Do You mean I should try the multiple uninstall-install approaches in sequence?

And let me remind: the VSE is not able to update without ePO/Agent also, possibly, the issue is outside Enterprise monitoring (ePO) stack.

Now I set the agent log level = 2 and left the system till Monday.

chealey, sorry, I also don't see any of 2 my reports to You. Let me try again.

I'm not able to found the script start couple of messages, instead, I found something, which correlates  with 'infinite update hang' in McScript.log file:

 

Spoiler

2019-02-04 18:23:42 I #12912 ScrptExe Executing section: [SetFileFound]
2019-02-04 18:23:42 I #12912 ScrptExe Executing section: [VerifyFile]
2019-02-04 18:23:42 I #12912 ScrptMgr Downloading DATRepHC.zip.
2019-02-04 18:23:42 I #12912 p2p_client Checking content via discovery... for hash(D8AF2E39BE0B6F4F5A9434812256FBECA48E3D97)
2019-02-04 18:23:44 I #12912 downloader calling system proxy client api.
2019-02-04 18:23:49 I #12912 downloader Using system configured proxy for connection.
2019-02-04 18:23:49 I #12912 downloader Downloading file from https://10.20.128.193:443/Software/Current/VSCANDAT1000/DAT/0000/DATRepHC.zip?hash=D8AF2E39BE0B6F4F5... to C:\Program Files (x86)\Common Files\McAfee\DATReputation\DATRepHC.zip
2019-02-04 18:23:49 I #12912 curl Setting proxy info proxy:10.20.130.101 port:3128 scope:0
2019-02-04 18:23:49 I #12912 crypto Negotiated Cipher : EDH-RSA-AES256-SHA256
2019-02-04 18:23:49 I #12912 downloader Downloading file from https://10.20.128.193:443/Software/Current/VSCANDAT1000/DAT/0000/DATRepHC.zip?hash=D8AF2E39BE0B6F4F5... to C:\Program Files (x86)\Common Files\McAfee\DATReputation\DATRepHC.zip success.
2019-02-04 18:23:49 I #12912 downloader changing permission...
2019-02-04 18:23:49 I #12912 policybag Sending content "add" request
2019-02-04 18:23:49 I #12912 policybag Content "add" request succeded.
2019-02-04 18:23:49 I #12912 ScrptExe Executing section: [ExtractFile]
2019-02-04 18:23:49 I #12912 ScrptMgr Setting the working dir as C:\Program Files (x86)\Common Files\McAfee\DATReputation
2019-02-04 18:23:49 I #12912 ScrptMgr Setting the working dir as C:\ProgramData\McAfee\Agent\\Current\VSCANDAT1000
2019-02-04 18:23:49 I #12912 ScrptExe Executing section: [SetThrottleAndNeutral]
2019-02-04 18:23:49 I #12912 ScrptExe Running "C:\Program Files (x86)\Common Files\McAfee\DATReputation\mcdatrep.exe" /setdatrepneutralu=1 /setdatrephcneutralu=0 /setdatrepneutralm=1 /setdatrephcneutralm=0
2019-02-04 18:23:49 I #12912 ScrptExe Running "C:\Program Files (x86)\Common Files\McAfee\DATReputation\mcdatrep.exe" /setdatrepneutralu=1 /setdatrephcneutralu=0 /setdatrepneutralm=1 /setdatrephcneutralm=0
2019-02-04 18:23:49 I #12912 ScrptExe Did not match searched path
2019-02-04 18:23:49 I #12912 ScrptExe Executing "C:\Program Files (x86)\Common Files\McAfee\DATReputation\mcdatrep.exe" /setdatrepneutralu=1 /setdatrephcneutralu=0 /setdatrepneutralm=1 /setdatrephcneutralm=0
2019-02-04 18:23:49 I #12912 ScrptExe Using Aac exclusion path C:\Program Files (x86)\Common Files\McAfee\DATReputation\mcdatrep.exe
2019-02-04 18:24:27 I #12912 ScrptExe Running "C:\Program Files (x86)\Common Files\McAfee\DATReputation\mcdatrep.exe" /throttlehealthcheck=1000000
2019-02-04 18:24:27 I #12912 ScrptExe Running "C:\Program Files (x86)\Common Files\McAfee\DATReputation\mcdatrep.exe" /throttlehealthcheck=1000000
2019-02-04 18:24:27 I #12912 ScrptExe Did not match searched path
2019-02-04 18:24:27 I #12912 ScrptExe Executing "C:\Program Files (x86)\Common Files\McAfee\DATReputation\mcdatrep.exe" /throttlehealthcheck=1000000
2019-02-04 18:24:27 I #12912 ScrptExe Using Aac exclusion path C:\Program Files (x86)\Common Files\McAfee\DATReputation\mcdatrep.exe
2019-02-04 18:25:05 I #12912 ScrptExe Executing section: [IsDATBlocked]
2019-02-04 18:25:05 I #12912 ScrptExe Running "C:\Program Files (x86)\Common Files\McAfee\DATReputation\mcdatrep.exe" /timeout=60000 /datreputation=9156.0000
2019-02-04 18:25:05 I #12912 ScrptExe Running "C:\Program Files (x86)\Common Files\McAfee\DATReputation\mcdatrep.exe" /timeout=60000 /datreputation=9156.0000
2019-02-04 18:25:05 I #12912 ScrptExe Did not match searched path
2019-02-04 18:25:05 I #12912 ScrptExe Executing "C:\Program Files (x86)\Common Files\McAfee\DATReputation\mcdatrep.exe" /timeout=60000 /datreputation=9156.0000
2019-02-04 18:25:05 I #12912 ScrptExe Using Aac exclusion path C:\Program Files (x86)\Common Files\McAfee\DATReputation\mcdatrep.exe
2019-02-04 18:26:32 I #12912 ScrptExe Executing section: [GotMinEng]
2019-02-04 18:26:32 I #12912 ScrptExe Executing section: [EnumerateThroughProducts]
2019-02-04 18:26:32 I #12912 ScrptExe Executing section: [GetNextProductID]
2019-02-04 18:26:32 I #12912 ScrptExe Executing section: [DoesProductNeedUpdate]
2019-02-04 18:26:32 I #12912 ScrptExe Executing section: [SetInstalledVersionsUsingRegistry]
2019-02-04 18:26:32 I #12912 ScrptExe Executing section: [IsProductInstalledReg]
2019-02-04 18:26:32 I #12912 ScrptExe Executing section: [EnumerateThroughProducts]
2019-02-04 18:26:32 I #12912 ScrptExe Executing section: [GetNextProductID]
2019-02-04 18:26:32 I #12912 ScrptExe Executing section: [DoesProductNeedUpdate]

... and so on ....

 

 

nashcoop
Level 10
Report Inappropriate Content
Message 15 of 24

Re: VSE 8.8 update fail - reason unknown

Jump to solution

I had a similar issue with an Exchange server, but managed to finally fix it today.  After removing and reinstalling McAfee agent 5.6.0.702, and VScan with Patch 12 (and running MCPR each time) multiple times without fixing the update issue I decided to try installing an older version of VScan.  I had been installing the McAfee agent first, then VScan.  This time I installed VScan with Patch 9, then ran an update which successfully grabbed the DAT from McAfee.  Then I installed the 5.5.1.388 agent, and ran another update which then grabbed tasks & policies from our EPO server and updated to patch 12.

Highlighted
McAfee Employee chealey
McAfee Employee
Report Inappropriate Content
Message 16 of 24

Re: VSE 8.8 update fail - reason unknown

Jump to solution

At this point I would suggest gathering MA debug logs via our MER tool and opening a case with our McAfee Agent team. They will be able to look through the logs in their entirety and help identify the cause of the issue.

If re-installing doesn't help, this does again indicate a network issue or a dll injection type issue.

Was my reply helpful?
If this information was helpful in any way, or answered your question, will you please select "Accept as Solution" in my reply, or give kudos as appropriate, so together we can help other members?

Re: VSE 8.8 update fail - reason unknown

Jump to solution

OK, here is a list with a lot of results:

- At Monday we noticed the DAT file is actual and it was updated during scheduled session successfully; Great! We left the system without additional manipulations to keep watching it;

- At Tuesday and Wednesday the DAT file update was unsuccessfull, it remained at Monday revision;

- Today we tried to implement nashcoop plan. Removed both VSE and Agent - run MCPR - installed the 5.06 Agent - installed VSE 8.8 U6 (the U9 is not available at Downloads section). Result: Agent is not able to contact ePO at all, thus, the policy and updates are not possible;

- Tried to replace the Agent with version 5.60 via update. Result is the same: no interaction with ePO server;

- Tried to remove both VSE and Agent - run MCPR - installed the 5.60 Agent - installed VSE 8.8 U6 . Result: still, Agent is not able to contact ePO at all;

- Tried to remove both VSE and Agent - run MCPR - installed the 5.60 Agent. Result: Agent is not able to contact ePO;

The firewall rules not changed and visually, seems OK (allowing rules are present and active). The Agent logs, seems, have no problems (at the spoiler).

- Now we added the VSE 8.8 U6 and left the system till Friday or Monday. If nothing will change, which point you would suggest as base to initiate the service request: "Agent 5.5 + VSE 8.8 U12" (our production set) or "Agent 5.0.6 + VSE 8.8 U6" (which might to operate with higher possibility)?

Spoiler
2019-02-14 14:09:39.654 masvc(10864.10832) protected_aac_ctl.Info: starting protected_aac_ctl worker thread...
2019-02-14 14:09:39.654 masvc(10864.10832) protected_aac_ctl.Info: Attempting to create child process using cmdline: <"C:\Program Files\McAfee\Agent\x86\\mfemactl.exe" --log "C:\ProgramData\McAfee\Agent\logs" --ppid 10864 --interface 4D454F57010000000000000000000000C0000000000000460000000005000000D57397CBA85B266340177EB0C4F8148E022C0000702A502A5F9070768D2D80CD00000000 >...
2019-02-14 14:09:39.701 masvc(10864.10832) protected_aac_ctl.Info: Ok, successfully created child process
2019-02-14 14:09:39.716 masvc(10864.10832) protected_aac_ctl.Info: In RegisterProtectedAacCtl
2019-02-14 14:09:39.716 masvc(10864.10868) protected_aac_ctl.Info: Worker thread reported successful start
2019-02-14 14:09:39.716 masvc(10864.10832) protected_aac_ctl.Info: ProcessThreadMessage invoking VALIDATE_VTP
2019-02-14 14:09:39.716 masvc(10864.10868) protected_aac_ctl.Info: protected_aac_ctl_validate_vtp completed with status: <0>, result: <0>
2019-02-14 14:09:39.716 masvc(10864.10832) protected_aac_ctl.Info: ProcessThreadMessage invoking (START|STOP)_MONITORING
2019-02-14 14:09:39.732 masvc(10864.10868) protected_aac_ctl.Info: protected_aac_ctl_start_monitoring completed with status: <0>
2019-02-14 14:09:39.732 masvc(10864.10832) protected_aac_ctl.Info: ProcessThreadMessage invoking APPLY_POLICY
2019-02-14 14:09:39.732 masvc(10864.10868) protected_aac_ctl.Info: protected_aac_ctl_apply_policy completed with status: <0>
2019-02-14 14:09:39.732 masvc(10864.10832) protected_aac_ctl.Info: ProcessThreadMessage invoking ENABLE_DISABLE_AAC_GROUP for policy {C7080E42-1D78-4B64-8E32-6D9E032123FE}, ma.selfprotect, -1
2019-02-14 14:09:39.732 masvc(10864.10868) protected_aac_ctl.Info: protected_aac_ctl_enable_group completed with status: <80004002>
2019-02-14 14:09:39.732 masvc(10864.10832) protected_aac_ctl.Info: ProcessThreadMessage invoking ENABLE_DISABLE_AAC_GROUP for policy {2AA87236-7E59-449B-BDE1-D2A6045ED15B}, mfemms, -1
2019-02-14 14:09:39.732 masvc(10864.10868) protected_aac_ctl.Info: protected_aac_ctl_enable_group completed with status: <80004002>
2019-02-14 14:09:39.732 masvc(10864.10832) protected_aac_ctl.Info: ProcessThreadMessage invoking ENABLE_DISABLE_AAC_GROUP for policy {65CF3D67-B283-4477-83C6-181CEFAC7443}, mfemms, -1
2019-02-14 14:09:39.732 masvc(10864.10868) protected_aac_ctl.Info: protected_aac_ctl_enable_group completed with status: <80004002>
2019-02-14 14:10:18.430 masvc(10864.10832) protected_aac_ctl.Info: ProcessThreadMessage invoking APPLY_POLICY
2019-02-14 14:10:18.430 masvc(10864.10868) protected_aac_ctl.Info: protected_aac_ctl_apply_policy completed with status: <0>
2019-02-14 14:10:18.430 masvc(10864.10832) protected_aac_ctl.Info: ProcessThreadMessage invoking ENABLE_DISABLE_AAC_GROUP for policy {578CD062-4EAC-4242-A026-5938D40F45E6}, dxl, -1
2019-02-14 14:10:18.430 masvc(10864.10868) protected_aac_ctl.Info: protected_aac_ctl_enable_group completed with status: <80004002>

 

McAfee Employee akatt
McAfee Employee
Report Inappropriate Content
Message 18 of 24

Re: VSE 8.8 update fail - reason unknown

Jump to solution

Just a thought, but when reinstalling the Agent, how is this being performed?  Locally, or ePO deployment?  If locally, is the Agent package one that was created from the ePO server that we want it to connect to?

I am assuming that the Agent deployment is the correct Agent package, or that it was done via ePO, but just want to make sure we aren't missing an obvious reason for what appears to be an MA communication failure with ePO.  Provided everything above has been verified, and not thought to be part of the problem, the best assistance will come from the support team that reviews ePO/MA issues daily, which is the Enabling Technologies team, and engaging them through a support case may be ideal at this time.


Was my reply helpful?

If this information was helpful in any way, or answered your question, will you please select "Accept as Solution" in my reply, or give kudos as appropriate, so together we can help other members?



Re: VSE 8.8 update fail - reason unknown

Jump to solution

akatt, I made these approaches:

  • Agents 5.06 and 5.60 were downloaded from site and installed locally (run as administrator from copied to local storage file);
  • Agent 5.5 was installed both locally from ePO-prepared package and via ePO agent deployment fuctionality;
  • VSE 8.8 U6 was downloaded from site and installed locally (run as administrator from copied to local storage file);
  • VSE 8.8 U12 was installed both locally from ePO-downloaded package and via ePO product deployment fuctionality;

Ok, I will set the "Agent 5.5 + VSE 8.8 U12 + MER" combination and continue with support team. Upon resolution I will add the update. Thank You!

Re: VSE 8.8 update fail - reason unknown

Jump to solution

The attempt to deploy "Agent 5.5 + VSE 8.8 U12 + MER" group was unsuccessfull after "Agent" deploy: the Agent is visible from ePO, but unable to deploy any software further. MVT (Virtual Technician) says the all required services not started, the standalone MER was used to collect data. Now we have to make 3-weeks pause, so, the SR will be opened in mid-March.

More McAfee Tools to Help You
  • Subscription Service Notification (SNS)
  • How-to: Endpoint Removal Tool
  • Support: Endpoint Security
  • eSupport: Policy Orchestrator
  • Community Help Hub

      New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

    • Find Forum FAQs
    • Learn How to Earn Badges
    • Ask for Help
    Go to Community Help

    Join the Community

      Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

    • Get helpful solutions from McAfee experts.
    • Stay connected to product conversations that matter to you.
    • Participate in product groups led by McAfee employees.
    Join the Community
    Join the Community