Replication on my DFS has stopped. DC1 seems like it's current and DC2 stale.
Here is my dcdiag - can anyone help? I'm panicking.
Both are Server 2012 boxes.
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
* Verifying that the local machine DC2, is a Directory Server.
Home Server = DC2
* Connecting to directory service on server DC2.
* Identified AD Forest.
Collecting AD specific global data
* Collecting site info.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=ccwtech,DC=local,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
The previous call succeeded
Iterating through the sites
Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ccwtech,DC=local
Getting ISTG and options for the site
* Identifying all servers.
Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=ccwtech,DC=local,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
The previous call succeeded....
The previous call succeeded
Iterating through the list of servers
Getting information for the server CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ccwtech,DC=local
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
Getting information for the server CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ccwtech,DC=local
objectGuid obtained
InvocationID obtained
dnsHostname obtained
site info obtained
All the info for the server collected
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC2
Starting test: Connectivity
* Active Directory LDAP Services Check
Determining IP4 connectivity
* Active Directory RPC Services Check
......................... DC2 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC2
Starting test: Advertising
The DC DC2 is advertising itself as a DC and having a DS.
The DC DC2 is advertising as an LDAP server
The DC DC2 is advertising as having a writeable directory
The DC DC2 is advertising as a Key Distribution Center
The DC DC2 is advertising as a time server
The DS DC2 is advertising as a GC.
......................... DC2 passed test Advertising
Test omitted by user request: CheckSecurityError
Test omitted by user request: CutoffServers
Starting test: FrsEvent
* The File Replication Service Event log test
Skip the test because the server is running DFSR.
......................... DC2 passed test FrsEvent
Starting test: DFSREvent
The DFS Replication Event Log.
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.
A warning event occurred. EventID: 0x80001396
Time Generated: 05/26/2013 01:00:38
Event String:
The DFS Replication service is stopping communication with partner DC1 for replication group Domain System Volume due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9033 (The request was cancelled by a shutdown)
Connection ID: 86BAEFAD-852A-447F-8052-7702DFABA7EE
Replication Group ID: D76C581A-8BEF-44FF-BDCE-E97C15821D74
A warning event occurred. EventID: 0x80001396
Time Generated: 05/26/2013 01:00:38
Event String:
The DFS Replication service is stopping communication with partner DC1 for replication group ccwtech.local\shared\dfs due to an error. The service will retry the connection periodically.
Additional Information:
Error: 9033 (The request was cancelled by a shutdown)
Connection ID: CC164875-E688-4F27-AAC9-5282665D919B
Replication Group ID: 4BBEEA61-74D7-449C-AACC-F48D5687E273
......................... DC2 passed test DFSREvent
Starting test: SysVolCheck
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... DC2 passed test SysVolCheck
Starting test: KccEvent
* The KCC Event log test
Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
......................... DC2 passed test KccEvent
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ccwtech,DC=local
Role Domain Owner = CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ccwtech,DC=local
Role PDC Owner = CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ccwtech,DC=local
Role Rid Owner = CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ccwtech,DC=local
Role Infrastructure Update Owner = CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ccwtech,DC=local
......................... DC2 passed test KnowsOfRoleHolders
Starting test: MachineAccount
Checking machine account for DC DC2 on DC DC2.
* SPN found :LDAP/DC2.ccwtech.local/ccwtech.local
* SPN found :LDAP/DC2.ccwtech.local
* SPN found :LDAP/DC2
* SPN found :LDAP/DC2.ccwtech.local/CCWTECH
* SPN found :LDAP/854c9c3a-47f9-4fca-a019-1016e9710daa._msdcs.ccwtech.local
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/854c9c3a-47f9-4fca-a019-1016e9710daa/ccwtech.local
* SPN found :HOST/DC2.ccwtech.local/ccwtech.local
* SPN found :HOST/DC2.ccwtech.local
* SPN found :HOST/DC2
* SPN found :HOST/DC2.ccwtech.local/CCWTECH
* SPN found :GC/DC2.ccwtech.local/ccwtech.local
......................... DC2 passed test MachineAccount
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC DC2.
* Security Permissions Check for
DC=ForestDnsZones,DC=ccwtech,DC=local
(NDNC,Version 3)
* Security Permissions Check for
DC=DomainDnsZones,DC=ccwtech,DC=local
(NDNC,Version 3)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=ccwtech,DC=local
(Schema,Version 3)
* Security Permissions Check for
CN=Configuration,DC=ccwtech,DC=local
(Configuration,Version 3)
* Security Permissions Check for
DC=ccwtech,DC=local
(Domain,Version 3)
......................... DC2 passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\DC2\netlogon
Verified share \\DC2\sysvol
......................... DC2 passed test NetLogons
Starting test: ObjectsReplicated
DC2 is in domain DC=ccwtech,DC=local
Checking for CN=DC2,OU=Domain Controllers,DC=ccwtech,DC=local in domain DC=ccwtech,DC=local on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ccwtech,DC=local in domain CN=Configuration,DC=ccwtech,DC=local on 1 servers
Object is up-to-date on all servers.
......................... DC2 passed test ObjectsReplicated
Test omitted by user request: OutboundSecureChannels
Starting test: Replications
* Replications Check
* Replication Latency Check
DC=ForestDnsZones,DC=ccwtech,DC=local
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=DomainDnsZones,DC=ccwtech,DC=local
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Schema,CN=Configuration,DC=ccwtech,DC=local
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Configuration,DC=ccwtech,DC=local
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=ccwtech,DC=local
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
......................... DC2 passed test Replications
Starting test: RidManager
* Available RID Pool for the Domain is 3101 to 1073741823
* DC1.ccwtech.local is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 2601 to 3100
* rIDPreviousAllocationPool is 2601 to 3100
* rIDNextRID: 2602
......................... DC2 passed test RidManager
Starting test: Services
* Checking Service: EventSystem
* Checking Service: RpcSs
* Checking Service: NTDS
* Checking Service: DnsCache
* Checking Service: DFSR
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: w32time
* Checking Service: NETLOGON
......................... DC2 passed test Services
Starting test: SystemLog
* The System Event log test
A warning event occurred. EventID: 0x00000458
Time Generated: 05/26/2013 14:59:26
Event String:
The Group Policy Client Side Extension Group Policy Drive Maps was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish completely before the next startup or logon for this user, and this may result in slow startup and boot performance.
Found no errors in "System" Event log in the last 60 minutes.
......................... DC2 passed test SystemLog
Test omitted by user request: Topology
Test omitted by user request: VerifyEnterpriseReferences
Starting test: VerifyReferences
The system object reference (serverReference)
CN=DC2,OU=Domain Controllers,DC=ccwtech,DC=local and backlink on
CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ccwtech,DC=local
are correct.
The system object reference (serverReferenceBL)
CN=DC2,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=ccwtech,DC=local
and backlink on
CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ccwtech,DC=local
are correct.
The system object reference (msDFSR-ComputerReferenceBL)
CN=11dfb26b-dbe7-4a3d-a905-cf452f02d7a3,CN=Topology,CN=ccwtech.local\\shared\\dfs,CN=DFSR-GlobalSettings,CN=System,DC=ccwtech,DC=local
and backlink on CN=DC2,OU=Domain Controllers,DC=ccwtech,DC=local are
correct.
......................... DC2 passed test VerifyReferences
Test omitted by user request: VerifyReplicas
Test omitted by user request: DNS
Test omitted by user request: DNS
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Running partition tests on : ccwtech
Starting test: CheckSDRefDom
......................... ccwtech passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ccwtech passed test CrossRefValidation
Running enterprise tests on : ccwtech.local
Test omitted by user request: DNS
Test omitted by user request: DNS
Starting test: LocatorCheck
GC Name: \\DC2.ccwtech.local
Locator Flags: 0xe00071fc
PDC Name: \\DC1.ccwtech.local
Locator Flags: 0xe00073fd
Time Server Name: \\DC2.ccwtech.local
Locator Flags: 0xe00071fc
Preferred Time Server Name: \\DC1.ccwtech.local
Locator Flags: 0xe00073fd
KDC Name: \\DC2.ccwtech.local
Locator Flags: 0xe00071fc
......................... ccwtech.local passed test LocatorCheck
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... ccwtech.local passed test Intersite
DFS Replication Health Report (Show All)
Data collected on: Sunday, May 26, 2013 at 4:03:02 PM (GMT-7:00)
Replication Group: ccwtech.local\shared\dfs (ccwtech.local)
Reference member: DC1 (dc1.ccwtech.local)
Server scope: Selected 2 of 2 servers
DFS Replication bandwidth savings: 0.00%
Server health: Servers with no errors or warnings (0) Servers unavailable for reporting (0)
Servers with DFS Replication errors (2) Servers with DFS Replication warnings (2)
Report Loading. Please wait . . .
ERRORS (2 servers with errors)(Hide All)
DC1 (1 error) (View Server Details)
The DFS Replication service is restarting frequently.
DC2 (1 error) (View Server Details)
The DFS Replication service is restarting frequently.
WARNINGS (2 servers with warnings)(Hide All)
DC1 (1 warning) (View Server Details)
Reference member returned no replicated folders.
DC2 (1 warning) (View Server Details)
This member is waiting for initial replication for replicated folder DFS.
SERVERS UNAVAILABLE FOR REPORTING (All servers reporting)
SERVER DETAILS (2 servers)(Hide All)
Rendering content. Please wait . . .
DC1(Hide All)
DNS name: dc1.ccwtech.local
Domain name: ccwtech.local
Reference domain controller: DC1.ccwtech.local
IP address: fe80::5d5e:dc10:3e3c:74b0%20,10.0.0.10
Site: Default-First-Site-Name
Time zone: (GMT-7:00)
ERRORS (There is 1 error to report)
The DFS Replication service is restarting frequently.
Affected replicated folders: All replicated folders on this server.
Description: The DFS Replication service has restarted 5 times in the past 7 days. This problem can affect the replication of all replicated folders to and from this server. Event ID: 1004
Last occurred: Friday, May 24, 2013 at 1:10:54 PM (GMT-7:00)
Suggested action: If you restarted the service manually, you can safely ignore this message. For information about troubleshooting frequent service restart issues, see The Microsoft Web Site.
WARNINGS (There is 1 warning to report)
Reference member returned no replicated folders.
Description: Backlog calculations cannot be performed because the reference member returned zero replicated folders.
Last occurred: Sunday, May 26, 2013 at 4:03:03 PM (GMT-7:00)
Suggested action: For information about troubleshooting backlog problems, see The Microsoft Web Site.
INFORMATIONAL
Service state: Running
DFS Replication service uptime: 2 days 2 hr.
DFS Replication service version: 6.2.9200.16384
Summary of replicated folder status
The following table provides a high-level overview of replicated folder status on this server.
Replicated Folder Status # of Files Received DFS Replication Bandwidth Savings
DFS Indeterminate 0 0.00%
Data shown about the number of received files and the DFS Replication Bandwidth Savings accumulate from the time the DFS Replication service is started.
No backlog is shown because the backlogged transactions for all members are relative to this server.
Current used and free disk space on volumes where replicated folders are stored
The following table describes the current used and free disk space on volumes where replicated folders are stored.
Volume Path Volume Label Volume Size Free Space % Free Space USN Journal Size
C: (has no label) 465 GB 427 GB 91.8% 512 MB
DFS Replication Bandwidth Savings:
The DFS Replication bandwidth savings are computed by determining the total size of data replicated across the network using a combination of remote differential compression (RDC), which sends only byte-level changes, and stream compression. By comparing this
figure to the amount of data that would be replicated across the network if RDC and stream compression were not used, you can determine the percentage of bandwidth saved.
Reduction in WAN traffic: 0 KB
The following table describes the total on-disk size of files that were replicated and compares them to the amount of data actually received over the network with DFS Replication.
Replicated Folder Total Size of Data If Received Without DFS Replication Actual Data Received Across the Network Using DFS Replication DFS Replication Bandwidth Savings
DFS 0 KB 0 KB 0.00%
Savings from using DFS Replication 0 KB 0 KB 0.00%
DC2(Hide All)
DNS name: dc2.ccwtech.local
Domain name: ccwtech.local
Reference domain controller: DC2.ccwtech.local
IP address: fe80::68ce:8af2:1e3b:3445%12,10.0.0.12
Site: Default-First-Site-Name
Time zone: (GMT-7:00)
ERRORS (There is 1 error to report)
The DFS Replication service is restarting frequently.
Affected replicated folders: All replicated folders on this server.
Description: The DFS Replication service has restarted 8 times in the past 7 days. This problem can affect the replication of all replicated folders to and from this server. Event ID: 1004
Last occurred: Sunday, May 26, 2013 at 3:20:45 PM (GMT-7:00)
Suggested action: If you restarted the service manually, you can safely ignore this message. For information about troubleshooting frequent service restart issues, see The Microsoft Web Site.
WARNINGS (There is 1 warning to report)
This member is waiting for initial replication for replicated folder DFS.
Affected replicated folders: DFS
Description: This member is waiting for initial replication for replicated folder DFS and is not currently participating in replication. This delay can occur because the member is waiting for the DFS Replication service to retrieve replication settings from
Active Directory Domain Services. After the member detects that it is part of replication group, the member will begin initial replication.
Last occurred: Sunday, May 26, 2013 at 4:03:02 PM (GMT-7:00)
Suggested action: Replication will begin after initial replication is complete. If this state does not change, see The Microsoft Web Site.
INFORMATIONAL
Service state: Running
DFS Replication service uptime: 42 min.
DFS Replication service version: 6.2.9200.16384
Summary of replicated folder status
The following table provides a high-level overview of replicated folder status on this server.
Replicated Folder Status Backlogged Sending Transactions Backlogged Receiving Transactions # of Files Received DFS Replication Bandwidth Savings
DFS Waiting for initial replication -- -- 0 0.00%
Data shown about the number of received files and the DFS Replication Bandwidth Savings accumulate from the time the DFS Replication service is started.
Backlogged transactions are relative to member DC1 (dc1.ccwtech.local).
Current used and free disk space on volumes where replicated folders are stored
The following table describes the current used and free disk space on volumes where replicated folders are stored.
Volume Path Volume Label Volume Size Free Space % Free Space USN Journal Size
C: (has no label) 931 GB 467 GB 50.1% 512 MB
DFS Replication Bandwidth Savings:
The DFS Replication bandwidth savings are computed by determining the total size of data replicated across the network using a combination of remote differential compression (RDC), which sends only byte-level changes, and stream compression. By comparing this
figure to the amount of data that would be replicated across the network if RDC and stream compression were not used, you can determine the percentage of bandwidth saved.
Reduction in WAN traffic: 0 KB
The following table describes the total on-disk size of files that were replicated and compares them to the amount of data actually received over the network with DFS Replication.
Replicated Folder Total Size of Data If Received Without DFS Replication Actual Data Received Across the Network Using DFS Replication DFS Replication Bandwidth Savings
DFS 0 KB 0 KB 0.00%
Savings from using DFS Replication 0 KB 0 KB 0.00%