This content has been marked as final. Show 5 replies
Registry or dll failure, uninstall and reinstall agent on that machine.
I have searched this forum and this thread is the closest I could find to my problem. I have a Windows 2008 Server (x64) on which I try to run the McAfee Agent 184.108.40.2061 and it never registers with the server. The installation works fine but I've tried many wakeup calls and they always get me errors in the log, I have included a sample below. I have tried uninstalling / reinstalling at least a dozen times, making sure the files were deleted before installing but I always have the same error. The only thing I haven't done is reboot the server but I really can't do that now.
2009-09-10 14:36:07 I #1512 FrmSvc Starting Subsystem <Management>
2009-09-10 14:36:07 I #3700 Manage Mangement plugin watch worker thread started
2009-09-10 14:36:07 I #1512 Manage CManage::Start() InitializePolicies() -- failed result=-1(0xffffffff)
2009-09-10 14:36:07 I #3700 Manage WorkThread - WaitForMultipleObjects = WAIT_OBJECT_0
2009-09-10 14:36:07 I #3700 Manage Mangement plugin watch worker thread terminating
2009-09-10 14:36:07 I #1512 Manage call CManage::Deinitialize() -- because result=-1(0xffffffff)
2009-09-10 14:36:07 e #1512 FrmSvc Impossible de démarrer le sous-système <Management>, résultat=-1
2009-09-10 14:36:07 I #1512 FrmSvc Starting Subsystem <Agent>
2009-09-10 14:36:07 I #1512 Agent Démarrage du sous-système...
2009-09-10 14:36:07 i #1512 Agent Génération de la paire de clés de l'agent...
2009-09-10 14:36:07 e #1512 Agent La génération de la clé privée a ÉCHOUÉ
2009-09-10 14:36:07 e #1512 Agent La paire de clés de l'agent n'a pu être générée
Thanks for your time.
are you doing it from RDP using the /console switch or just standard mstsc?
are you manually clearing the agent section of the registry inbetween attempts?
do you already have an older entry for this in EPO that you have not deleted?
Is EMC PowerPath installed on the machine? MA 4 has a known conflict with this software - see KB60775.
It's not fixable in MA4 - the only solution at this point is either to downgrade to CMA3.6 or wait until MA4.5 is released.
I was installing over a RDP connection, I think that might have been the problem. Our server was rebooted this weekend and when it came back online it was transmitting its properties correctly.