Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, May 26, 2013 3:24 AM
I started a thread in the Windows General forum but I'm not getting much traction so I thought I'd try here. This is the last post I submitted:
This evening, I ran the dfsrdiag utility. The command I ran was:
dfsrdiag proptest /RGName:"mydomain.com\my files\test" /RFName:test /TestFilename:TestFile02.xml /V /Mem:file02.mydomain.com
I ran this command from both File01 and File 02 and on both machines, I ran it with the Mem parameter set to File01 and File 02. All 4 iterations of the command reported success and the xml file was created on both machines. An example of the command outpu (ran on File02 targeting File01):
Name:test /TestFilename:TestFile02.xml /V /Mem:file01.mydomain.com
[INFO] Computer Name: file01
[INFO] Computer DNS: file01.mydomain.com
[INFO] Domain DNS: mydomain.com
[INFO] Site Name: MySite
[INFO] Connected to WMI services on computer: file01.mydomain.com
[INFO] Issuing query: SELECT * FROM DfsrReplicationGroupConfig WHERE Replication
GroupName="mydomain.com\my files\test"
[INFO] Found DfsrReplicationGroupConfig object, guid: A57A94DD-48AE-4132-A577-61
7938B43DB9
[INFO] Issuing query: SELECT * FROM DfsrReplicatedFolderConfig WHERE Replication
GroupGuid="A57A94DD-48AE-4132-A577-617938B43DB9" AND ReplicatedFolderName="test"
[INFO] Found DfsrReplicatedFolderConfig object, guid: 2529A9CE-52E1-4D0D-8FCB-1B
1F5E68B85B
[INFO] RootPath: E:\Test-dfs
[INFO] Execution Time: 0 seconds
Operation Succeeded
But, replication still does not work. I copied a bunch of files into one of the replicated shares on one machine and they do not appear on the other. Here is an example of the log entries:
2F0489129E8E} rgName:mydomain.com\my files\camera Error:
+ [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4054 2612 C A failure was reported by the remote partner]
+ [Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4054 2612 C The content set was not found]
20130525 02:59:43.107 2612 INCO 2653 InConnection::ProcessErrorStatus remoteError:1 Error:9028(0x2344) The content set was not found
20130525 02:59:43.107 2612 INCO 2690 InConnection::ProcessErrorStatus Restarting session on error. connId:{A60F7F57-A781-4FF3-B8D1-93712FDCCA2A} csId:{CBA881FA-19E8-4C6C-9478-2F0489129E8E} state:CONNECTED
20130525 02:59:43.107 2612 INCO 7114 InConnection::RestartSession Retrying establish contentset session. connId:{A60F7F57-A781-4FF3-B8D1-93712FDCCA2A} csId:{CBA881FA-19E8-4C6C-9478-2F0489129E8E} csName:Camera
20130525 02:59:43.107 2612 INCO 1021 [WARN] SessionTask::Step (Ignored) Failed, should have already been processed. Error:
+ [Error:9027(0x2343) InConnection::TransportEstablishSession inconnection.cpp:7701 2612 C A failure was reported by the remote partner]
+ [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4075 2612 C A failure was reported by the remote partner]
+ [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4054 2612 C A failure was reported by the remote partner]
+ [Error:9028(0x2344) DownstreamTransport::EstablishSession downstreamtransport.cpp:4054 2612 C The content set was not found]
20130525 02:59:43.107 2612 TASK 756 Task::Schedule task:00000098016C4850 oldState:RUNNING newState:RUNSLEEP timeout:120000 NEW_SESSION
20130525 02:59:43.107 2612 TASK 1030 TaskPool::Sleep New sleeper thread inserted. Sleepers: 2
20130525 02:59:53.814 2636 TASK 1030 TaskPool::Sleep New sleeper thread inserted. Sleepers: 2
The same error is repeated for each replicated folder.
Any ideas? There isn't much on this online. I even went through the lengthy "Understanding DFSR Debug Logging" and, while a good reference, it didn't touch on what errors 9027 and 9028 mean or what causes them.
Thanks
Bert
All replies (6)
Monday, May 27, 2013 1:33 PM
Hi Bert,
I checked the previous thread and it seems that the issue lasts for some days.
Maybe you could try to recreate the replication group to see if it will back to work. A similar issue mentioned in this thread and the OP deleted one of the folder target (actually he formatted the drive):
Also you could test to recreate DFSR database to see if it will help:
1. Run “net stop dfsr”(without quotation marks) to stop DFSR service.
2. Then rename dfsr.db to dfsr_old.db under folder database_GUID.
3. Run “net start dfsr”(without the quotes) to start DFSR service again.
4. Verify the new database file is created under C:\System Volume Information\DFSR\database_GUID
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected].
Monday, May 27, 2013 3:27 PM
Thanks for the reply, Shaon.
This is odd. I don't have a file named dfsr.db nor do I have a folder called database_GUID. All I have in the C:\System Volume Information\DFSR folder is a folder called config. In that folder is a single xml file called DfsrMachineConfig.xml and it just contains information about the schema and update info (a little more on one machine presumably because I increased the logging level).
Bert
Thursday, May 30, 2013 3:51 AM | 2 votes
Then the DFSR database seems incorrect in your description.
Try the following steps to rename the DFSR folder and see if database could be recreated:
1. Stop and ALSO disable the DFSR service on <ServerA> server (don't just simply stop it)
2. In Windows Explorer open the specific drive
3. Right click on the "System Volume Information" directory and select Properties\Security
Note: You might need to select the option for "Show hidden files, folders or drives" and also uncheck "Hide protected operating system files" in the folders view options to be able to even see the "System Volume Information" directory.
4. Grant your user account that you're logged in with (if a member of Administrators group this will also suffice) "Full Control" to the "System Volume Information" directory.
Note: You may get an error on setting security on some files - this is expected.
5. Open an elevated/Administrative command prompt. Switch to the "<drive letter>:\System Volume Information" directory
6. Type the command "rmdir DFSR /s"
7. Enable and re-start the DFSR service on <ServerA> server
8. We will then set the <ServerA> server as the Primary member with dfsradmin.exe utility –
Dfsradmin Membership Set /RGName:<RG Name> /RFName:<RF Name> /MemName:<Member Name> /IsPrimary:True
Note: Files will be replicated from ServerA to all other targets. So if there is any newer file on other target servers, backup before starting replication.
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected].
Thursday, May 30, 2013 12:52 PM
Thanks, Shaon, that seemed to work. I now have the test folder replicating from File02 to File01, but not in the other direction.
Bert
Wednesday, June 5, 2013 7:09 AM
Hi Bert,
Any error occurs? Generally reset database will help on such kind of issues. Maybe you could have a try to redo these steps on server2.
Meanwhile here is a thread which related to a one-way replication issue.
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected].
Monday, June 10, 2013 1:34 AM
How are thing going? Please let us know if there is any progress.
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected].