• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3971
  • Last Modified:

Server 2012 DFSR Replication not working for Sysvol

Hi
Have 2 server 2012 DC `s and replicating AD

Have this event in Active directory domain services event log on the PDC

Warning DFSR  Event ID 5014

the DFS Replication service Stopping communication with Partner XXXX for replication group Domain system Volume due to an error . .......

Error 9033 (the request was cancelled by a shutdown

After that an event 5004

Which in return shows replication working for the other DC
0
JakesC
Asked:
JakesC
  • 5
1 Solution
 
Manikandan NarayanswamySecurity Specialist & IBM Security GuardiumCommented:
Hi,

Perform the following on the servers where you're facing this issue

1. Add these registry values to all DFSR replications partners that are having the issues. You will need to reboot for these changes to take effect.



HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters



Value =DisableTaskOffload
Type = DWORD
Data = 1



Value =EnableTCPChimney
Type = DWORD
Data = 0



Value =EnableTCPA
Type = DWORD
Data = 0



Value =EnableRSS
Type = DWORD
Data = 0

For the event ID 5004. Refer the below link and see if it helps

https://support.microsoft.com/en-us/kb/2517913

Thanks
Manikandan
0
 
JakesCAuthor Commented:
We have done the Registry settings and still the same error occurs in the event viewer .
Additionally checking the the two DC`s sysvol folders no replication occured

Also installed the newest Patch hotfices for DFS and Server  2012
0
 
JakesCAuthor Commented:
On the DFSreports
" THis member is waiting  for initial replication for replicated folder sysvol . Share and is not currently particiating in replication. the delay can occur because the meber is waiting for the DFS Replication service to retrieve replication settings from Active directory domain services. "  .....


running repadmin all AD componenets does replicate apart from sysvol
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
JakesCAuthor Commented:
Apologies for the Text , but this is what was found in the Debug Logs for DFSR
Under  the c:\windows\debug


0150426 07:22:13.772 1664 CLUS  4338 Cluster::ClusterUtil::GetVcoList [CLUSTER] Searching for locally owned VCOs
20150426 07:22:13.772 1664 CFAD  8781 Config::AdConfig::GetComputer [CLUSTER] Cluster service is not installed or configured. Skipping the VCO polling.
20150426 07:23:38.054 4540 DOWN  4061 DownstreamTransport::EstablishSession Failed on connId:{5916785E-0A15-47A2-8577-66D4C3B395C6} csId:{BE8EAD28-49D2-4BB9-BE10-BA658852290C} rgName:Domain System Volume Error:
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4054 4540 C A failure was reported by the remote partner]
+      [Error:9051(0x235b) DownstreamTransport::EstablishSession downstreamtransport.cpp:4054 4540 C The content set is not ready]
20150426 07:23:38.054 4540 INCO  7114 InConnection::RestartSession Retrying establish contentset session. connId:{5916785E-0A15-47A2-8577-66D4C3B395C6} csId:{BE8EAD28-49D2-4BB9-BE10-BA658852290C} csName:SYSVOL Share
20150426 07:23:38.054 4540 INCO  1021 [WARN] SessionTask::Step (Ignored) Failed, should have already been processed. Error:
+      [Error:9027(0x2343) InConnection::TransportEstablishSession inconnection.cpp:7701 4540 C A failure was reported by the remote partner]
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4075 4540 C A failure was reported by the remote partner]
+      [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4054 4540 C A failure was reported by the remote partner]
+      [Error:9051(0x235b) DownstreamTransport::EstablishSession downstreamtransport.cpp:4054 4540 C The content set is not ready]
20150426 07:23:38.054 4540 ISYN    68 InitialSyncManager::ReturnToken InitialSync sync step not finished yet. Wake up other session tasks.
20150426 07:23:39.929 4568 SRTR   969 [WARN] SERVER_EstablishSession Failed to establish a replicated folder session. connId:{79781E53-78F8-421D-A9C8-CBF402F9A86E} csId:{BE8EAD28-49D2-4BB9-BE10-BA658852290C} Error:
+      [Error:9051(0x235b) UpstreamTransport::EstablishSession upstreamtransport.cpp:808 4568 C The content set is not ready]
+      [Error:9051(0x235b) OutConnection::TransportEstablishSession outconnection.cpp:510 4568 C The content set is not ready]
+      [Error:9051(0x235b) OutConnection::TransportEstablishSession outconnection.cpp:449 4568 C The content set is not ready]
20150426 07:24:47.075 1648 FSVC  1777 FrsService::PostShutdownMessage Setting shutdown start event
20150426 07:24:47.090 1668 FSVC  1821 FrsService::ShutdownService svcState:ACTIVATED
20150426 07:24:47.090 1668 FSVC  1863 FrsService::ShutdownService Shutting down service
20150426 07:24:47.090 1668 EVNT  1184 EventLog::Report Logging eventId:1006 parameterCount:0
20150426 07:24:47.105 1668 SCNT   570 ServiceControl::SetPendingState Current state:[Service Running], moving to:[Service Stop Pending]
0
 
JakesCAuthor Commented:
Issue resolved By below

To fix this issue, we need to do authoritative restore for SYSVOL on DC-01 and non-authoritative restore on DC-02.
Action Plan
1.       Backup the content of SYSVOL on both domain controllers by copying it to another location.
2.       Stop DFSR service on DC-01 and all other domain controllers in the same domain.
3.       In the ADSIEDIT.MSC tool, modify the following DN and two attributes on DC-01.
CN=SYSVOL Subscription,CN=Domain System Volume,CN=DFSR-LocalSettings,CN=<the server name>,OU=Domain Controllers,DC=<domain>
msDFSR-Enabled=FALSE
msDFSR-options=1
4.       Modify the following DN and single attribute on all other domain controllers in that domain:
CN=SYSVOL Subscription,CN=Domain System Volume,CN=DFSR-LocalSettings,CN=<each other server name>,OU=Domain Controllers,DC=<domain>
msDFSR-Enabled=FALSE
5.       Force Active Directory replication throughout the domain and validate its success on all DCs.
6.       Start the DFSR service on -DC-01.
7.       You will see Event ID 4114 in the DFSR event log indicating SYSVOL is no longer being replicated.
8.       On the same DN from Step 3, set:
msDFSR-Enabled=TRUE
9.       Force Active Directory replication throughout the domain and validate its success on all DCs.
10.   Run the following command from an elevated command prompt on -DC-01.
DFSRDIAG POLLAD
11.   You will see Event ID 4602 in the DFSR event log indicating SYSVOL has been initialized.
12.   Start the DFSR service on the other non-authoritative DCs. You will see Event ID 4114 in the DFSR event log indicating SYSVOL is no longer being replicated on each of them.
13.   Modify the following DN and single attribute on all other domain controllers in that domain:
CN=SYSVOL Subscription,CN=Domain System Volume,CN=DFSR-LocalSettings,CN=<each other server name>,OU=Domain Controllers,DC=<domain>
msDFSR-Enabled=TRUE
14.   Run the following command from an elevated command prompt on all other DCs:
DFSRDIAG POLLAD
15.   You will see Event ID 4614 and 4604 in the DFSR event log indicating SYSVOL has been initialized.
0
 
JakesCAuthor Commented:
As provided and implemented with Microsoft
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now