Hi,
We are using McAfee Virusscan Enterpise 7.0 with EPO (ePolicy Orchestrator Agent). About 90% of the machines don't have a problem using the AV software and updating the AV files. However, the other 10% do have problems. The machines can't update because: "Failed to initialize Common Updater subsytem. Make sure the McAfee Framework Service is running". This happens all over sudden (yesterday it worked, now it fails). The service can't be started anymore. Hence, the AV files are not updated at all.
Anyone has experienced this?
Affected: NT4-SP6a, XP-SP1
Thanks.
Ed
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Windows XP SP2 RC1 Users: who attempted to run VirusScan Enterprise 7 auto update (MIT installer) were not be able to do so without applying the solution after upgrading to SP2. The error: "Failed to initialize common updater subsystem. Make sure the McAfee Framework Service is running". A workaround was posted within the test matirx: <http://web.mit.edu/swrt/r
Pete,
Thanks for your quick response. Tried to locate Framepkg.exe but can't find it. Do you know where it should reside? Also, uninstalling/reinstalling is not an option. We would need several FTE's to do this on a daily base (talking about hundreds of machines) ;-). Also found soemting regarding NAI service packs. Will try that as well.
Thanks. Let you know if it solved the problem.
>>Tried to locate Framepkg.exe but can't find it. Do you know where it should reside?
where you put it when you set up Epo (its usually on the server) you can always create anothe FramPkg.exe on the server from the epo management console if you cant find it.
put in on the server (I keep mine in a folder called ePO_Agents) on the client
\\servername\epo_agents {enter}
when it opens run the FramePkg.exe file it will disable the framework service then upgrade it - before you do this make sure everything is runnin well in ePO
also upgrade Epo to version 3.01
If removal of the agent from the ePO server fails there is a process for manual remove of the agent from an affected PC. Depending on how (and of what version) the agent was deployed, the location may vary. Under the current version the path and command is C:\Program files\Network associates\Common Framework\FrmInst.exe /Remove=Agent. Previous versions placed this in a folder on the root of the C drive (such as C:\ePOAgent) and may be FramePkg.exe instead of FrmInst.exe. This should usually work irregardless, but you may have to stop the McAfee Framework Service prior to manual removal. It is also recommended that any Anti-Virus software be uninstalled via Add/Remove Programs prior to redeploying the agent. Once this is done, set the McaFee Framework Service to Disabled and reboot the PC. If the path was different than the current one I would recommend deleting all old folders before redeploying the Agent. You may now deploy the current agent from the ePO server. I usually delete the system and then add it back in to the managed list, then send the agent install to the PC. In most cases this has been successful for me, although I have seen a couple of times where the manual removal will not even work. These systems were eventually rebuilt.
Current versions:
ePO 3.5
VirusScan Enterprise 8.0i
Windows XP and Windows 2000
Network Associates has posted a new KB article with updated instructions on the manual removal of the agent.
KB43214
"http://knowledgemap.nai.c
http://knowledgemap.nai.co
I have yet to try this, but I hope it helps.
Hi All,
I also had this problem on a standalone machine and none of the above worked. I uninstalled McAfee but the Framework service still stayed in the services mmc. I tried reinstalling and still got same error that it couldn't update. I fixed it by trawling through the reg and deleting any registry entries with "McAfee" and "Framework" references. I reinstalled and it worked fine.
Hope this helps,
FL
What I found was the the error is due to the FrameworkManifest.XML file being corrupt. In my case I got an error that the service is not started. If you try to uninstall the framework service, I get an error that "cannot access path to C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\FrameworkManifes
Check the services to ensure that the McAfee Framework Service is stopped. More than likely the service will not even start to begin with.
Replace this file:
C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\FrameworkManifes
Now you will need to uninstall the framework package.
Open the command prompt and navigate to
C:\Program Files\McAfee\Common Framework
Type frminst.exe /forceuninstall
Then re-install the framework package.
Restart the PC.
Once the PC is back up and you have logged back in, check the services to verify that the McAfee Framework Service is running.
The problem should be fixed and you can now successfully update McAfee.
I just had this as well and I tried to re-install the framework package but it could not read a file.
So I uninstalled Mcafee, then I restarted the PC,
I delete the Mcafee folder in C:\Documents and Settings\All Users\Application Data
And then I reinstalled Mcafee and the Framework was completly re-installed this time and Mcafee works perfectly once again.
I've had this in the past and I wish I knew how to fix it then, because this was so easy.
Lasareath
Business Accounts
Answer for Membership
by: PeteLongPosted on 2004-07-27 at 02:34:17ID: 11644664
Same Problem http://www.experts-exchang
Usually either a remove an reinstall of the client software or re-running the FramePkg.exe will fix this problem.
Pete