Ryfujk

Error "illegal generic type for instanceof" when using local classes

Why do we bend a book to keep it straight?

How much time will it take to get my passport back if I am applying for multiple Schengen visa countries?

English words in a non-english sci-fi novel

How to deal with a team lead who never gives me credit?

Using et al. for a last / senior author rather than for a first author

Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?

How do I stop a creek from eroding my steep embankment?

What is known about the Ubaid lizard-people figurines?

Naming the result of a source block

Can I cast Passwall to drop an enemy into a 20-foot pit?

Why are Kinder Surprise Eggs illegal in the USA?

How do pianists reach extremely loud dynamics?

What does this icon in iOS Stardew Valley mean?

Should I discuss the type of campaign with my players?

Fundamental Solution of the Pell Equation

How widely used is the term Treppenwitz? Is it something that most Germans know?

How to call a function with default parameter through a pointer to function that is the return of another function?

List *all* the tuples!

What does an IRS interview request entail when called in to verify expenses for a sole proprietor small business?

Why are there no cargo aircraft with "flying wing" design?

How to find out what spells would be useless to a blind NPC spellcaster?

Identifying polygons that intersect with another layer using QGIS?

How does the particle を relate to the verb 行く in the structure「A を + B に行く」?

Read Only Domain Controller not replicating after writable domain controller outage

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}

3

I have a RO domain controller that replicates with a writable DC which is at another site. The other week the writable DC was out for about 2 days because of maintenance at that site. After this outage, the RODC is no longer replicating with the writable DC.

The error I get is 1722, the RPC server is unavailable. I confirmed that the RPC service is running on both DCs. I suspect that the problem is caused by DNS - the DNS event logs contain the following:

The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "000006BA: SvcErr: DSID-03210BEB, problem 5012 (DIR_ERROR), data 0". The event data contains the error.

I also get the following errors:

The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.

All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.

There is insufficient site connectivity information for the KCC to create a spanning tree replication topology. Or, one or more directory servers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible directory servers.

The Knowledge Consistency Checker located a replication connection for the local read-only directory service, but the source server is not responsive or not replicating. A new suitable source server was not found from the current replication partners. This operation will be retried.

So maybe when the writable DC was restarted some sort of setting or configuration has been lost - causing the RODC to be unable to replicate with it. The DCs can ping each other fine though.

Any help would be much appreciated! Thanks!

active-directory domain-controller replication

share|improve this question

edited Mar 31 '16 at 18:49

longneck

20.9k24075

asked Dec 3 '14 at 19:59

KelvinKelvin

1612

bumped to the homepage by Community♦ 4 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Let's see a dcdiag /c from each DC, please, and also a repadmin /showreps on each DC.
  
  – Ryan Ries
  Dec 3 '14 at 20:13
  

  
  
  
  

add a comment | 

3

I have a RO domain controller that replicates with a writable DC which is at another site. The other week the writable DC was out for about 2 days because of maintenance at that site. After this outage, the RODC is no longer replicating with the writable DC.

The error I get is 1722, the RPC server is unavailable. I confirmed that the RPC service is running on both DCs. I suspect that the problem is caused by DNS - the DNS event logs contain the following:

The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "000006BA: SvcErr: DSID-03210BEB, problem 5012 (DIR_ERROR), data 0". The event data contains the error.

I also get the following errors:

The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.

All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.

There is insufficient site connectivity information for the KCC to create a spanning tree replication topology. Or, one or more directory servers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible directory servers.

The Knowledge Consistency Checker located a replication connection for the local read-only directory service, but the source server is not responsive or not replicating. A new suitable source server was not found from the current replication partners. This operation will be retried.

So maybe when the writable DC was restarted some sort of setting or configuration has been lost - causing the RODC to be unable to replicate with it. The DCs can ping each other fine though.

Any help would be much appreciated! Thanks!

active-directory domain-controller replication

share|improve this question

edited Mar 31 '16 at 18:49

longneck

20.9k24075

asked Dec 3 '14 at 19:59

KelvinKelvin

1612

bumped to the homepage by Community♦ 4 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Let's see a dcdiag /c from each DC, please, and also a repadmin /showreps on each DC.
  
  – Ryan Ries
  Dec 3 '14 at 20:13
  

  
  
  
  

add a comment | 

I have a RO domain controller that replicates with a writable DC which is at another site. The other week the writable DC was out for about 2 days because of maintenance at that site. After this outage, the RODC is no longer replicating with the writable DC.

The error I get is 1722, the RPC server is unavailable. I confirmed that the RPC service is running on both DCs. I suspect that the problem is caused by DNS - the DNS event logs contain the following:

The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "000006BA: SvcErr: DSID-03210BEB, problem 5012 (DIR_ERROR), data 0". The event data contains the error.

I also get the following errors:

The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site.

All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.

There is insufficient site connectivity information for the KCC to create a spanning tree replication topology. Or, one or more directory servers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible directory servers.

The Knowledge Consistency Checker located a replication connection for the local read-only directory service, but the source server is not responsive or not replicating. A new suitable source server was not found from the current replication partners. This operation will be retried.

So maybe when the writable DC was restarted some sort of setting or configuration has been lost - causing the RODC to be unable to replicate with it. The DCs can ping each other fine though.

Any help would be much appreciated! Thanks!

active-directory domain-controller replication

share|improve this question

edited Mar 31 '16 at 18:49

longneck

20.9k24075

asked Dec 3 '14 at 19:59

KelvinKelvin

1612

share|improve this question

edited Mar 31 '16 at 18:49

longneck

