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)
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.
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.
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)
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:
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.
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?