Discussion:
AD RPC replication Issue
(too old to reply)
KC
2005-11-01 18:01:07 UTC
Permalink
About every week AD replication begins to fail between my ONLY two sites and
my users at the remote office are unable to access network resources at the
main site.

I DCPROMO'd the remote office server about a month ago with no errors. Every
week since then replication fails and the only way to rectify the issue is to
reboot the DC at the main office. This has happened 4 times so far, a reboot
has solved the issue each time. The issue is that the bridgehead server is
also the Exchange server and requires advanced notice prior to a reboot.

The AD design is straightforward:
2 DCs (SISJDC01 & SISJDC02) at the main site using intrasite replication
SISJDC01 is holding all FSMO roles
SISJDC02 is the brigehead for intersite replication (IP)

1 DC (SIDFS01) at the remote office using intersite replication
SIDFS01 is hosting a Global Catalog

Troubleshooting:
-Verified VPN connectivity
-Increased the RPC time out value (article ID 830746)
-Toggled KCC on all DCs using the script (article ID 245610)
-Removed the Default site link and “hand made it”
-I changed the DNS of the remote office from itself to the 2 DCs at the main
site (to make sure that this server was not an “island”
-Toggled the netlogon service on the DC’s
-Verified that Net View lists available resources on all DCs
-Checked replication topology on all NTDS listings
-Attempted to force replication fails with RPC errors
-Verified NetBios name resolution and added entries to the Host file for
each DC on each DC
-Installed FRSdiag but was lost in result errors.


Errors:
Since there are only 3 DCs involved I have decided to include the error
messages from each server as well as a DCDiag and Netdiag from each.
*SIDFS01 is uable to run a Netdiag, I assume because I have its DNS pointed
the main office servers and not itself.

SIDFS01
Remote office server

Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1188
Date: 11/1/2005
Time: 7:52:11 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SIDFS01
Description:
A thread in Active Directory is waiting for the completion of a RPC made to
the following domain controller.

Domain controller:
bd206802-6a5c-44b8-a445-00ffd744dc84._msdcs.structint.ad
Operation:
get changes
Thread ID:
b58
Timeout period (minutes):
48

Active Directory has attempted to cancel the call and recover this thread.

User Action
If this condition continues, restart the domain controller.

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

*****************************************************
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1232
Date: 11/1/2005
Time: 7:52:11 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SIDFS01
Description:
Active Directory attempted to perform a remote procedure call (RPC) to the
following server. The call timed out and was cancelled.

Server:
bd206802-6a5c-44b8-a445-00ffd744dc84._msdcs.structint.ad
Call Timeout (Mins):
48
Thread ID:
b58

************************************
DCDIAG

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Structural-Integrity-Denver\sidfs01
Starting test: Connectivity
......................... sidfs01 passed test Connectivity

Doing primary tests

Testing server: Structural-Integrity-Denver\sidfs01
Starting test: Replications
[Replications Check,sidfs01] A recent replication attempt failed:
From SISJDC02 to sidfs01
Naming Context: DC=ForestDnsZones,DC=structint,DC=ad
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2005-11-01 09:02:44.
The last success occurred at 2005-10-31 20:46:02.
8 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
[Replications Check,sidfs01] A recent replication attempt failed:
From SISJDC02 to sidfs01
Naming Context: DC=DomainDnsZones,DC=structint,DC=ad
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2005-11-01 08:59:40.
The last success occurred at 2005-10-31 20:46:02.
8 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
[Replications Check,sidfs01] A recent replication attempt failed:
From SISJDC02 to sidfs01
Naming Context: CN=Configuration,DC=structint,DC=ad
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2005-11-01 08:50:28.
The last success occurred at 2005-10-31 21:00:19.
17 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
[Replications Check,sidfs01] A recent replication attempt failed:
From SISJDC02 to sidfs01
Naming Context: DC=structint,DC=ad
The replication generated an error (1726):
The remote procedure call failed.
The failure occurred at 2005-11-01 08:56:36.
The last success occurred at 2005-10-31 23:00:33.
6 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
REPLICATION-RECEIVED LATENCY WARNING
sidfs01: Current time is 2005-11-01 09:02:58.
DC=ForestDnsZones,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:46:02.
Last replication recieved from SISJDC02 at 2005-10-31 20:46:02.
DC=DomainDnsZones,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:46:02.
Last replication recieved from SISJDC02 at 2005-10-31 20:46:02.
CN=Configuration,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:54:37.
Last replication recieved from SISJDC02 at 2005-10-31 21:00:19.
......................... sidfs01 passed test Replications
Starting test: NCSecDesc
......................... sidfs01 passed test NCSecDesc
Starting test: NetLogons
......................... sidfs01 passed test NetLogons
Starting test: Advertising
......................... sidfs01 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... sidfs01 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... sidfs01 passed test RidManager
Starting test: MachineAccount
......................... sidfs01 passed test MachineAccount
Starting test: Services
......................... sidfs01 passed test Services
Starting test: ObjectsReplicated
......................... sidfs01 passed test ObjectsReplicated
Starting test: frssysvol
......................... sidfs01 passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may
cause
Group Policy problems.
......................... sidfs01 failed test frsevent
Starting test: kccevent
......................... sidfs01 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00000457
Time Generated: 11/01/2005 08:42:39
(Event String could not be retrieved)
......................... sidfs01 failed test systemlog
Starting test: VerifyReferences
......................... sidfs01 passed test VerifyReferences

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : structint
Starting test: CrossRefValidation
......................... structint passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... structint passed test CheckSDRefDom

Running enterprise tests on : structint.ad
Starting test: Intersite
......................... structint.ad passed test Intersite
Starting test: FsmoCheck
......................... structint.ad passed test FsmoCheck






SISJDC01
FSMO roles holder
First DC in Domain

Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1566
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
Description:
All domain controllers in the following site that can replicate the
directory partition over this transport are currently unavailable.

Site:
CN=Structural-Integrity-Denver,CN=Sites,CN=Configuration,DC=structint,DC=ad
Directory partition:
DC=DomainDnsZones,DC=structint,DC=ad
Transport:
CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=structint,DC=ad

***************************************

Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
Description:
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.

Sites:
CN=Structural-Integrity-Denver,CN=Sites,CN=Configuration,DC=structint,DC=ad


***************************************

Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
Description:
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.

Sites:
CN=Structural-Integrity-Denver,CN=Sites,CN=Configuration,DC=structint,DC=ad

Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
Description:
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.

Sites:
CN=Structural-Integrity-Denver,CN=Sites,CN=Configuration,DC=structint,DC=ad


***************************************

Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
Description:
The Knowledge Consistency Checker (KCC) has detected problems with the
following directory partition.

Directory partition:
DC=ForestDnsZones,DC=structint,DC=ad

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.

***************************************

DCDIAG
Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Structural-Integrity-San-Jose\SISJDC01
Starting test: Connectivity
......................... SISJDC01 passed test Connectivity

Doing primary tests

Testing server: Structural-Integrity-San-Jose\SISJDC01
Starting test: Replications
REPLICATION-RECEIVED LATENCY WARNING
SISJDC01: Current time is 2005-11-01 08:01:20.
DC=ForestDnsZones,DC=structint,DC=ad
Last replication recieved from sidfs01 at 2005-10-26 23:49:34.
DC=DomainDnsZones,DC=structint,DC=ad
Last replication recieved from sidfs01 at 2005-10-26 23:49:34.
CN=Schema,CN=Configuration,DC=structint,DC=ad
Last replication recieved from sidfs01 at 2005-10-26 23:49:34.
CN=Configuration,DC=structint,DC=ad
Last replication recieved from sidfs01 at 2005-10-26 23:49:34.
DC=structint,DC=ad
Last replication recieved from sidfs01 at 2005-10-26 23:49:33.
......................... SISJDC01 passed test Replications
Starting test: NCSecDesc
......................... SISJDC01 passed test NCSecDesc
Starting test: NetLogons
......................... SISJDC01 passed test NetLogons
Starting test: Advertising
......................... SISJDC01 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... SISJDC01 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... SISJDC01 passed test RidManager
Starting test: MachineAccount
......................... SISJDC01 passed test MachineAccount
Starting test: Services
......................... SISJDC01 passed test Services
Starting test: ObjectsReplicated
......................... SISJDC01 passed test ObjectsReplicated
Starting test: frssysvol
......................... SISJDC01 passed test frssysvol
Starting test: frsevent
......................... SISJDC01 passed test frsevent
Starting test: kccevent
An Warning Event occured. EventID: 0x8000061E
Time Generated: 11/01/2005 07:47:53
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 11/01/2005 07:47:53
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 11/01/2005 07:47:53
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 11/01/2005 07:47:53
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) was
......................... SISJDC01 failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00000457
Time Generated: 11/01/2005 07:47:12
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 11/01/2005 07:47:12
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0001B77
Time Generated: 11/01/2005 07:47:15
(Event String could not be retrieved)
......................... SISJDC01 failed test systemlog
Starting test: VerifyReferences
......................... SISJDC01 passed test VerifyReferences

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : structint
Starting test: CrossRefValidation
......................... structint passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... structint passed test CheckSDRefDom

