Restart the framework service that will help. Prob you have a shortage of memory in that server?
No shortage of memory. (1GB physical, only 313MB in use).
Rebooting doesn't help, can't see that restarting the framework service would, but thanks for that suggestion.
You didn't tell you where rebooting before re-install, so that was a guess.
Did you started with agent 4.5 or updated it? Try to use the 4.0 agent and check if the directory/share is OK and the security didn't change.
I have the same problem, opened a ticket, TS said it was a known problem and would be fixed with EPO 4.5 patch 2, due sometime in March.
1 of 1 people found this helpful
Yep, this a known issue- i find a few things seem to work well
1 is a for sure thing- downgrade to agent 4.0, the security mechnism isn't as fancy as 4.5.
2nd, is to /remove=agent, then delete the remnants of the repository, the sitelist.xml is left on the host- after thats all cleared push agent45, then re-apply SA policy.
Seeing the same behavior here, and using the same workarounds (reloading client) when it becomes critical. Thanks for digging into it. Let's hope the patch resolves it.
Now using Agent 220.127.116.119 with hotfix MA450HF620018WIN . The error code has changed but replication still unreliable and needing frequent manual intervention.
Is it just my perception, or is McAfee really bad at software testing and QA?