KB70009 ( https://mysupport.mcafee.com/eservice/Article.aspx?id=KB70009 ) has just been published:
When the ePO server is unavailable or unreachable, and an Agent-to-Server Connection Interval (ASCI) is attempted on a client computer, the frameworkservice.exe process starts using 95-100% CPU. The high CPU continues until you stop the frameworkservice.exe process. This does not occur in all environments and is specific to the McAfee Agent 220.127.116.119 (Patch 1) build.
There are not Agent log entries at this time that will definitively qualify the issue.
When the agent attempts to ping an inaccessible Distributed Repository during processing of the SiteList.xml, the frameworkservice.exe process starts using 95-100% CPU. The high CPU continues until you stop the frameworkservice.exe process. This does not occur in all environments and is specific to the McAfee Agent 18.104.22.1689 (Patch 1) build.
The Agent log shows the processing of SiteList.xml. When it locates the offending repository, SiteList processing stops and no further logging related to the SiteList.xml is present. CPU usage elevates at this point:
If you experience these symptoms, contact McAfee Technical Support and quote this article number.
Once the appropriate data has been collected, implement the Workaround shown below to restore normal operations until a code based solution can be provided.
In addition to the files above, please provide the following data:
Terminate the Frameworkservice.exe on the affected computer and downgrade to one of the following agent versions until a code based solution can be provided:
Do you see it in your environment? Mental note... never reboot the EPO server
We are experiencing this issue. As many of our epo clients are in remote sites, and sometimes links to central ePO server is down, we have many reports of workstations running @ 99% cpu due to frameworkservice.exe process.
Now we know why.
Downgrading Agent to 4.0 is not really an option, so we need some hotfix or patch to address it.
Any idea how is it going to be fix? Would the fix be included in MA4.5 Patch 2? When is P2 expected?
The engineering teams are looking at this as a matter of the highest priority. If you're experiencing the problem then please open a case with support so that it can be escalated and tracked.
The problem is that error occurs randomly, and if occurred users don't look for help - they just reboot the PC. They complain later.
I'll try to reproduce it and then take screen shots/mer and open a case, lets hope it wont be stuck at Tier1....
Message was edited by: psolinski on 30/09/10 09:06:44 CEST
It says you can downgrade to the "original" Agent 4.5, you wouldn't have to downgrade to 4.0.
Oh, yes, reading it for the second time (after a cup of green tea) I can see this
Anyway downgrading the Agent on nearly 3k machines isnt my favorite option.
If MA45 Patch 2 is just "around the corner" I prefer to wait.
KB says "early Q4".... any news from McAfee MA team?
This issue will be resolved with a post McAfee Agent 4.5 Patch1 hotfix. This hotfix is tentatively targeted to begin the Managed Release cycle (late in the day US time) on October 19, 2010.
Additionally, the hotfix for this issue will also be included in McAfee Agent 4.5 Patch 2 for Windows.
This issue is targeted to be resolved with McAfee Agent 4.5 Patch 2, which is currently expected to begin Managed Release in early Q4 2010.
This issue will be resolved with a post McAfee Agent 4.5 Patch1 hotfix. This hotfix is tentatively targeted to begin the Managed Release cycle (late in the day US time) on October 19, 2010
Anybody got the hotfix?
You can get the HF by escalating a case to Tier 3 McAfee Support. I believe you should have the link to download it (your particular case has come to me)...please check your e-mail.