Mombu the Microsoft Forum sponsored links

Go Back   Mombu the Microsoft Forum > Microsoft > FILE SERVICES (TECHNET) > evenid 5014 during DFS replication
User Name
Password
REGISTER NOW! Mark Forums Read

sponsored links


Reply
 
1 10th April 23:03
External User
 
Posts: 1
Default evenid 5014 during DFS replication


I configured DFS on W2k3 R2. Replication seems to succeed, but every time I
recieve an error 5014 in the eventlog.

//-----------------------------------------------
Event Type: Warning
Event Source: DFSR
Event Category: None
Event ID: 5014
Date: 4/10/2007
Time: 2:43:30 PM
User: N/A
Computer: DC1
Description:
The DFS Replication service is stopping communication with partner DC2 for
replication group ContentReplication due to an error. The service will retry
the connection periodically.

Additional Information:
Error: 1726 (The remote procedure call failed.)
Connection ID: 126A745F-2A15-4E58-A66A-71C24FCFED76
Replication Group ID: 321177E8-F89B-4EDA-9A64-A65F2FCAE676

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
//-----------------------------------------------

I opened a specific port for RPC traffic and configured DFS to use that
port. I also installed KB908521, but without any luck. Does anybode know how
to loose the warnings?
  Reply With Quote


  sponsored links


2 11th April 15:54
nikolaj bjorner (msft)
External User
 
Posts: 1
Default evenid 5014 during DFS replication


The DFS management tools provide additional filtering on events to prune
spurious connection errors (when you configure one member before the other,
the first one will have problems connecting to the non-configured member).
I would recommend generating a health report and use this as an indication
of whether things are stable. With the event-log alone, you would have to
pair events and anti-events manually.

The 1726 error is by itself a fairly generic RPC error code and does not
convey much specific information. There could of course be various conditions
specific to your setup that cause such errors.


Nikolaj Bjorner (MSFT)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
  Reply With Quote
3 12th April 05:59
External User
 
Posts: 1
Default evenid 5014 during DFS replication


Hello Bjorn,

the health reports shows no errors, just a warning that the DFS service has
been restarted several times the past days, that's correct I did that
manually. Replication also seems te work. When I add data to the first
server, it's visible on the other server after a short while. Do you know how
much time a normal replication should take? Is it a matter of seconds?
  Reply With Quote
4 12th April 22:25
nikolaj bjorner (msft)
External User
 
Posts: 1
Default evenid 5014 during DFS replication


There could be up to a 5s, or so, delay from the first change for replication
to kick in as DFS-R contains some throttling. The other main sources of
delays consist of heavy file activity on the sending system or heavy download
activity on the receiving system. Otherwise, replication is mainly event
driven, so that a file system change gets signalled to DFS-R, then signalled
to the receiving partners, then the receiving partners download the updates.

Nikolaj Bjorner (MSFT)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
  Reply With Quote
5 25th April 01:41
External User
 
Posts: 1
Default evenid 5014 during DFS replication


I configured DFS on W2k3 R2. Replication seems to succeed, but every time I
recieve an error 5014 in the eventlog.

//-----------------------------------------------
Event Type: Warning
Event Source: DFSR
Event Category: None
Event ID: 5014
Date: 4/10/2007
Time: 2:43:30 PM
User: N/A
Computer: DC1
Description:
The DFS Replication service is stopping communication with partner DC2 for
replication group ContentReplication due to an error. The service will retry
the connection periodically.

Additional Information:
Error: 1726 (The remote procedure call failed.)
Connection ID: 126A745F-2A15-4E58-A66A-71C24FCFED76
Replication Group ID: 321177E8-F89B-4EDA-9A64-A65F2FCAE676

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
//-----------------------------------------------

I opened a specific port for RPC traffic and configured DFS to use that
port. I also installed KB908521, but without any luck. Does anybode know how
to loose the warnings?
  Reply With Quote
6 25th April 01:42
nikolaj bjorner (msft)
External User
 
Posts: 1
Default evenid 5014 during DFS replication


The DFS management tools provide additional filtering on events to prune
spurious connection errors (when you configure one member before the other,
the first one will have problems connecting to the non-configured member).
I would recommend generating a health report and use this as an indication
of whether things are stable. With the event-log alone, you would have to
pair events and anti-events manually.

The 1726 error is by itself a fairly generic RPC error code and does not
convey much specific information. There could of course be various conditions
specific to your setup that cause such errors.


Nikolaj Bjorner (MSFT)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
  Reply With Quote
7 30th April 12:05
External User
 
Posts: 1
Default evenid 5014 during DFS replication


Hello Bjorn,

the health reports shows no errors, just a warning that the DFS service has
been restarted several times the past days, that's correct I did that
manually. Replication also seems te work. When I add data to the first
server, it's visible on the other server after a short while. Do you know how
much time a normal replication should take? Is it a matter of seconds?
  Reply With Quote
8 30th April 12:07
nikolaj bjorner (msft)
External User
 
Posts: 1
Default evenid 5014 during DFS replication


There could be up to a 5s, or so, delay from the first change for replication
to kick in as DFS-R contains some throttling. The other main sources of
delays consist of heavy file activity on the sending system or heavy download
activity on the receiving system. Otherwise, replication is mainly event
driven, so that a file system change gets signalled to DFS-R, then signalled
to the receiving partners, then the receiving partners download the updates.

Nikolaj Bjorner (MSFT)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
  Reply With Quote


  sponsored links


Reply


Thread Tools
Display Modes




Copyright 2006 SmartyDevil.com - Dies Mies Jeschet Boenedoesef Douvema Enitemaus -
666