4 Replies Latest reply on Apr 5, 2017 4:54 AM by Richard Carpenter

    After Endpoint Security 10.2 installs, most Win7 and Win8.1 DAT updates fail using ePo Cloud

    tong@hwiarchitects.com

      After the recent 8/11/2016 Endpoint Security 10.2 installs from ePo Cloud, about 75% of our office computers (about 30 Win7 and Win8.1) are failing to auto-update DAT files (only win10 and three win7/8.1 are updating) .  I've already got a ticket in with Mcafee but their tier 2 support who was supposed to call me still hasn't called me with any solutions.  Nothing has changed on our clients, servers nor network.  On Mcafee Agent Monitor, the DAT auto-updates end with the error:

       

           - The task Initial Deployment Update My Group 11 (5) has failed.

           - Unable to find a valid repository

           - Update Finished

           - Updated failed to version 23xx.0

           - Error occurred while downloading C:\ProgramData\McAfee\Agent\\Current\AMCORDAT2000\DAT\0000\PkgCatalog.z

       

      Anyone else getting DAT update failures?  Any help would be appreciated.

       

       

      -W

        • 1. Re: After Endpoint Security 10.2 installs, most Win7 and Win8.1 DAT updates fail using ePo Cloud
          woody188

          I'm seeing this too but with locally hosted ePO:

           

          2/15/2017 12:36:38 PM   mfeesp(2668.37076) <SYSTEM> PackageManager.PackageManager.Activity: Starting Update Task : Default Update Task

          2/15/2017 12:36:41 PM   mfeesp(2668.3212) <SYSTEM> PackageManager.PackageManager.Activity: Update in Progress

          2/15/2017 12:36:41 PM   mfeesp(2668.5080) <SYSTEM> PackageManager.PackageManager.Activity: Please wait for update to finish...

          2/15/2017 12:37:02 PM   mfeesp(2668.3216) <SYSTEM> PackageManager.PackageManager.Activity: Checking update packages from repository ePO_QW9EPOAH1VM.

          2/15/2017 12:37:02 PM   mfeesp(2668.3216) <SYSTEM> PackageManager.PackageManager.Activity: Initializing update...

          2/15/2017 12:37:02 PM   mfeesp(2668.3212) <SYSTEM> PackageManager.PackageManager.Activity: Verifying catalog.z.

          2/15/2017 12:37:02 PM   mfeesp(2668.5080) <SYSTEM> PackageManager.PackageManager.Activity: Extracting catalog.z.

          2/15/2017 12:37:02 PM   mfeesp(2668.3216) <SYSTEM> PackageManager.PackageManager.Activity: Loading update configuration from: catalog.xml

          2/15/2017 12:37:03 PM   mfeesp(2668.4200) <SYSTEM> PackageManager.PackageManager.Activity: These updates will be applied if they are in the repository:  AMCORDAT2000, ENDPCNT_1000, EXTRADAT1000, JTICLIENTMETA.

          2/15/2017 12:37:03 PM   mfeesp(2668.3216) <SYSTEM> PackageManager.PackageManager.Activity: Verifying amcore.mcs.

          2/15/2017 12:37:03 PM   mfeesp(2668.3216) <SYSTEM> PackageManager.PackageManager.Activity: Downloading PkgCatalog.z.

          2/15/2017 12:37:06 PM   mfeesp(2668.3216) <SYSTEM> PackageManager.PackageManager.Activity: Verifying PkgCatalog.z.

          2/15/2017 12:37:06 PM   mfeesp(2668.4200) <SYSTEM> PackageManager.PackageManager.Activity: Extracting PkgCatalog.z.

          2/15/2017 12:37:06 PM   mfeesp(2668.3212) <SYSTEM> PackageManager.PackageManager.Activity: Loading update configuration from: PkgCatalog.xml

          2/15/2017 12:37:07 PM   mfeesp(2668.5080) <SYSTEM> PackageManager.PackageManager.Activity: Downloading amupdate.dll.

          2/15/2017 12:37:09 PM   mfeesp(2668.5080) <SYSTEM> PackageManager.PackageManager.Activity: Error occurred while downloading C:\ProgramData\McAfee\Common Framework\\Current\AMCORDAT2000\DAT\0000\PkgCatalog.z.

          2/15/2017 12:37:09 PM   mfeesp(2668.5080) <SYSTEM> PackageManager.PackageManager.Activity: Update failed to version 2890.0.

          2/15/2017 12:37:29 PM   mfeesp(2668.4200) <SYSTEM> PackageManager.PackageManager.Activity: There were errors during the update, please check the error log for details.

           

          Odd because it can contact ePO as Agent checks in and there is the most recent update in the ePO master repository. Updated to a newer Agent 5.0.4.283 and still no joy getting this 10.2 package to download and install.

           

          Check in the Event Viewer and I'm getting this the same time as the update bombs:

          Process **\macompatsvc.exe pid (2802) contained unsigned or corrupted code and was blocked from performing a privileged operation with a McAfee driver.

          Process **\McScript_InUse.exe pid (1080) contained unsigned or corrupted code and was blocked from performing a privileged operation with a McAfee driver.

           

          Seems to be occurring on all our workstations in our test group. Have about 140 instances installed evaluating for the other 6500 endpoints still on VSE.

          • 2. Re: After Endpoint Security 10.2 installs, most Win7 and Win8.1 DAT updates fail using ePo Cloud
            woody188

            Can a moderator please move this to Endpoint discussion area?

            • 3. Re: After Endpoint Security 10.2 installs, most Win7 and Win8.1 DAT updates fail using ePo Cloud
              woody188

              I was able to fix this by disabling AMCore Content Reputation in the ePO Policy Catalog.

               

              ePOPolicyCatOptionsDefault.png

              Works fine after Agent pulls the new policy. Default is set to Check.

              1 of 1 people found this helpful
              • 4. Re: After Endpoint Security 10.2 installs, most Win7 and Win8.1 DAT updates fail using ePo Cloud
                Richard Carpenter

                Moved to Endpoint Security for more assistance.

                 

                Rich

                McAfee Volunteer Moderator - Business Products