20.9k24075

asked Dec 3 '14 at 19:59

KelvinKelvin

1612

share|improve this question

edited Mar 31 '16 at 18:49

longneck

20.9k24075

asked Dec 3 '14 at 19:59

KelvinKelvin

1612

edited Mar 31 '16 at 18:49

longneck

20.9k24075

edited Mar 31 '16 at 18:49

longneck

20.9k24075

asked Dec 3 '14 at 19:59

KelvinKelvin

1612

asked Dec 3 '14 at 19:59

KelvinKelvin

1612

1 Answer
1

active

oldest

votes

0

I've had this exact problem.

What kind of network do you have? You need one that is fully meshed for replication to work properly. If you open up active directory sites and services, you can see DC's are trying to replicate from each other. They will complain if they can only see one main DC, they need to be able to see and replicate from each other.

share|improve this answer

answered Dec 3 '14 at 20:14

Josh KelahanJosh Kelahan

11

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  How can I ensure that it's fully meshed?
  
  – Kelvin
  Dec 3 '14 at 20:33
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The RODC is supposed to replicate with 2 writable DCs but one of them stopped replicating in May. It continued to replicate with the 2nd one until a couple of weeks ago (although replication failed for 1 day in June when there was another outage)
  
  – Kelvin
  Dec 3 '14 at 20:35
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Use sites and services to remove both of the replication partners: Find the RODC on the left, and expand it ServersServerNameNTDS Settings. On the NTDS settings, you will see where it is trying to replicate from. Delete these. You said you had 2 servers, but one stopped in May. Did it tombstone? After you have deleted the connections, force replication on your server. Use: repadmin /replicate <name of working DC> It should rebuild its connections and replicate.
  
  – Josh Kelahan
  Dec 3 '14 at 20:43
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks very much for your help. Unfortunately deleting the connections didn't work. I don't think the 2nd DC tombstoned - it's still active and replicating with the other writable CD
  
  – Kelvin
  Dec 3 '14 at 21:33
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f648947%2fread-only-domain-controller-not-replicating-after-writable-domain-controller-out%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

I've had this exact problem.

What kind of network do you have? You need one that is fully meshed for replication to work properly. If you open up active directory sites and services, you can see DC's are trying to replicate from each other. They will complain if they can only see one main DC, they need to be able to see and replicate from each other.

share|improve this answer

answered Dec 3 '14 at 20:14

Josh KelahanJosh Kelahan

11

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  How can I ensure that it's fully meshed?
  
  – Kelvin
  Dec 3 '14 at 20:33
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The RODC is supposed to replicate with 2 writable DCs but one of them stopped replicating in May. It continued to replicate with the 2nd one until a couple of weeks ago (although replication failed for 1 day in June when there was another outage)
  
  – Kelvin
  Dec 3 '14 at 20:35
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Use sites and services to remove both of the replication partners: Find the RODC on the left, and expand it ServersServerNameNTDS Settings. On the NTDS settings, you will see where it is trying to replicate from. Delete these. You said you had 2 servers, but one stopped in May. Did it tombstone? After you have deleted the connections, force replication on your server. Use: repadmin /replicate <name of working DC> It should rebuild its connections and replicate.
  
  – Josh Kelahan
  Dec 3 '14 at 20:43
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks very much for your help. Unfortunately deleting the connections didn't work. I don't think the 2nd DC tombstoned - it's still active and replicating with the other writable CD
  
  – Kelvin
  Dec 3 '14 at 21:33
  

  
  
  
  

add a comment | 

0

I've had this exact problem.

What kind of network do you have? You need one that is fully meshed for replication to work properly. If you open up active directory sites and services, you can see DC's are trying to replicate from each other. They will complain if they can only see one main DC, they need to be able to see and replicate from each other.

share|improve this answer

answered Dec 3 '14 at 20:14

Josh KelahanJosh Kelahan

11

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  How can I ensure that it's fully meshed?
  
  – Kelvin
  Dec 3 '14 at 20:33
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The RODC is supposed to replicate with 2 writable DCs but one of them stopped replicating in May. It continued to replicate with the 2nd one until a couple of weeks ago (although replication failed for 1 day in June when there was another outage)
  
  – Kelvin
  Dec 3 '14 at 20:35
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Use sites and services to remove both of the replication partners: Find the RODC on the left, and expand it ServersServerNameNTDS Settings. On the NTDS settings, you will see where it is trying to replicate from. Delete these. You said you had 2 servers, but one stopped in May. Did it tombstone? After you have deleted the connections, force replication on your server. Use: repadmin /replicate <name of working DC> It should rebuild its connections and replicate.
  
  – Josh Kelahan
  Dec 3 '14 at 20:43
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks very much for your help. Unfortunately deleting the connections didn't work. I don't think the 2nd DC tombstoned - it's still active and replicating with the other writable CD
  
  – Kelvin
  Dec 3 '14 at 21:33
  

  
  
  
  

add a comment | 

I've had this exact problem.

What kind of network do you have? You need one that is fully meshed for replication to work properly. If you open up active directory sites and services, you can see DC's are trying to replicate from each other. They will complain if they can only see one main DC, they need to be able to see and replicate from each other.

share|improve this answer

answered Dec 3 '14 at 20:14

Josh KelahanJosh Kelahan

11

share|improve this answer

answered Dec 3 '14 at 20:14

Josh KelahanJosh Kelahan

11

answered Dec 3 '14 at 20:14

Josh KelahanJosh Kelahan

11

answered Dec 3 '14 at 20:14

Josh KelahanJosh Kelahan

11