Recently started deploying HDLP 9.1 (ePO 4.5) and we're getting many agent status listed as driver initialization failed. We're also seeing a lot of pop up windows upon initial logon stating fcag.exe - Application Error : The instruction at "0x0069880c" referenced memory at "0x83ffff7a". The memory could not be "read". I believe the two events are related but haven't proved it yet. I cannot find anything in the knowledge base. Has anyone experienced this and/or fixed the problem?
I didn't catch that you were using 220.127.116.11 and just realized what that meant. Do you have an open SR? A fix is in the works.Message was edited by: Raja on 2/8/11 11:02:20 PM GMT-08:00
We too are experiencing the same issue with the 18.104.22.168 agents. (Did not see this issue old DLP agents) We get this error on both XP and Win 7 machines. The error seems to appear after a specific GPO is applied to the machine, however, we do not know specifically which setting in the GPO is causing the error. Unfortunately the GPO that appears to be the culprit is our domain baseline computer GPO that gets applied to every machine on the domain. So we cannot proceed with the upgrade of the DLP agent until this issue is resolved. Any help with this would be greatly appreciated.
Adding to the list of victims of this issue. I would say about 50% of my organization is having this same issue. Even after re-installing the agent, a few days later again we have "Agent Drivers Initialization failed" Anyone with any clue as to what GPO is causing this problem and can give me some help here?
We ended up getting a newer DLP version from McAfee (22.214.171.124). Not sure if this is released for production yet but it fixed the install errors we were getting. Now we're trying to get McAfee to tell us what the agent status of "none" means.
I have researched extensively and found nothing about a 126.96.36.199 version. Is this in beta still? Did they have any news on when it was going to be released. We are still haven't this issue where the agent drivers fail to initialize when a user logs in. Or even after a user stays logged in for a period of time. Anyone have ANY input? We are kinda desperate here as we need to have this running in my organization.