Running enterprise tests on : structint.ad
Starting test: Intersite
......................... structint.ad passed test Intersite
Starting test: FsmoCheck
......................... structint.ad passed test FsmoCheck

***************************************


Global results

Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{00393C90-F937-4BFE-88F6-EDD6071B007F}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed

IP loopback ping test. . . . . . . : Passed

Default gateway test . . . . . . . : Passed

NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation
Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.

Winsock test . . . . . . . . . . . : Passed

DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server
'192.168.11.4
1' and other DCs also have some of the names registered.
PASS - All the DNS entries for DC are registered on DNS server
'192.168.11.4
2' and other DCs also have some of the names registered.

Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{00393C90-F937-4BFE-88F6-EDD6071B007F}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{00393C90-F937-4BFE-88F6-EDD6071B007F}
The browser is bound to 1 NetBt transport.

DC discovery test. . . . . . . . . : Passed

DC list test . . . . . . . . . . . : Passed

Trust relationship test. . . . . . : Skipped

Kerberos test. . . . . . . . . . . : Passed

LDAP test. . . . . . . . . . . . . : Passed

Bindings test. . . . . . . . . . . : Passed

WAN configuration test . . . . . . : Skipped
No active remote access connections.

Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information

The command completed successfully





SISJDC02
Exchange server
Intersite Bridgehead Server

Event Type: Warning
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1862
Date: 10/31/2005
Time: 11:49:29 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC02
Description:
This is the replication status for the following directory partition on the
local domain controller.

Directory partition:
DC=ForestDnsZones,DC=structint,DC=ad

The local domain controller has not received replication information from a
number of domain controllers in other sites within the configured latency
intverval.

Number of domain controllers:
1
Latency Interval (Hours):
24

The latency interval can be modified with the following registry key.

Registry Key:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator latency
error interval (hours)

To identify the domain controllers by name, install the support tools
included on the installation CD and run dcdiag.exe.
You can also use the support tool repadmin.exe to display the replication
latencies of the domain controllers in the forest. The command is "repadmin
/showvector /latency <partition-dn>".
N.
2005-11-01 20:08:12 UTC
Permalink
I am having the exact same weekly issue. Do you have WIN 2003 SP1 insalled
on your DC's ? I have read about a hotfix that updates the TCPIP.SYS file
to correct a problem introduced in Win 2003 SP1. I will be implementing
this hot fix tonight. I'll let the group know how I make out.

