Solved! Go to Solution.
Has this ever worked? When did the issue start and what changed? What agent version? Check the kb site for any known issues with the agent version you are running first of all.
Otherwise, the best way most of the time to fix a superagent is to first make it no longer a superagent. Then, delete the directory that the agent is using for the repository. If you are not able to delete it, then you might need to stop agent services. If you are unable to stop services, push a policy to it to disable self protection temporarily.
Once all that entire directory is gone, make it a superagent again - do not pre-create that folder. The agent conversion process to superagent needs to create that folder. Once that is done, try to replicate again.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
The problem turned out to be that I was using a corporate image that had residual GPO settings, which blocked my attempts. Once I set everything up in my personal lab, the replication issues disappeared.
Does it make any difference if you restart MA services on Super Agent machine?
Has this ever worked? When did the issue start and what changed? What agent version? Check the kb site for any known issues with the agent version you are running first of all.
Otherwise, the best way most of the time to fix a superagent is to first make it no longer a superagent. Then, delete the directory that the agent is using for the repository. If you are not able to delete it, then you might need to stop agent services. If you are unable to stop services, push a policy to it to disable self protection temporarily.
Once all that entire directory is gone, make it a superagent again - do not pre-create that folder. The agent conversion process to superagent needs to create that folder. Once that is done, try to replicate again.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
One other thing, make sure if you are using replication, that lazy caching is disabled in the agent policy. That can also cause access denied with files locked. You should use one or the other, but never both.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
That is what I did and fixed on Friday. Thanks!
Good deal!
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
I've followed your instructions exactly, but still have the problem. There are no known issues that I have been able to find for our version (MA 5.6.5.236). Any other tips? Thanks!
Check the macmnsvc log on the superagent server for any errors. Check also to make sure there is no proxy or firewall in between causing issues.
c:\programdata\mcafee\agent\logs
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
I have done so, but I'm not seeing anything that is related to the attempted replication. I've used Keywords 'error', 'fail', 'replication' and 'code'.... no luck. Are there any other keywords you'd recommend?
Look for the IP address of the epo server at the same time replication failed.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: