We help IT Professionals succeed at work.
Get Started

FRS DIAG ISSUES

1,567 Views
Last Modified: 2012-05-10
Having issues with mixed Server OS's 2003 R2 and 2008 R2 with FRS Diag: The was working pretty well before. All servers were demoted except DC3 then brought back up over 3 day weeekend. All were working with no errors untill several days later, presumably afterl replications finally completed. Now its a mess. I cannot seem to get a fix on the cause(s). repadmin /showrepl shows everything replicating correctly. SPN's all appear to be correct. as well. Can anyone give me a clue on this one. I'm to close to itand tired and am beating my head against the wall out of frustration.  DC2-3 are 2008 R2 all else are 2003 R2.
Thanks...

DC1
NtFrs      9/5/2010 8:02:36 PM      Warning      13508      The File Replication Service is having trouble enabling replication  from DC3 to DC1for c:\windows\sysvol\domain using the DNS name DC3.domain.com. FRS will keep retrying.     Following are some of the reasons you would see this warning.         [1] FRS can not correctly resolve the DNS name DC3.domain.com from this computer.     [2] FRS is not running on DC3.domain.com.     [3] The topology information in the Active Directory for this replica has not  yet replicated to all the Domain Controllers.         This event log message will appear once per connection, After the problem  is fixed you will see another event log message indicating that the connection  has been established.
      WARNING: Found Event ID 13508 errors without trailing 13509 ... see above for (up to) the 3 latest entries!

DC2
NTDS Replication      9/6/2010 1:02:36 PM      Error      1645      Active Directory did not perform an authenticated remote procedure call (RPC) to another domain controller because the desired service principal name (SPN) for the destination domain controller is not registered on the Key Distribution Center (KDC) domain controller that resolves the SPN.        Destination domain controller:  50ecd707-d579-41e0-b220-1ac48dfcba76._msdcs.domain.com    SPN:  E3514235-4B06-11D1-AB04-00C04FC2DCD2/50ecd707-d579-41e0-b220-1ac48dfcba76/domain.com@domain.com        User Action    Verify that the names of the destination domain controller and domain are correct. Also, verify that the SPN is registered on the KDC domain controller. If the destination domain controller has been recently promoted, it will be necessary for the local domain controller’s computer account data to replicate to the KDC before this computer can be authenticated.
      WARNING: Found Directory Service Errors in the past 15 days! FRS Depends on AD so Check AD Replication!

DC3
NtFrs      9/7/2010 9:31:57 PM      Warning      13508      The File Replication Service is having trouble enabling replication  from DC4 to DC3 for c:\windows\sysvol\domain using the DNS name DC4.domain.com. FRS will keep retrying.     Following are some of the reasons you would see this warning.         [1] FRS can not correctly resolve the DNS name DC4.domain.com from this computer.     [2] FRS is not running on DC4.domain.com.     [3] The topology information in the Active Directory for this replica has not  yet replicated to all the Domain Controllers.         This event log message will appear once per connection, After the problem  is fixed you will see another event log message indicating that the connection  has been established.
      WARNING: Found Event ID 13508 errors without trailing 13509 ... see above for (up to) the 3 latest entries!

 ......... failed 1
Checking for errors in Directory Service Event Log ....       
NTDS Replication      9/10/2010 11:29:16 AM      Error      1791      Replication of Naming Context DC=domain,DC=org from source f7cab657-9f79-4b00-be4f-91735ec9cbc0 (DC5.domain.com) has been aborted.  Replication requires consistent schema but last attempt to sync  the schema had failed. It is crucial that schema replication  functions properly. See previous errors for more diagnostics.  If this issue persists, please contact Microsoft Product DC4  Services for assistance.  Error 8418: The replication operation failed because of a schema mismatch between the servers involved..      
NTDS Replication      9/10/2010 11:29:16 AM      Error      1791      Replication of Naming Context DC=DomainDnsZones,DC=domain,DC=org from source f7cab657-9f79-4b00-be4f-91735ec9cbc0 (DC5.domain.com) has been aborted.  Replication requires consistent schema but last attempt to sync  the schema had failed. It is crucial that schema replication  functions properly. See previous errors for more diagnostics.  If this issue persists, please contact Microsoft Product DC4  Services for assistance.  Error 8418: The replication operation failed because of a schema mismatch between the servers involved..      
NTDS Replication      9/10/2010 11:26:37 AM      Error      1791      Replication of Naming Context DC=domain,DC=org from source f7cab657-9f79-4b00-be4f-91735ec9cbc0 (DC5.domain.com) has been aborted.  Replication requires consistent schema but last attempt to sync  the schema had failed. It is crucial that schema replication  functions properly. See previous errors for more diagnostics.  If this issue persists, please contact Microsoft Product DC4  Services for assistance.  Error 8418: The replication operation failed because of a schema mismatch between the servers involved..      
NTDS General      9/5/2010 12:16:45 AM      Error      1311      The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.        Directory partition:  CN=Configuration,DC=domain,DC=org        There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers.        User Action    Use Active Directory Sites and Services to perform one of the following actions:    - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.    - Add a Connection object to a domain controller that contains the directory partition in this site from a domain controller that contains the same directory partition in another site.        If neither of the Active Directory Sites and Services tasks correct this condition, see previous events logged by the KCC that identify the inaccessible domain controllers.      
NTDS General      9/5/2010 12:16:45 AM      Error      1311      The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.        Directory partition:  DC=ForestDnsZones,DC=domain,DC=org        There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers.        User Action    Use Active Directory Sites and Services to perform one of the following actions:    - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.    - Add a Connection object to a domain controller that contains the directory partition in this site from a domain controller that contains the same directory partition in another site.        If neither of the Active Directory Sites and Services tasks correct this condition, see previous events logged by the KCC that identify the inaccessible domain controllers.      
NTDS General      9/5/2010 12:16:45 AM      Error      1311      The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.        Directory partition:  DC=DomainDnsZones,DC=domain,DC=org        There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers.        User Action    Use Active Directory Sites and Services to perform one of the following actions:    - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.    - Add a Connection object to a domain controller that contains the directory partition in this site from a domain controller that contains the same directory partition in another site.        If neither of the Active Directory Sites and Services tasks correct this condition, see previous events logged by the KCC that identify the inaccessible domain controllers.      
NTDS General      9/5/2010 12:16:45 AM      Error      1311      The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.        Directory partition:  DC=domain,DC=org        There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers.        User Action    Use Active Directory Sites and Services to perform one of the following actions:    - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.    - Add a Connection object to a domain controller that contains the directory partition in this site from a domain controller that contains the same directory partition in another site.        If neither of the Active Directory Sites and Services tasks correct this condition, see previous events logged by the KCC that identify the inaccessible domain controllers.      
NTDS General      9/5/2010 12:01:45 AM      Error      1311      The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.        Directory partition:  CN=Configuration,DC=domain,DC=org        There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers.        User Action    Use Active Directory Sites and Services to perform one of the following actions:    - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.    - Add a Connection object to a domain controller that contains the directory partition in this site from a domain controller that contains the same directory partition in another site.        If neither of the Active Directory Sites and Services tasks correct this condition, see previous events logged by the KCC that identify the inaccessible domain controllers.      
NTDS General      9/5/2010 12:01:45 AM      Error      1311      The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.        Directory partition:  DC=ForestDnsZones,DC=domain,DC=org        There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers.        User Action    Use Active Directory Sites and Services to perform one of the following actions:    - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.    - Add a Connection object to a domain controller that contains the directory partition in this site from a domain controller that contains the same directory partition in another site.        If neither of the Active Directory Sites and Services tasks correct this condition, see previous events logged by the KCC that identify the inaccessible domain controllers.      
NTDS General      9/5/2010 12:01:45 AM      Error      1311      The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.        Directory partition:  DC=DomainDnsZones,DC=domain,DC=org        There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers.        User Action    Use Active Directory Sites and Services to perform one of the following actions:    - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.    - Add a Connection object to a domain controller that contains the directory partition in this site from a domain controller that contains the same directory partition in another site.        If neither of the Active Directory Sites and Services tasks correct this condition, see previous events logged by the KCC that identify the inaccessible domain controllers.      
NTDS General      9/5/2010 12:01:45 AM      Error      1311      The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.        Directory partition:  DC=domain,DC=org        There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers.        User Action    Use Active Directory Sites and Services to perform one of the following actions:    - Publish sufficient site connectivity information so that the KCC can determine a route by which this directory partition can reach this site. This is the preferred option.    - Add a Connection object to a domain controller that contains the directory partition in this site from a domain controller that contains the same directory partition in another site.        If neither of the Active Directory Sites and Services tasks correct this condition, see previous events logged by the KCC that identify the inaccessible domain controllers.
      WARNING: Found Directory Service Errors in the past 15 days! FRS Depends on AD so Check AD Replication!

 ......... failed 11
Checking for minimum FRS version requirement ... passed
Checking for errors/warnings in ntfrsutl ds ... passed
Checking for Replica Set configuration triggers... passed
Checking for suspicious file Backlog size... passed
Checking Overall Disk Space and SYSVOL structure (note: integrity is not checked)... passed
Checking for suspicious inlog entries ... passed
Checking for suspicious outlog entries ... passed
Checking for appropriate staging area size ... passed
Checking for errors in debug logs ...
      ERROR on NtFrs_0001.log : "RPC_S_CALL_FAILED_DNE(Indicates RPC Session was established to target, but there was a failure to send RPC call package. Check for Networking problems!)" : <SndCsMain:                     6760:   883: S0: 05:00:21> ++ ERROR - EXCEPTION (000006bf) :  WStatus: RPC_S_CALL_FAILED_DNE
      ERROR on NtFrs_0001.log : "RPC_S_CALL_FAILED_DNE(Indicates RPC Session was established to target, but there was a failure to send RPC call package. Check for Networking problems!)" : <SndCsMain:                     6760:   884: S0: 05:00:21> :SR: Cmd 12716f80, CxtG efb7a625, WS RPC_S_CALL_FAILED_DNE, To   DC4.domain.com Len:  (374) [SndFail - rpc exception]
      ERROR on NtFrs_0001.log : "RPC_S_CALL_FAILED_DNE(Indicates RPC Session was established to target, but there was a failure to send RPC call package. Check for Networking problems!)" : <SndCsMain:                     6760:   904: S0: 05:00:21> :SR: Cmd 12716f80, CxtG efb7a625, WS RPC_S_CALL_FAILED_DNE, To   DC4.domain.com Len:  (374) [SndFail - Send Penalty]

      Found 3 RPC_S_CALL_FAILED_DNE error(s)! Latest ones (up to 3) listed above

DC4
ONLY ONE PASSING

DC5
Checking for errors in debug logs ...
      ERROR on NtFrs_0004.log : "ERROR_ACCESS_DENIED" : <SndCsMain:                     5832:   904: S0: 00:36:08> :SR: Cmd 0152a9d0, CxtG 7a31f797, WS ERROR_ACCESS_DENIED, To   DC2.domain.com Len:  (372) [SndFail - Send Penalty]
      ERROR on NtFrs_0004.log : "ERROR_ACCESS_DENIED" : <SndCsMain:                     5832:   877: S0: 00:37:34> :SR: Cmd 01539168, CxtG 7a31f797, WS ERROR_ACCESS_DENIED, To   DC2.domain.com Len:  (372) [SndFail - rpc call]
      ERROR on NtFrs_0004.log : "ERROR_ACCESS_DENIED" : <SndCsMain:                     5832:   904: S0: 00:37:34> :SR: Cmd 01539168, CxtG 7a31f797, WS ERROR_ACCESS_DENIED, To   DC2.domain.com Len:  (372) [SndFail - Send Penalty]
Comment
Watch Question
CERTIFIED EXPERT
Top Expert 2012
Commented:
This problem has been solved!
Unlock 1 Answer and 28 Comments.
See Answer
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE