DFS Replicaton Problem Event ID 5014 and 5004

Question

_{Saturday, June 30, 2012 1:17 PM}

Hi,

Currently I have server 2003 r2 replicating with Server 2008 enterprise (Primary) in two sites. I am in the process of removing server 2003 and installing new server 2008 r2 (Secondary) and start replication betwen both server 2008.

I have added the new folder target to new server 2008 (Secondary) and have started bidirectional replicating between server 2008 NOT SERVER 2003.

Server 2003 and server 2008 are on the different site whereas server 2008 (primary) and new server 2008 are on the same site.

The server replicaton is happening but very slow. I have been running for last 24 hrs and it has only done 800 Mb. It's using the full bandwith and have allocated 40 GB staging file size. The total data on the primary server is around 200 Gb. I have check the DFS replication log and found out event id 5014 and after 1 second event id 5004. The gap various from 1 second to 4 second to 30 min.

Event ID: 5014

The DFS Replication service is stopping communication with partner <SERVER> for replication group <>due to an error. The service will retry the connection periodically.

Error: 1726 (The remote procedure call failed.)

I do not see the above warning and log on primary server 2008.

Also i am not sure if it makes any difference, I do not see the DFSRoot on C drive of the new server whereas both server 2003 and server 2008 (primary) have the DFSRoot folder on the c drive.

Any advice would be appreciated.

Thanks.

All replies (2)

_{Saturday, June 30, 2012 4:56 PM ✅Answered}

Hello Heymula, 

I suggest you check similar kind of thread for Event ID 5014:http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/d27bd902-034e-4230-9516-0ede42308193

Another useful link:http://support.microsoft.com/kb/976442

Regards, Ravikumar P

_{Tuesday, July 3, 2012 7:35 AM ✅Answered}

Hi,

Another related thread:

DFS Replication failing for large files

http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/93993c45-5361-4f04-a60c-1863a7ec7a4c

It is resolved by changing the MTU size.

TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected].