This content has been marked as final. Show 6 replies
You most likely have a problem with your repository share. Make sure you have set both share permissions AND NTFS permissions for the service account you use for the replication job. You can test/validate the connection from ePO when you set up the replication partner.
and thanks for the answer.
Where can I find information about this protocol as I need to see with our FW team about granting access from one server to the other.
Yes, it is a Windows shared folder, if you're using UNC type repositories. It shows up as \\<servername>\<SharedFolderName>. You could also use FTP or HTTP as you must have noticed.
But I remember running into the same issue as you discribed because on one of our shares, I forgot to set the NTFS permissions. Therefore the replication account could not upload the files.
If it's on your internal network, firewall rules should not have any effect unless of course there's one inbetween the servers. In that case, I'd imagine you'd need to allow SMB transfer but that's easy to test, if you can copy a file from one server to the other, manually, you should be all set.
I've never used SuperAgents nor GlobalUpdating, never had to and last I spoke to McAfee support about it, they said not to use this with ePO 4.0 (if I remember correctly).
Bearing in mind I dont want to Hijack the thread, why did they say not to use GlobalUpdating?
I don't remember about GlobalUpdating and I may have that wrong, but I'm pretty sure about SuperAgents, that with the newer agent version or ePO version is was no longer necessary!?! Sorry I can't be more precise. Maybe it still has it's value.
I am seeing the same error but with global updating turned on. the problem is intermittent for some of the repositories with varying degrees of consistency. Sometimes it is a one off or sometimes it can be every day for a week. The servers that fail often change as well.