Here's the link:
http://support.microsoft.com/default.aspx?scid=898060
Post by KC
About every week AD replication begins to fail between my ONLY two sites and
my users at the remote office are unable to access network resources at the
main site.
I DCPROMO'd the remote office server about a month ago with no errors. Every
week since then replication fails and the only way to rectify the issue is to
reboot the DC at the main office. This has happened 4 times so far, a reboot
has solved the issue each time. The issue is that the bridgehead server is
also the Exchange server and requires advanced notice prior to a reboot.
2 DCs (SISJDC01 & SISJDC02) at the main site using intrasite replication
SISJDC01 is holding all FSMO roles
SISJDC02 is the brigehead for intersite replication (IP)
1 DC (SIDFS01) at the remote office using intersite replication
SIDFS01 is hosting a Global Catalog
-Verified VPN connectivity
-Increased the RPC time out value (article ID 830746)
-Toggled KCC on all DCs using the script (article ID 245610)
-Removed the Default site link and "hand made it"
-I changed the DNS of the remote office from itself to the 2 DCs at the main
site (to make sure that this server was not an "island"
-Toggled the netlogon service on the DC's
-Verified that Net View lists available resources on all DCs
-Checked replication topology on all NTDS listings
-Attempted to force replication fails with RPC errors
-Verified NetBios name resolution and added entries to the Host file for
each DC on each DC
-Installed FRSdiag but was lost in result errors.
Since there are only 3 DCs involved I have decided to include the error
messages from each server as well as a DCDiag and Netdiag from each.
*SIDFS01 is uable to run a Netdiag, I assume because I have its DNS pointed
the main office servers and not itself.
SIDFS01
Remote office server
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1188
Date: 11/1/2005
Time: 7:52:11 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SIDFS01
A thread in Active Directory is waiting for the completion of a RPC made to
the following domain controller.
bd206802-6a5c-44b8-a445-00ffd744dc84._msdcs.structint.ad
get changes
b58
48
Active Directory has attempted to cancel the call and recover this thread.
User Action
If this condition continues, restart the domain controller.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
*****************************************************
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1232
Date: 11/1/2005
Time: 7:52:11 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SIDFS01
Active Directory attempted to perform a remote procedure call (RPC) to the
following server. The call timed out and was cancelled.
bd206802-6a5c-44b8-a445-00ffd744dc84._msdcs.structint.ad
48
b58
************************************
DCDIAG
Domain Controller Diagnosis
Done gathering initial info.
Doing initial required tests
Testing server: Structural-Integrity-Denver\sidfs01
Starting test: Connectivity
......................... sidfs01 passed test Connectivity
Doing primary tests
Testing server: Structural-Integrity-Denver\sidfs01
Starting test: Replications
From SISJDC02 to sidfs01
Naming Context: DC=ForestDnsZones,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 09:02:44.
The last success occurred at 2005-10-31 20:46:02.
8 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: DC=DomainDnsZones,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:59:40.
The last success occurred at 2005-10-31 20:46:02.
8 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: CN=Configuration,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:50:28.
The last success occurred at 2005-10-31 21:00:19.
17 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:56:36.
The last success occurred at 2005-10-31 23:00:33.
6 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
REPLICATION-RECEIVED LATENCY WARNING
sidfs01: Current time is 2005-11-01 09:02:58.
DC=ForestDnsZones,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:46:02.
Last replication recieved from SISJDC02 at 2005-10-31 20:46:02.
DC=DomainDnsZones,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:46:02.
Last replication recieved from SISJDC02 at 2005-10-31 20:46:02.
CN=Configuration,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:54:37.
Last replication recieved from SISJDC02 at 2005-10-31 21:00:19.
......................... sidfs01 passed test Replications
Starting test: NCSecDesc
......................... sidfs01 passed test NCSecDesc
Starting test: NetLogons
......................... sidfs01 passed test NetLogons
Starting test: Advertising
......................... sidfs01 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... sidfs01 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... sidfs01 passed test RidManager
Starting test: MachineAccount
......................... sidfs01 passed test MachineAccount
Starting test: Services
......................... sidfs01 passed test Services
Starting test: ObjectsReplicated
......................... sidfs01 passed test ObjectsReplicated
Starting test: frssysvol
......................... sidfs01 passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may
cause
Group Policy problems.
......................... sidfs01 failed test frsevent
Starting test: kccevent
......................... sidfs01 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00000457
Time Generated: 11/01/2005 08:42:39
(Event String could not be retrieved)
......................... sidfs01 failed test systemlog
Starting test: VerifyReferences
......................... sidfs01 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : structint
Starting test: CrossRefValidation
......................... structint passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... structint passed test CheckSDRefDom
Running enterprise tests on : structint.ad
Starting test: Intersite
......................... structint.ad passed test Intersite
Starting test: FsmoCheck
......................... structint.ad passed test FsmoCheck
SISJDC01
FSMO roles holder
First DC in Domain
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1566
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
All domain controllers in the following site that can replicate the
directory partition over this transport are currently unavailable.
CN=Structural-Integrity-Denver,CN=Sites,CN=Configuration,DC=structint,DC=ad
DC=DomainDnsZones,DC=structint,DC=ad
CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=structint,DC=ad
***************************************
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
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.
CN=Structural-Integrity-Denver,CN=Sites,CN=Configuration,DC=structint,DC=ad
***************************************
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
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.
CN=Structural-Integrity-Denver,CN=Sites,CN=Configuration,DC=structint,DC=ad
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
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.
CN=Structural-Integrity-Denver,CN=Sites,CN=Configuration,DC=structint,DC=ad
***************************************
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
The Knowledge Consistency Checker (KCC) has detected problems with the
following directory partition.
DC=ForestDnsZones,DC=structint,DC=ad
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
- 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.
***************************************
DCDIAG
Domain Controller Diagnosis
Done gathering initial info.
Doing initial required tests
Testing server: Structural-Integrity-San-Jose\SISJDC01
Starting test: Connectivity
......................... SISJDC01 passed test Connectivity
Doing primary tests
Testing server: Structural-Integrity-San-Jose\SISJDC01
Starting test: Replications
REPLICATION-RECEIVED LATENCY WARNING
SISJDC01: Current time is 2005-11-01 08:01:20.
DC=ForestDnsZones,DC=structint,DC=ad
Last replication recieved from sidfs01 at 2005-10-26 23:49:34.
DC=DomainDnsZones,DC=structint,DC=ad
Last replication recieved from sidfs01 at 2005-10-26 23:49:34.
CN=Schema,CN=Configuration,DC=structint,DC=ad
Last replication recieved from sidfs01 at 2005-10-26 23:49:34.
CN=Configuration,DC=structint,DC=ad
Last replication recieved from sidfs01 at 2005-10-26 23:49:34.
DC=structint,DC=ad
Last replication recieved from sidfs01 at 2005-10-26 23:49:33.
......................... SISJDC01 passed test Replications
Starting test: NCSecDesc
......................... SISJDC01 passed test NCSecDesc
Starting test: NetLogons
......................... SISJDC01 passed test NetLogons
Starting test: Advertising
......................... SISJDC01 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... SISJDC01 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... SISJDC01 passed test RidManager
Starting test: MachineAccount
......................... SISJDC01 passed test MachineAccount
Starting test: Services
......................... SISJDC01 passed test Services
Starting test: ObjectsReplicated
......................... SISJDC01 passed test ObjectsReplicated
Starting test: frssysvol
......................... SISJDC01 passed test frssysvol
Starting test: frsevent
......................... SISJDC01 passed test frsevent
Starting test: kccevent
An Warning Event occured. EventID: 0x8000061E
Time Generated: 11/01/2005 07:47:53
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 11/01/2005 07:47:53
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 11/01/2005 07:47:53
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 11/01/2005 07:47:53
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 11/01/2005 07:47:53
Event String: The Knowledge Consistency Checker (KCC) was
......................... SISJDC01 failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00000457
Time Generated: 11/01/2005 07:47:12
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 11/01/2005 07:47:12
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC0001B77
Time Generated: 11/01/2005 07:47:15
(Event String could not be retrieved)
......................... SISJDC01 failed test systemlog
Starting test: VerifyReferences
......................... SISJDC01 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : structint
Starting test: CrossRefValidation
......................... structint passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... structint passed test CheckSDRefDom
Running enterprise tests on : structint.ad
Starting test: Intersite
......................... structint.ad passed test Intersite
Starting test: FsmoCheck
......................... structint.ad passed test FsmoCheck
***************************************
Global results
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
NetBT_Tcpip_{00393C90-F937-4BFE-88F6-EDD6071B007F}
1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation
Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server
'192.168.11.4
1' and other DCs also have some of the names registered.
PASS - All the DNS entries for DC are registered on DNS server
'192.168.11.4
2' and other DCs also have some of the names registered.
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{00393C90-F937-4BFE-88F6-EDD6071B007F}
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{00393C90-F937-4BFE-88F6-EDD6071B007F}
The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Skipped
Note: run "netsh ipsec dynamic show /?" for more detailed information
The command completed successfully
SISJDC02
Exchange server
Intersite Bridgehead Server
Event Type: Warning
Event Source: NTDS Replication
Event Category: Replication
Event ID: 1862
Date: 10/31/2005
Time: 11:49:29 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC02
This is the replication status for the following directory partition on the
local domain controller.
DC=ForestDnsZones,DC=structint,DC=ad
The local domain controller has not received replication information from a
number of domain controllers in other sites within the configured latency
intverval.
1
24
The latency interval can be modified with the following registry key.
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator latency
error interval (hours)
To identify the domain controllers by name, install the support tools
included on the installation CD and run dcdiag.exe.
You can also use the support tool repadmin.exe to display the replication
latencies of the domain controllers in the forest. The command is "repadmin
/showvector /latency <partition-dn>".
KC
2005-11-01 20:35:02 UTC
Permalink
Indeed. All my DCs are w2k3 sp1 and I did see that hotfix available.

Please let me know how this works for you! Of course we won't know anything
for another week!

Are you applying this hotfix too all your DCs, or just the one affected and
the Bridgehead it communicates with?

-KC
Post by N.
I am having the exact same weekly issue. Do you have WIN 2003 SP1 insalled
on your DC's ? I have read about a hotfix that updates the TCPIP.SYS file
to correct a problem introduced in Win 2003 SP1. I will be implementing
this hot fix tonight. I'll let the group know how I make out.
http://support.microsoft.com/default.aspx?scid=898060
Post by KC
About every week AD replication begins to fail between my ONLY two sites and
my users at the remote office are unable to access network resources at the
main site.
I DCPROMO'd the remote office server about a month ago with no errors. Every
week since then replication fails and the only way to rectify the issue is to
reboot the DC at the main office. This has happened 4 times so far, a reboot
has solved the issue each time. The issue is that the bridgehead server is
also the Exchange server and requires advanced notice prior to a reboot.
2 DCs (SISJDC01 & SISJDC02) at the main site using intrasite replication
SISJDC01 is holding all FSMO roles
SISJDC02 is the brigehead for intersite replication (IP)
1 DC (SIDFS01) at the remote office using intersite replication
SIDFS01 is hosting a Global Catalog
-Verified VPN connectivity
-Increased the RPC time out value (article ID 830746)
-Toggled KCC on all DCs using the script (article ID 245610)
-Removed the Default site link and "hand made it"
-I changed the DNS of the remote office from itself to the 2 DCs at the main
site (to make sure that this server was not an "island"
-Toggled the netlogon service on the DC's
-Verified that Net View lists available resources on all DCs
-Checked replication topology on all NTDS listings
-Attempted to force replication fails with RPC errors
-Verified NetBios name resolution and added entries to the Host file for
each DC on each DC
-Installed FRSdiag but was lost in result errors.
Since there are only 3 DCs involved I have decided to include the error
messages from each server as well as a DCDiag and Netdiag from each.
*SIDFS01 is uable to run a Netdiag, I assume because I have its DNS pointed
the main office servers and not itself.
SIDFS01
Remote office server
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1188
Date: 11/1/2005
Time: 7:52:11 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SIDFS01
A thread in Active Directory is waiting for the completion of a RPC made to
the following domain controller.
bd206802-6a5c-44b8-a445-00ffd744dc84._msdcs.structint.ad
get changes
b58
48
Active Directory has attempted to cancel the call and recover this thread.
User Action
If this condition continues, restart the domain controller.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
*****************************************************
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1232
Date: 11/1/2005
Time: 7:52:11 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SIDFS01
Active Directory attempted to perform a remote procedure call (RPC) to the
following server. The call timed out and was cancelled.
bd206802-6a5c-44b8-a445-00ffd744dc84._msdcs.structint.ad
48
b58
************************************
DCDIAG
Domain Controller Diagnosis
Done gathering initial info.
Doing initial required tests
Testing server: Structural-Integrity-Denver\sidfs01
Starting test: Connectivity
......................... sidfs01 passed test Connectivity
Doing primary tests
Testing server: Structural-Integrity-Denver\sidfs01
Starting test: Replications
From SISJDC02 to sidfs01
Naming Context: DC=ForestDnsZones,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 09:02:44.
The last success occurred at 2005-10-31 20:46:02.
8 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: DC=DomainDnsZones,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:59:40.
The last success occurred at 2005-10-31 20:46:02.
8 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: CN=Configuration,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:50:28.
The last success occurred at 2005-10-31 21:00:19.
17 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:56:36.
The last success occurred at 2005-10-31 23:00:33.
6 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
REPLICATION-RECEIVED LATENCY WARNING
sidfs01: Current time is 2005-11-01 09:02:58.
DC=ForestDnsZones,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:46:02.
Last replication recieved from SISJDC02 at 2005-10-31 20:46:02.
DC=DomainDnsZones,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:46:02.
Last replication recieved from SISJDC02 at 2005-10-31 20:46:02.
CN=Configuration,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:54:37.
Last replication recieved from SISJDC02 at 2005-10-31 21:00:19.
......................... sidfs01 passed test Replications
Starting test: NCSecDesc
......................... sidfs01 passed test NCSecDesc
Starting test: NetLogons
......................... sidfs01 passed test NetLogons
Starting test: Advertising
......................... sidfs01 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... sidfs01 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... sidfs01 passed test RidManager
Starting test: MachineAccount
......................... sidfs01 passed test MachineAccount
Starting test: Services
......................... sidfs01 passed test Services
Starting test: ObjectsReplicated
......................... sidfs01 passed test ObjectsReplicated
Starting test: frssysvol
......................... sidfs01 passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may
cause
Group Policy problems.
......................... sidfs01 failed test frsevent
Starting test: kccevent
......................... sidfs01 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00000457
Time Generated: 11/01/2005 08:42:39
(Event String could not be retrieved)
......................... sidfs01 failed test systemlog
Starting test: VerifyReferences
......................... sidfs01 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : structint
Starting test: CrossRefValidation
......................... structint passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... structint passed test CheckSDRefDom
Running enterprise tests on : structint.ad
Starting test: Intersite
......................... structint.ad passed test Intersite
Starting test: FsmoCheck
......................... structint.ad passed test FsmoCheck
SISJDC01
FSMO roles holder
First DC in Domain
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1566
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
All domain controllers in the following site that can replicate the
directory partition over this transport are currently unavailable.
CN=Structural-Integrity-Denver,CN=Sites,CN=Configuration,DC=structint,DC=ad
DC=DomainDnsZones,DC=structint,DC=ad
CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=structint,DC=ad
N.
2005-11-01 22:56:43 UTC
Permalink
I have implemented this hotfix on all (2) of my DC's with SP1.
Post by KC
Indeed. All my DCs are w2k3 sp1 and I did see that hotfix available.
Please let me know how this works for you! Of course we won't know anything
for another week!
Are you applying this hotfix too all your DCs, or just the one affected and
the Bridgehead it communicates with?
-KC
Post by N.
I am having the exact same weekly issue. Do you have WIN 2003 SP1 insalled
on your DC's ? I have read about a hotfix that updates the TCPIP.SYS file
to correct a problem introduced in Win 2003 SP1. I will be implementing
this hot fix tonight. I'll let the group know how I make out.
http://support.microsoft.com/default.aspx?scid=898060
Post by KC
About every week AD replication begins to fail between my ONLY two
sites
and
my users at the remote office are unable to access network resources at the
main site.
I DCPROMO'd the remote office server about a month ago with no errors. Every
week since then replication fails and the only way to rectify the issue
is
to
reboot the DC at the main office. This has happened 4 times so far, a reboot
has solved the issue each time. The issue is that the bridgehead server is
also the Exchange server and requires advanced notice prior to a reboot.
2 DCs (SISJDC01 & SISJDC02) at the main site using intrasite replication
SISJDC01 is holding all FSMO roles
SISJDC02 is the brigehead for intersite replication (IP)
1 DC (SIDFS01) at the remote office using intersite replication
SIDFS01 is hosting a Global Catalog
-Verified VPN connectivity
-Increased the RPC time out value (article ID 830746)
-Toggled KCC on all DCs using the script (article ID 245610)
-Removed the Default site link and "hand made it"
-I changed the DNS of the remote office from itself to the 2 DCs at the main
site (to make sure that this server was not an "island"
-Toggled the netlogon service on the DC's
-Verified that Net View lists available resources on all DCs
-Checked replication topology on all NTDS listings
-Attempted to force replication fails with RPC errors
-Verified NetBios name resolution and added entries to the Host file for
each DC on each DC
-Installed FRSdiag but was lost in result errors.
Since there are only 3 DCs involved I have decided to include the error
messages from each server as well as a DCDiag and Netdiag from each.
*SIDFS01 is uable to run a Netdiag, I assume because I have its DNS pointed
the main office servers and not itself.
SIDFS01
Remote office server
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1188
Date: 11/1/2005
Time: 7:52:11 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SIDFS01
A thread in Active Directory is waiting for the completion of a RPC
made
to
the following domain controller.
bd206802-6a5c-44b8-a445-00ffd744dc84._msdcs.structint.ad
get changes
b58
48
Active Directory has attempted to cancel the call and recover this thread.
User Action
If this condition continues, restart the domain controller.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
*****************************************************
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1232
Date: 11/1/2005
Time: 7:52:11 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SIDFS01
Active Directory attempted to perform a remote procedure call (RPC) to the
following server. The call timed out and was cancelled.
bd206802-6a5c-44b8-a445-00ffd744dc84._msdcs.structint.ad
48
b58
************************************
DCDIAG
Domain Controller Diagnosis
Done gathering initial info.
Doing initial required tests
Testing server: Structural-Integrity-Denver\sidfs01
Starting test: Connectivity
......................... sidfs01 passed test Connectivity
Doing primary tests
Testing server: Structural-Integrity-Denver\sidfs01
Starting test: Replications
From SISJDC02 to sidfs01
Naming Context: DC=ForestDnsZones,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 09:02:44.
The last success occurred at 2005-10-31 20:46:02.
8 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: DC=DomainDnsZones,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:59:40.
The last success occurred at 2005-10-31 20:46:02.
8 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: CN=Configuration,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:50:28.
The last success occurred at 2005-10-31 21:00:19.
17 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:56:36.
The last success occurred at 2005-10-31 23:00:33.
6 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
REPLICATION-RECEIVED LATENCY WARNING
sidfs01: Current time is 2005-11-01 09:02:58.
DC=ForestDnsZones,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:46:02.
Last replication recieved from SISJDC02 at 2005-10-31 20:46:02.
DC=DomainDnsZones,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:46:02.
Last replication recieved from SISJDC02 at 2005-10-31 20:46:02.
CN=Configuration,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:54:37.
Last replication recieved from SISJDC02 at 2005-10-31 21:00:19.
......................... sidfs01 passed test Replications
Starting test: NCSecDesc
......................... sidfs01 passed test NCSecDesc
Starting test: NetLogons
......................... sidfs01 passed test NetLogons
Starting test: Advertising
......................... sidfs01 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... sidfs01 passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... sidfs01 passed test RidManager
Starting test: MachineAccount
......................... sidfs01 passed test MachineAccount
Starting test: Services
......................... sidfs01 passed test Services
Starting test: ObjectsReplicated
......................... sidfs01 passed test ObjectsReplicated
Starting test: frssysvol
......................... sidfs01 passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours
after
the
SYSVOL has been shared. Failing SYSVOL replication problems may
cause
Group Policy problems.
......................... sidfs01 failed test frsevent
Starting test: kccevent
......................... sidfs01 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00000457
Time Generated: 11/01/2005 08:42:39
(Event String could not be retrieved)
......................... sidfs01 failed test systemlog
Starting test: VerifyReferences
......................... sidfs01 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test
CheckSDRefDom
Running partition tests on : structint
Starting test: CrossRefValidation
......................... structint passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... structint passed test CheckSDRefDom
Running enterprise tests on : structint.ad
Starting test: Intersite
......................... structint.ad passed test Intersite
Starting test: FsmoCheck
......................... structint.ad passed test FsmoCheck
SISJDC01
FSMO roles holder
First DC in Domain
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1566
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
All domain controllers in the following site that can replicate the
directory partition over this transport are currently unavailable.
CN=Structural-Integrity-Denver,CN=Sites,CN=Configuration,DC=structint,DC=ad
DC=DomainDnsZones,DC=structint,DC=ad
CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=structint,DC=ad
N.
2005-11-07 14:31:56 UTC
Permalink
Welp, It's Monday morning. I've successfully logged into all my domains
from local and remote clients. Replication is working, no freezing, no
reboots :)
It seems this hotfix has fixed the issue.
Post by N.
I have implemented this hotfix on all (2) of my DC's with SP1.
Post by KC
Indeed. All my DCs are w2k3 sp1 and I did see that hotfix available.
Please let me know how this works for you! Of course we won't know anything
for another week!
Are you applying this hotfix too all your DCs, or just the one affected and
the Bridgehead it communicates with?
-KC
Post by N.
I am having the exact same weekly issue. Do you have WIN 2003 SP1 insalled
on your DC's ? I have read about a hotfix that updates the TCPIP.SYS file
to correct a problem introduced in Win 2003 SP1. I will be implementing
this hot fix tonight. I'll let the group know how I make out.
http://support.microsoft.com/default.aspx?scid=898060
Post by KC
About every week AD replication begins to fail between my ONLY two
sites
and
my users at the remote office are unable to access network resources
at
the
main site.
I DCPROMO'd the remote office server about a month ago with no errors. Every
week since then replication fails and the only way to rectify the
issue is
to
reboot the DC at the main office. This has happened 4 times so far, a reboot
has solved the issue each time. The issue is that the bridgehead server is
also the Exchange server and requires advanced notice prior to a reboot.
2 DCs (SISJDC01 & SISJDC02) at the main site using intrasite replication
SISJDC01 is holding all FSMO roles
SISJDC02 is the brigehead for intersite replication (IP)
1 DC (SIDFS01) at the remote office using intersite replication
SIDFS01 is hosting a Global Catalog
-Verified VPN connectivity
-Increased the RPC time out value (article ID 830746)
-Toggled KCC on all DCs using the script (article ID 245610)
-Removed the Default site link and "hand made it"
-I changed the DNS of the remote office from itself to the 2 DCs at
the
main
site (to make sure that this server was not an "island"
-Toggled the netlogon service on the DC's
-Verified that Net View lists available resources on all DCs
-Checked replication topology on all NTDS listings
-Attempted to force replication fails with RPC errors
-Verified NetBios name resolution and added entries to the Host file for
each DC on each DC
-Installed FRSdiag but was lost in result errors.
Since there are only 3 DCs involved I have decided to include the error
messages from each server as well as a DCDiag and Netdiag from each.
*SIDFS01 is uable to run a Netdiag, I assume because I have its DNS pointed
the main office servers and not itself.
SIDFS01
Remote office server
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1188
Date: 11/1/2005
Time: 7:52:11 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SIDFS01
A thread in Active Directory is waiting for the completion of a RPC
made
to
the following domain controller.
bd206802-6a5c-44b8-a445-00ffd744dc84._msdcs.structint.ad
get changes
b58
48
Active Directory has attempted to cancel the call and recover this thread.
User Action
If this condition continues, restart the domain controller.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
*****************************************************
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1232
Date: 11/1/2005
Time: 7:52:11 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SIDFS01
Active Directory attempted to perform a remote procedure call (RPC) to the
following server. The call timed out and was cancelled.
bd206802-6a5c-44b8-a445-00ffd744dc84._msdcs.structint.ad
48
b58
************************************
DCDIAG
Domain Controller Diagnosis
Done gathering initial info.
Doing initial required tests
Testing server: Structural-Integrity-Denver\sidfs01
Starting test: Connectivity
......................... sidfs01 passed test Connectivity
Doing primary tests
Testing server: Structural-Integrity-Denver\sidfs01
Starting test: Replications
From SISJDC02 to sidfs01
Naming Context: DC=ForestDnsZones,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 09:02:44.
The last success occurred at 2005-10-31 20:46:02.
8 failures have occurred since the last success.
The replication RPC call executed for too long at the
server
and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: DC=DomainDnsZones,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:59:40.
The last success occurred at 2005-10-31 20:46:02.
8 failures have occurred since the last success.
The replication RPC call executed for too long at the
server
and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: CN=Configuration,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:50:28.
The last success occurred at 2005-10-31 21:00:19.
17 failures have occurred since the last success.
The replication RPC call executed for too long at the
server
and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:56:36.
The last success occurred at 2005-10-31 23:00:33.
6 failures have occurred since the last success.
The replication RPC call executed for too long at the
server
and
was cancelled.
Check load and resouce usage on SISJDC02.
REPLICATION-RECEIVED LATENCY WARNING
sidfs01: Current time is 2005-11-01 09:02:58.
DC=ForestDnsZones,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:46:02.
Last replication recieved from SISJDC02 at 2005-10-31 20:46:02.
DC=DomainDnsZones,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:46:02.
Last replication recieved from SISJDC02 at 2005-10-31 20:46:02.
CN=Configuration,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:54:37.
Last replication recieved from SISJDC02 at 2005-10-31 21:00:19.
......................... sidfs01 passed test Replications
Starting test: NCSecDesc
......................... sidfs01 passed test NCSecDesc
Starting test: NetLogons
......................... sidfs01 passed test NetLogons
Starting test: Advertising
......................... sidfs01 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... sidfs01 passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... sidfs01 passed test RidManager
Starting test: MachineAccount
......................... sidfs01 passed test MachineAccount
Starting test: Services
......................... sidfs01 passed test Services
Starting test: ObjectsReplicated
......................... sidfs01 passed test
ObjectsReplicated
Starting test: frssysvol
......................... sidfs01 passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours
after
the
SYSVOL has been shared. Failing SYSVOL replication problems may
cause
Group Policy problems.
......................... sidfs01 failed test frsevent
Starting test: kccevent
......................... sidfs01 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00000457
Time Generated: 11/01/2005 08:42:39
(Event String could not be retrieved)
......................... sidfs01 failed test systemlog
Starting test: VerifyReferences
......................... sidfs01 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : structint
Starting test: CrossRefValidation
......................... structint passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... structint passed test CheckSDRefDom
Running enterprise tests on : structint.ad
Starting test: Intersite
......................... structint.ad passed test Intersite
Starting test: FsmoCheck
......................... structint.ad passed test FsmoCheck
SISJDC01
FSMO roles holder
First DC in Domain
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1566
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
All domain controllers in the following site that can replicate the
directory partition over this transport are currently unavailable.
CN=Structural-Integrity-Denver,CN=Sites,CN=Configuration,DC=structint,DC=ad
DC=DomainDnsZones,DC=structint,DC=ad
CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=structint,DC=ad
KC
2005-11-07 19:45:11 UTC
Permalink
I took the plunge as well with the hotfix last week. In fact I called and
spoke with a technician prior to applying the hotfix. Microsoft indicated
that this would be the first step in troubleshooting this type of replication
issue. So I went for it.

I applied the hotfix the night of 11/1 also. Not a single replication hickup
since this hotfix was applied. (I still have my fingers crossed!)

I hope this helps the next person that experiences this issue!

The link to the hotfix can be found here:
http://support.microsoft.com/default.aspx?scid=898060
Post by N.
Welp, It's Monday morning. I've successfully logged into all my domains
from local and remote clients. Replication is working, no freezing, no
reboots :)
It seems this hotfix has fixed the issue.
Post by N.
I have implemented this hotfix on all (2) of my DC's with SP1.
Post by KC
Indeed. All my DCs are w2k3 sp1 and I did see that hotfix available.
Please let me know how this works for you! Of course we won't know anything
for another week!
Are you applying this hotfix too all your DCs, or just the one affected and
the Bridgehead it communicates with?
-KC
Post by N.
I am having the exact same weekly issue. Do you have WIN 2003 SP1 insalled
on your DC's ? I have read about a hotfix that updates the TCPIP.SYS file
to correct a problem introduced in Win 2003 SP1. I will be implementing
this hot fix tonight. I'll let the group know how I make out.
http://support.microsoft.com/default.aspx?scid=898060
Post by KC
About every week AD replication begins to fail between my ONLY two
sites
and
my users at the remote office are unable to access network resources
at
the
main site.
I DCPROMO'd the remote office server about a month ago with no errors. Every
week since then replication fails and the only way to rectify the
issue is
to
reboot the DC at the main office. This has happened 4 times so far, a reboot
has solved the issue each time. The issue is that the bridgehead server is
also the Exchange server and requires advanced notice prior to a reboot.
2 DCs (SISJDC01 & SISJDC02) at the main site using intrasite replication
SISJDC01 is holding all FSMO roles
SISJDC02 is the brigehead for intersite replication (IP)
1 DC (SIDFS01) at the remote office using intersite replication
SIDFS01 is hosting a Global Catalog
-Verified VPN connectivity
-Increased the RPC time out value (article ID 830746)
-Toggled KCC on all DCs using the script (article ID 245610)
-Removed the Default site link and "hand made it"
-I changed the DNS of the remote office from itself to the 2 DCs at
the
main
site (to make sure that this server was not an "island"
-Toggled the netlogon service on the DC's
-Verified that Net View lists available resources on all DCs
-Checked replication topology on all NTDS listings
-Attempted to force replication fails with RPC errors
-Verified NetBios name resolution and added entries to the Host file for
each DC on each DC
-Installed FRSdiag but was lost in result errors.
Since there are only 3 DCs involved I have decided to include the error
messages from each server as well as a DCDiag and Netdiag from each.
*SIDFS01 is uable to run a Netdiag, I assume because I have its DNS pointed
the main office servers and not itself.
SIDFS01
Remote office server
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1188
Date: 11/1/2005
Time: 7:52:11 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SIDFS01
A thread in Active Directory is waiting for the completion of a RPC
made
to
the following domain controller.
bd206802-6a5c-44b8-a445-00ffd744dc84._msdcs.structint.ad
get changes
b58
48
Active Directory has attempted to cancel the call and recover this thread.
User Action
If this condition continues, restart the domain controller.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
*****************************************************
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1232
Date: 11/1/2005
Time: 7:52:11 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SIDFS01
Active Directory attempted to perform a remote procedure call (RPC) to the
following server. The call timed out and was cancelled.
bd206802-6a5c-44b8-a445-00ffd744dc84._msdcs.structint.ad
48
b58
************************************
DCDIAG
Domain Controller Diagnosis
Done gathering initial info.
Doing initial required tests
Testing server: Structural-Integrity-Denver\sidfs01
Starting test: Connectivity
......................... sidfs01 passed test Connectivity
Doing primary tests
Testing server: Structural-Integrity-Denver\sidfs01
Starting test: Replications
From SISJDC02 to sidfs01
Naming Context: DC=ForestDnsZones,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 09:02:44.
The last success occurred at 2005-10-31 20:46:02.
8 failures have occurred since the last success.
The replication RPC call executed for too long at the
server
and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: DC=DomainDnsZones,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:59:40.
The last success occurred at 2005-10-31 20:46:02.
8 failures have occurred since the last success.
The replication RPC call executed for too long at the
server
and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: CN=Configuration,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:50:28.
The last success occurred at 2005-10-31 21:00:19.
17 failures have occurred since the last success.
The replication RPC call executed for too long at the
server
and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:56:36.
The last success occurred at 2005-10-31 23:00:33.
6 failures have occurred since the last success.
The replication RPC call executed for too long at the
server
and
was cancelled.
Check load and resouce usage on SISJDC02.
REPLICATION-RECEIVED LATENCY WARNING
sidfs01: Current time is 2005-11-01 09:02:58.
DC=ForestDnsZones,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:46:02.
Last replication recieved from SISJDC02 at 2005-10-31 20:46:02.
DC=DomainDnsZones,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:46:02.
Last replication recieved from SISJDC02 at 2005-10-31 20:46:02.
CN=Configuration,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:54:37.
Last replication recieved from SISJDC02 at 2005-10-31 21:00:19.
......................... sidfs01 passed test Replications
Starting test: NCSecDesc
......................... sidfs01 passed test NCSecDesc
Starting test: NetLogons
......................... sidfs01 passed test NetLogons
Starting test: Advertising
......................... sidfs01 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... sidfs01 passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... sidfs01 passed test RidManager
Starting test: MachineAccount
......................... sidfs01 passed test MachineAccount
Starting test: Services
......................... sidfs01 passed test Services
Starting test: ObjectsReplicated
......................... sidfs01 passed test
ObjectsReplicated
Starting test: frssysvol
......................... sidfs01 passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours
after
the
SYSVOL has been shared. Failing SYSVOL replication problems may
cause
Group Policy problems.
......................... sidfs01 failed test frsevent
Starting test: kccevent
......................... sidfs01 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00000457
Time Generated: 11/01/2005 08:42:39
(Event String could not be retrieved)
......................... sidfs01 failed test systemlog
Starting test: VerifyReferences
......................... sidfs01 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
Juanan
2005-12-27 16:13:48 UTC
Permalink
Hello, we had exactly the same problems. Our schema master and intersite
topology replicator and global catalogs in a site were update to SP1. Then we
started to notice a lot of intersite replications failures. The hotfix that
Article ID 898060 talks about fixed all those replications issues. Now
everithing works fine again...uffff!!!

And notice, just FYI, that office live communications server 2005 stops
working with events 20491, 16417 and 12299. Obviously, that has been fixed
too.

Thanks a lot!
Post by KC
About every week AD replication begins to fail between my ONLY two sites and
my users at the remote office are unable to access network resources at the
main site.
I DCPROMO'd the remote office server about a month ago with no errors. Every
week since then replication fails and the only way to rectify the issue is to
reboot the DC at the main office. This has happened 4 times so far, a reboot
has solved the issue each time. The issue is that the bridgehead server is
also the Exchange server and requires advanced notice prior to a reboot.
2 DCs (SISJDC01 & SISJDC02) at the main site using intrasite replication
SISJDC01 is holding all FSMO roles
SISJDC02 is the brigehead for intersite replication (IP)
1 DC (SIDFS01) at the remote office using intersite replication
SIDFS01 is hosting a Global Catalog
-Verified VPN connectivity
-Increased the RPC time out value (article ID 830746)
-Toggled KCC on all DCs using the script (article ID 245610)
-Removed the Default site link and “hand made it”
-I changed the DNS of the remote office from itself to the 2 DCs at the main
site (to make sure that this server was not an “island”
-Toggled the netlogon service on the DC’s
-Verified that Net View lists available resources on all DCs
-Checked replication topology on all NTDS listings
-Attempted to force replication fails with RPC errors
-Verified NetBios name resolution and added entries to the Host file for
each DC on each DC
-Installed FRSdiag but was lost in result errors.
Since there are only 3 DCs involved I have decided to include the error
messages from each server as well as a DCDiag and Netdiag from each.
*SIDFS01 is uable to run a Netdiag, I assume because I have its DNS pointed
the main office servers and not itself.
SIDFS01
Remote office server
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1188
Date: 11/1/2005
Time: 7:52:11 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SIDFS01
A thread in Active Directory is waiting for the completion of a RPC made to
the following domain controller.
bd206802-6a5c-44b8-a445-00ffd744dc84._msdcs.structint.ad
get changes
b58
48
Active Directory has attempted to cancel the call and recover this thread.
User Action
If this condition continues, restart the domain controller.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
*****************************************************
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1232
Date: 11/1/2005
Time: 7:52:11 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SIDFS01
Active Directory attempted to perform a remote procedure call (RPC) to the
following server. The call timed out and was cancelled.
bd206802-6a5c-44b8-a445-00ffd744dc84._msdcs.structint.ad
48
b58
************************************
DCDIAG
Domain Controller Diagnosis
Done gathering initial info.
Doing initial required tests
Testing server: Structural-Integrity-Denver\sidfs01
Starting test: Connectivity
......................... sidfs01 passed test Connectivity
Doing primary tests
Testing server: Structural-Integrity-Denver\sidfs01
Starting test: Replications
From SISJDC02 to sidfs01
Naming Context: DC=ForestDnsZones,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 09:02:44.
The last success occurred at 2005-10-31 20:46:02.
8 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: DC=DomainDnsZones,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:59:40.
The last success occurred at 2005-10-31 20:46:02.
8 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: CN=Configuration,DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:50:28.
The last success occurred at 2005-10-31 21:00:19.
17 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
From SISJDC02 to sidfs01
Naming Context: DC=structint,DC=ad
The remote procedure call failed.
The failure occurred at 2005-11-01 08:56:36.
The last success occurred at 2005-10-31 23:00:33.
6 failures have occurred since the last success.
The replication RPC call executed for too long at the server and
was cancelled.
Check load and resouce usage on SISJDC02.
REPLICATION-RECEIVED LATENCY WARNING
sidfs01: Current time is 2005-11-01 09:02:58.
DC=ForestDnsZones,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:46:02.
Last replication recieved from SISJDC02 at 2005-10-31 20:46:02.
DC=DomainDnsZones,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:46:02.
Last replication recieved from SISJDC02 at 2005-10-31 20:46:02.
CN=Configuration,DC=structint,DC=ad
Last replication recieved from SISJDC01 at 2005-10-31 20:54:37.
Last replication recieved from SISJDC02 at 2005-10-31 21:00:19.
......................... sidfs01 passed test Replications
Starting test: NCSecDesc
......................... sidfs01 passed test NCSecDesc
Starting test: NetLogons
......................... sidfs01 passed test NetLogons
Starting test: Advertising
......................... sidfs01 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... sidfs01 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... sidfs01 passed test RidManager
Starting test: MachineAccount
......................... sidfs01 passed test MachineAccount
Starting test: Services
......................... sidfs01 passed test Services
Starting test: ObjectsReplicated
......................... sidfs01 passed test ObjectsReplicated
Starting test: frssysvol
......................... sidfs01 passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may
cause
Group Policy problems.
......................... sidfs01 failed test frsevent
Starting test: kccevent
......................... sidfs01 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00000457
Time Generated: 11/01/2005 08:42:39
(Event String could not be retrieved)
......................... sidfs01 failed test systemlog
Starting test: VerifyReferences
......................... sidfs01 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : structint
Starting test: CrossRefValidation
......................... structint passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... structint passed test CheckSDRefDom
Running enterprise tests on : structint.ad
Starting test: Intersite
......................... structint.ad passed test Intersite
Starting test: FsmoCheck
......................... structint.ad passed test FsmoCheck
SISJDC01
FSMO roles holder
First DC in Domain
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1566
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
All domain controllers in the following site that can replicate the
directory partition over this transport are currently unavailable.
CN=Structural-Integrity-Denver,CN=Sites,CN=Configuration,DC=structint,DC=ad
DC=DomainDnsZones,DC=structint,DC=ad
CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=structint,DC=ad
***************************************
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
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.
CN=Structural-Integrity-Denver,CN=Sites,CN=Configuration,DC=structint,DC=ad
***************************************
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 10/31/2005
Time: 6:20:06 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SISJDC01
The Knowledge Consistency Checker (KCC) was unable to form a complete
Continue reading on narkive:
Loading...