1 2 Previous Next 10 Replies Latest reply: May 24, 2008 11:06 PM by isepiq RSS

    McAfee Common Framework error

    texaspete
      Product: VirusScan Enterprise 8.0i
      Engine\DAT: 4400\4686

      A friend has this, and is getting an error when updating

      'ERROR: McAfee Common Framework returned error fffff95b @ 2, Failed to
      initialize common updater subsystem'

      The support site suggests two ways of fixing it in kb44872.

      I need to get a file called FrameworkManifest.xml from another machine
      running VirusScan 8.0i (it's in C:\Documents and Settings\All
      Users\Application Data\Network Associates\Common Framework)

      or I need to download and install the Common Management Agent Patch 5
      Standalone version.

      I have no other machine running VirusScan 8.0i, and I have no way of
      getting the CMA Patch (I have no grant number).

      Can anyone help with either?
        • 1. RE: McAfee Common Framework error
          Solution ID:


          Title:

          kb38938


          ERROR: Failed to Initialize Common Updater Subsystem

          Question or Problem:
          ERROR: Failed to Initialize Common Updater Subsystem
          ERROR: McAfee Common Framework returned error
          ERROR: Make sure the McAfee Framework Service is running
          The above various popup errors are incurred when an AutoUpdate is initiated. The type of error depends on the problem DLL or missing registry key.
          Solution1:

          The fffff?? errors are now resolvable by re-registering DLL's. Please refer to the Master Knowledgebase solution first for the list of known issues and which contains a generic solution.

          KB45362: Master article: ERROR: McAfee Common Framework returned error ffffff?? @ ? / Failed to initialize common updater subsystem
          Solution2:

          Since CMA references both Operating System registry keys and CMA registry keys, one or more of the following methods should be used to correct the issue:

          * Uninstalling and reinstalling all CMA registry keys (see KB43214)
          * Identifying and replacing the registry key (see below)
          * Correcting the permissions for the registry key (see below)

          Solution3:

          The registry key can be replaced by importing it from a correctly-functioning system. To do this, the key must first be exported:

          1. Use the table above to identify which registry key corresponds to the error.
          2. On the correctly-functioning system, select Start, Run, type regedit and click OK.
          3. Find and select the identified registry key.
          4. Select Registry, Export Registry File.
          5. Select a location, type a name for the file, and click Save.
          6. Transport the exported file to the system reporting the error (via floppy disk, CD, thumbdrive, Windows network, etc)
          7. On the system reporting the error, select Start, Run, type regedit and click OK.
          8. Find and select the branch that includes the identified registry key.
          9. Select Registry, Import Registry File.
          10. Navigate to the exported file and click Open.
          11. Click OK.

          Solution4:

          If all systems in the environment are reporting an error, security permissions for the identified registry key must be reset on each system manually:

          1. Use the table below to identify which registry key corresponds to the error.
          2. On the first system reporting the error, select Start, Run, type regedit and click OK.
          3. Find and select the identified registry key.
          4. Select Security, Permissions.
          5. Click Add. The Select Users, Computers, or Groups dialog box is displayed.
          6. Select System and click Add.
          7. Select Interactive and click Add.
          8. Select Administrators and click Add.
          9. Click OK to close the dialog box.
          10. Select System and under Allow, select Full Control.
          11. Select Interactive and under Allow, select Full Control.
          12. Select Administrator and under Allow, select Full Control.
          13. Check the box next to Allow inheritable permissions from parent to propagate to this object.
          14. Click Apply and OK.
          15. Restart the system.
          NOTE: The changes will not take effect until the system is restarted.
          16. Repeat all steps for the next system reporting the error.

          Notes:


          Upgrade the Common Management Agent component:

          1. Download the most current version or patch of the CMA. The name of the patch will be similar to ePolicy Orchestrator 3.x Common Management Agent Patch x, where x is the most current version. Since CMA development is cumulative, its patch and version numbers are not tied to the versions of ePO 3.x server. Only the most current version of the CMA is available for download.
          (See KB40531 - Downloading Patches for more information.)
          2. Add the CMA package to the ePO repository.
          (See the Readme.txt for instructions or see to NAI36718 - Check in new agent to the ePolicy Orchestrator master repository.)
          3. Use the Deployment task to deploy the new CMA.
          (See Using ePolicy Orchestrator to deploy the agent in the ePO 3.5 Product Guide at:
          https://mysupport.nai.com/redir/default.asp?pCode=epo&sRef=app&sDest=Docs)


          Environment:


          McAfee Common Management Agent 3.x
          McAfee ePolicy Orchestrator 3.x.x
          McAfee VirusScan Enterprise
          Microsoft Windows

          Cause of Problem:


          The Common Management Agent (CMA) could not read a registry key during an update. Registry permissions may have prevented certain entries from being made during installation or upgrade of VirusScan Enterprise (VSE).

          Certain registry keys are referenced during the update process. If those keys were not installed, or were altered by another application, the update process will fail. Most likely reasons are:

          * Registry key security permissions
          * Deleted or corrupted registry keys

          The table below lists the error codes which correspond to specific registry keys:

          Error
          Registry Key

          80040154@1


          [HKEY_CLASSES_ROOT\CLSID\{50CCECAC-7286-4CA0-9AD0-E309A2318482}]
          80004002@2

          [HKEY_CLASSES_ROOT\Interface\{243D841D-ABB9-4872-867A-3ED0EC91F19C}]
          8002801d@2

          [HKEY_CLASSES_ROOT\TypeLib\{745BA2BA-9B0E-459E-8A9C-A47C6A0131F1}]
          80040155@2

          [HKEY_CLASSES_ROOT\Interface\{00020400-0000-0000-C000-000000000046}]
          80004002@2

          [HKEY_CLASSES_ROOT\CLSID\{00020420-0000-0000-C000-000000000046}]
          8002801d@2

          [HKEY_CLASSES_ROOT\TypeLib\{745BA2BA-9B0E-459E-8A9C-A47C6A0131F1}]
          80040155@3 [HKEY_CLASSES_ROOT\Interface\{D831533D-0324-4EA4-B3FD-073AFEE85181}]
          8002801d@3 [HKEY_CLASSES_ROOT\TypeLib\{7576F677-3945-4DA2-B9F0-37850028A7E7}]
          80004002@2 [HKEY_CLASSES_ROOT\Interface\{243D841D-ABB9-4872-867A-3ED0EC91F19C}]
          8002801d@2 HKEY_CLASSES_ROOT\TypeLib\{745BA2BA-9B0E-459E-8A9C-A47C6A0131F1}]
          ffffffdf@3 [HKEY_CLASSES_ROOT\Interface\{0000000c-0000-0000-C000-000000000046}]
          80070005@2

          Error caused by Microsoft Windows XP SP2.
          The issue is resolved by installing the latest build of CMA.

          Changes Affecting
          this Problem:


          Change information is not available for this solution

          Last Modified:


          23JAN2006
          • 2. RE: McAfee Common Framework error
            texaspete
            Thanks yoda,

            I have seen that one. Solution 1 takes me to KB45362 and from there to KB44872. It says I have a problem with FrameworkManifest.xml. I know this is correct as, despite being 9k in size, the FrameworkManifest.xml file is completly blank.
            • 3. RE: McAfee Common Framework error
              Code_Green
              You haven't mentioned it but have you tried just uninstalling and re-installing?
              • 4. RE: McAfee Common Framework error
                texaspete
                I've tried the repair option in VSE, but I don't really want to uninstall if I can avoid it as I didn't have the details to re-register it. Plus, the only install CD I could find was a Dell badged security suite with a McAfee logo on it. Is that likely to be VSE?
                • 5. RE: McAfee Common Framework error
                  Code_Green
                  If it came with a Dell computer it is likely a retail version rather than an enterprise version. You mentioned earlier that this is a friends computer... where did they get VSE from?

                  You don't need to register VSE just install it if you can find the installation source. It is governed by a license agreement.
                  • 6. RE: McAfee Common Framework error
                    texaspete
                    I don't know for sure - friend was out at the time. She does have a Terminal Services type connection into her office, so there's a chance her employer asked her to use it.
                    • 7. RE: McAfee Common Framework error
                      texaspete
                      Now sorted, once I'd found an install CD, with an uninstall and reinstall.
                      • 8. RE: McAfee Common Framework error
                        Code_Green
                        Good to hear.
                        • 9. RE: McAfee Common Framework error
                          jssheep
                          Replacing the FrameworkManifest.xml with a FrameworkManifest.xml from another machine worked fine for me.
                          1 2 Previous Next