0 Replies Latest reply on Apr 30, 2009 4:30 AM by ScottGTO

    Engine Update Problems

      Ok folks, I'm hoping you can help me out here as I'm getting close to my wits end..

      Environment is ePO Server 4 Patch 4, McAfee Agent 4 Patch 2 and VSE 8.5i Patch 8 with the anti-spyware module. There is one ePO server and two remote repositories, each on different sites.

      The master repo. and remote repos. are synchronised and up to date, however, only the devices reporting into the master repo. were able to update their engine from 5300.2777 to 5301.4018. Any clients using the remote repositories weren't able to do so. A snippet from the log shows:

      2009-04-30 08:52:11 i #800 Updater Loading update configuration from: PkgCatalog.xml
      2009-04-30 08:52:11 I #800 Uec Done processing progress information
      2009-04-30 08:52:12 I #800 Uec Received ipc data from mue
      2009-04-30 08:52:12 I #800 Uec Processing progress information
      2009-04-30 08:52:12 i #800 Updater Verifying V2engdet.mcs.
      2009-04-30 08:52:12 I #800 Uec Done processing progress information
      2009-04-30 08:52:12 I #800 Uec Received ipc data from mue
      2009-04-30 08:52:12 I #800 Uec Processing progress information
      2009-04-30 08:52:12 i #800 Updater Downloading V2engdet.mcs.
      2009-04-30 08:52:12 I #800 Uec Done processing progress information
      2009-04-30 08:52:15 I #800 Uec Received ipc data from mue
      2009-04-30 08:52:15 I #800 Uec Processing progress information
      2009-04-30 08:52:15 i #800 Updater Error occurred while downloading C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Current\VSCANENG1000\PkgCatalog.z.

      followed by

      2009-04-30 08:53:00 i #800 Updater Updates were not applied because packages were not in the repository: Engine.

      Now I've tried to completely remove and recreate the remote repos but it had no effect. The same error occurs on both sites using the remote repositories. I have noticed the following though:

      - If I change the policy to force one of the problem clients to use the master repository then the engine update works fine.

      - If I rename or remove the VSCANENG1000 folder on the local client (C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Current\) and force an update then the engine updates fine from the remote repository.

      I could (reasonably) quickly create a script to rename/remove the VSCANENG1000 folder on my clients but I was hoping for a more elegant solution..

      All of my policies look to be ok. You can view the packages in the remote repositories and they also look to be ok.. Also, DAT, hotfixes etc all work fine from all of the repositories. It just appears to be the engine updates. Have you seen something like this before?

      Any advice you could offer would be greatly appreciated!

      S.