Hello,
This issue is between two w2k3 r2 servers. The master is at the data center
and he is Operations Master (global catalog server). The other is also a dc
but at a different site. Both are in their unique zone and they seem to have
healthy dns...
From time to time, files stop flowing down to the receivingmember. Bouncing
the DFS service is not correcting the problem this time though (it did in the
past). I notice that when I go to \\servername1\dfsshare or
\\dsfnamespace\dfsshare on the receiving member, he thinks that he has a full
copy of whats on the sending member. If I go to the local drive of the
receiving member, d:\dfsshare, there are no files.
Could this be Wins? DNS? or DFS itself? Any help would be greatly appreciated.

Steve

Its not really possible from this description to understand how you have the
name space and replication set up. I think the generalised names describe what
you think you have set up but may not describe what you have actually set up.

For example what is \\servername1\dfsshare, the name of the share that is the
DFS root or the name of a target UNC on a non DFS server that is being
redirected to from a link within the DFS name space.

For DFSR trouble shooting forget the DFS name space. DFSR replicates between
local folders on each server, e.g. D:\folderA on SrvA to Y:\FolderB on SrvB and
does not use the share or DFS names at all.


On Mon, 20 Apr 2009 15:24:01 -0700, steve <steve@discussions.microsoft.com>
wrote:

Quote:

Hello, This issue is between two w2k3 r2 servers. The master is at the data center and he is Operations Master (global catalog server). The other is also a dc but at a different site. Both are in their unique zone and they seem to have healthy dns... From time to time, files stop flowing down to the receivingmember. Bouncing the DFS service is not correcting the problem this time though (it did in the past). I notice that when I go to \\servername1\dfsshare or \\dsfnamespace\dfsshare on the receiving member, he thinks that he has a full copy of whats on the sending member. If I go to the local drive of the receiving member, d:\dfsshare, there are no files. Could this be Wins? DNS? or DFS itself? Any help would be greatly appreciated. Steve --

Dave Mills
There are 10 types of people, those that understand binary and those that don't.

Hello Steve,

This might have nothing to do with WINS or DNS. I think your issue is with
DFS. How is your dfs setup? how is replication working? Those the receiving
member d:\dfsshare supposed to get copies from master somewhere and it is
not getting? and that is why it is empty? Also when you say you go to
\servername1\dfsshare or \\dsfnamespace\dfsshare on the receiving member,
he thinks that he has a full copy of whats on the sending member.. what do
you mean by this? are there folders here that can't be found in d:\dfsshare?

Hope you can give us more details so we can try to assist

Isaac

Quote:

copy of whats on the sending member"steve" steve@discussions.microsoft.com> wrote in message news:905C4D0E-B1B6-4278-802B-DE127A5D13EC@microsoft.com... Hello, This issue is between two w2k3 r2 servers. The master is at the data center and he is Operations Master (global catalog server). The other is also a dc but at a different site. Both are in their unique zone and they seem to have healthy dns... From time to time, files stop flowing down to the receivingmember. Bouncing the DFS service is not correcting the problem this time though (it did in the past). I notice that when I go to \\servername1\dfsshare or \\dsfnamespace\dfsshare on the receiving member, he thinks that he has a full copy of whats on the sending member. If I go to the local drive of the receiving member, d:\dfsshare, there are no files. Could this be Wins? DNS? or DFS itself? Any help would be greatly appreciated. Steve

Sorry that my earlier description was not clear. The Namespace is
"\\domainname\locationname". The namespace server is \\server1, and we are
doing a Domain Based namespace. The type of replication is Full mesh and the
bandwidth allowed is 256k.
Last night, I deleted and recreated the entire thing. It worked last night
and up until 3pm today. Here's the error that I'm seeing in the DFS Log.
Here are two messages that I see in the event log:

Event ID 4412
The DFS Replication service detected that a file was changed on multiple
servers. A conflict resolution algorithm was used to determine the winning
file. The losing file was moved to the Conflict and Deleted folder.

Event ID 4202
The DFS Replication service has detected that the staging space in use for
the replicated folder at local path F:\data is above the high watermark. The
service will attempt to delete the oldest staging files. Performance may be
affected.
Thank you,
Steve

"steve" wrote:

Quote:

Hello, This issue is between two w2k3 r2 servers. The master is at the data center and he is Operations Master (global catalog server). The other is also a dc but at a different site. Both are in their unique zone and they seem to have healthy dns... From time to time, files stop flowing down to the receivingmember. Bouncing the DFS service is not correcting the problem this time though (it did in the past). I notice that when I go to \\servername1\dfsshare or \\dsfnamespace\dfsshare on the receiving member, he thinks that he has a full copy of whats on the sending member. If I go to the local drive of the receiving member, d:\dfsshare, there are no files. Could this be Wins? DNS? or DFS itself? Any help would be greatly appreciated. Steve

Hello Steve,
The first event 4412 is nothing to worry about. the second event, you may
want to increase your staging folder quota

--
Isaac Oben [MCTIP:EA, MCSE]
"steve" <steve@discussions.microsoft.com> wrote in message
news:C61E7A7E-D2F8-439B-A637-CE4CA50535A8@microsoft.com...

Quote:

Sorry that my earlier description was not clear. The Namespace is "\\domainname\locationname". The namespace server is \\server1, and we are doing a Domain Based namespace. The type of replication is Full mesh and the bandwidth allowed is 256k. Last night, I deleted and recreated the entire thing. It worked last night and up until 3pm today. Here's the error that I'm seeing in the DFS Log. Here are two messages that I see in the event log: Event ID 4412 The DFS Replication service detected that a file was changed on multiple servers. A conflict resolution algorithm was used to determine the winning file. The losing file was moved to the Conflict and Deleted folder. Event ID 4202 The DFS Replication service has detected that the staging space in use for the replicated folder at local path F:\data is above the high watermark. The service will attempt to delete the oldest staging files. Performance may be affected. Thank you, Steve "steve" wrote: Hello, This issue is between two w2k3 r2 servers. The master is at the data center and he is Operations Master (global catalog server). The other is also a dc but at a different site. Both are in their unique zone and they seem to have healthy dns... From time to time, files stop flowing down to the receivingmember. Bouncing the DFS service is not correcting the problem this time though (it did in the past). I notice that when I go to \\servername1\dfsshare or \\dsfnamespace\dfsshare on the receiving member, he thinks that he has a full copy of whats on the sending member. If I go to the local drive of the receiving member, d:\dfsshare, there are no files. Could this be Wins? DNS? or DFS itself? Any help would be greatly appreciated. Steve

Hi Isaac,
I've increased the staging quite a bit (to 20gb!) and still not getting
replication. any other ideas?
Here's an additional message:

Event ID 5002
The DFS Replication service encountered an error communicating with partner
DSGad1 for replication group mycompany.com\11davis\amc.

Partner DNS address: DSGAD1.mycompany.COM

Optional data if available:
Partner WINS Address: DSGAD1
Partner IP Address: 192.168.199.1

The service will retry the connection periodically.

Additional Information:
Error: 1753 (There are no more endpoints available from the endpoint mapper.)
Connection ID: CCD5FD56-82A9-448B-8008-2C2539C38837
Replication Group ID: 74DF5B35-66E7-440F-BA1B-FAAA60941F36

For more information, see Help and Support Center at
"Isaac Oben [MCITP,MCSE]" wrote:

Quote:

Hello Steve, The first event 4412 is nothing to worry about. the second event, you may want to increase your staging folder quota -- Isaac Oben [MCTIP:EA, MCSE] "steve" <steve@discussions.microsoft.com> wrote in message news:C61E7A7E-D2F8-439B-A637-CE4CA50535A8@microsoft.com... Sorry that my earlier description was not clear. The Namespace is "\\domainname\locationname". The namespace server is \\server1, and we are doing a Domain Based namespace. The type of replication is Full mesh and the bandwidth allowed is 256k. Last night, I deleted and recreated the entire thing. It worked last night and up until 3pm today. Here's the error that I'm seeing in the DFS Log. Here are two messages that I see in the event log: Event ID 4412 The DFS Replication service detected that a file was changed on multiple servers. A conflict resolution algorithm was used to determine the winning file. The losing file was moved to the Conflict and Deleted folder. Event ID 4202 The DFS Replication service has detected that the staging space in use for the replicated folder at local path F:\data is above the high watermark. The service will attempt to delete the oldest staging files. Performance may be affected. Thank you, Steve "steve" wrote: Hello, This issue is between two w2k3 r2 servers. The master is at the data center and he is Operations Master (global catalog server). The other is also a dc but at a different site. Both are in their unique zone and they seem to have healthy dns... From time to time, files stop flowing down to the receivingmember. Bouncing the DFS service is not correcting the problem this time though (it did in the past). I notice that when I go to \\servername1\dfsshare or \\dsfnamespace\dfsshare on the receiving member, he thinks that he has a full copy of whats on the sending member. If I go to the local drive of the receiving member, d:\dfsshare, there are no files. Could this be Wins? DNS? or DFS itself? Any help would be greatly appreciated. Steve

Another error in the message
Affected replicated folders: All replicated folders on this server.
Description: DFS Replication cannot replicate with partner DSGAD1 due to a
communication error. The DFS Replication service used partner DNS name
DSGAD1.mydomain.COM, IP address 192.168.199.1, and WINS address DSGAD1 but
failed with error ID: 1723 (The RPC server is too busy to complete this
operation.). Event ID: 5002
Last occurred: Wednesday, April 22, 2009 at 5:34:03 PM (GMT-5:00)
Suggested action: Check for network connectivity problems, for
troubleshooting RPC issues see RPC KB 839880 and for additional
troubleshooting information, see The Microsoft Web Site.


"Isaac Oben [MCITP,MCSE]" wrote:

Quote:

Hello Steve, The first event 4412 is nothing to worry about. the second event, you may want to increase your staging folder quota -- Isaac Oben [MCTIP:EA, MCSE] "steve" <steve@discussions.microsoft.com> wrote in message news:C61E7A7E-D2F8-439B-A637-CE4CA50535A8@microsoft.com... Sorry that my earlier description was not clear. The Namespace is "\\domainname\locationname". The namespace server is \\server1, and we are doing a Domain Based namespace. The type of replication is Full mesh and the bandwidth allowed is 256k. Last night, I deleted and recreated the entire thing. It worked last night and up until 3pm today. Here's the error that I'm seeing in the DFS Log. Here are two messages that I see in the event log: Event ID 4412 The DFS Replication service detected that a file was changed on multiple servers. A conflict resolution algorithm was used to determine the winning file. The losing file was moved to the Conflict and Deleted folder. Event ID 4202 The DFS Replication service has detected that the staging space in use for the replicated folder at local path F:\data is above the high watermark. The service will attempt to delete the oldest staging files. Performance may be affected. Thank you, Steve "steve" wrote: Hello, This issue is between two w2k3 r2 servers. The master is at the data center and he is Operations Master (global catalog server). The other is also a dc but at a different site. Both are in their unique zone and they seem to have healthy dns... From time to time, files stop flowing down to the receivingmember. Bouncing the DFS service is not correcting the problem this time though (it did in the past). I notice that when I go to \\servername1\dfsshare or \\dsfnamespace\dfsshare on the receiving member, he thinks that he has a full copy of whats on the sending member. If I go to the local drive of the receiving member, d:\dfsshare, there are no files. Could this be Wins? DNS? or DFS itself? Any help would be greatly appreciated. Steve

Hello Steve,

Event ID: 5002 is sometimes associated with NIC issues..Can you check
network card from both end make sure they are functioning properly? You can
also run a portqry against port 135 to make sure it is listening etc..
Also recommend do a repadmin /showreps and look for replicatio error if any
between the servers

--
Isaac Oben [MCTIP:EA, MCSE]
"steve" <steve@discussions.microsoft.com> wrote in message
news:11993D35-C70C-49D8-A9F8-10C26D24C5FC@microsoft.com...

Quote:

Another error in the message Affected replicated folders: All replicated folders on this server. Description: DFS Replication cannot replicate with partner DSGAD1 due to a communication error. The DFS Replication service used partner DNS name DSGAD1.mydomain.COM, IP address 192.168.199.1, and WINS address DSGAD1 but failed with error ID: 1723 (The RPC server is too busy to complete this operation.). Event ID: 5002 Last occurred: Wednesday, April 22, 2009 at 5:34:03 PM (GMT-5:00) Suggested action: Check for network connectivity problems, for troubleshooting RPC issues see RPC KB 839880 and for additional troubleshooting information, see The Microsoft Web Site. "Isaac Oben [MCITP,MCSE]" wrote: Hello Steve, The first event 4412 is nothing to worry about. the second event, you may want to increase your staging folder quota -- Isaac Oben [MCTIP:EA, MCSE] "steve" <steve@discussions.microsoft.com> wrote in message news:C61E7A7E-D2F8-439B-A637-CE4CA50535A8@microsoft.com... Sorry that my earlier description was not clear. The Namespace is "\\domainname\locationname". The namespace server is \\server1, and we are doing a Domain Based namespace. The type of replication is Full mesh and the bandwidth allowed is 256k. Last night, I deleted and recreated the entire thing. It worked last night and up until 3pm today. Here's the error that I'm seeing in the DFS Log. Here are two messages that I see in the event log: Event ID 4412 The DFS Replication service detected that a file was changed on multiple servers. A conflict resolution algorithm was used to determine the winning file. The losing file was moved to the Conflict and Deleted folder. Event ID 4202 The DFS Replication service has detected that the staging space in use for the replicated folder at local path F:\data is above the high watermark. The service will attempt to delete the oldest staging files. Performance may be affected. Thank you, Steve "steve" wrote: Hello, This issue is between two w2k3 r2 servers. The master is at the data center and he is Operations Master (global catalog server). The other is also a dc but at a different site. Both are in their unique zone and they seem to have healthy dns... From time to time, files stop flowing down to the receivingmember. Bouncing the DFS service is not correcting the problem this time though (it did in the past). I notice that when I go to \\servername1\dfsshare or \\dsfnamespace\dfsshare on the receiving member, he thinks that he has a full copy of whats on the sending member. If I go to the local drive of the receiving member, d:\dfsshare, there are no files. Could this be Wins? DNS? or DFS itself? Any help would be greatly appreciated. Steve

Will do. Thanks Isaac. Here's some additional information. I tried to force
the replication
G:\>DFSRDIAG SyncNow /RGName:Amc /Partner:dsgad1.mycompany.com /Time:60
/Verbose
[INFO] Duration in Minutes: 60, 60
[INFO] Computer Name: dsgad1
[INFO] Computer DNS: dsgad1.mycompany.com
[INFO] Domain Name: sentage
[INFO] Domain DNS: mycompany.com
[INFO] Site Name: datacenter
[INFO] Computer Name: 11DC
[INFO] Computer DNS: 11DC.mycompany.COM
[INFO] Domain Name: mycompany
[INFO] Domain DNS: mycompany.COM
[INFO] Site Name: 11Davis
[INFO] Connected to WMI services on computer: 11DC.mycompany.COM
[INFO] Issuing query: SELECT * FROM DfsrConnectionInfo WHERE
ReplicationGroupNam
e="amc" AND PartnerName="dsgad1" AND Inbound="true"
[ERROR] Cannot find inbound DfsrConnectionInfo object to the given partner.
Poss
ible reasons:
+ The member has no configured inbound connection with the partner
+ Access is denied to connection monitoring information


[INFO] Execution Time: 0 seconds
Operation Failed


Also I then issued the following command


"Isaac Oben [MCITP,MCSE]" wrote:

Quote:

Hello Steve, Event ID: 5002 is sometimes associated with NIC issues..Can you check network card from both end make sure they are functioning properly? You can also run a portqry against port 135 to make sure it is listening etc.. Also recommend do a repadmin /showreps and look for replicatio error if any between the servers -- Isaac Oben [MCTIP:EA, MCSE] "steve" <steve@discussions.microsoft.com> wrote in message news:11993D35-C70C-49D8-A9F8-10C26D24C5FC@microsoft.com... Another error in the message Affected replicated folders: All replicated folders on this server. Description: DFS Replication cannot replicate with partner DSGAD1 due to a communication error. The DFS Replication service used partner DNS name DSGAD1.mydomain.COM, IP address 192.168.199.1, and WINS address DSGAD1 but failed with error ID: 1723 (The RPC server is too busy to complete this operation.). Event ID: 5002 Last occurred: Wednesday, April 22, 2009 at 5:34:03 PM (GMT-5:00) Suggested action: Check for network connectivity problems, for troubleshooting RPC issues see RPC KB 839880 and for additional troubleshooting information, see The Microsoft Web Site. "Isaac Oben [MCITP,MCSE]" wrote: Hello Steve, The first event 4412 is nothing to worry about. the second event, you may want to increase your staging folder quota -- Isaac Oben [MCTIP:EA, MCSE] "steve" <steve@discussions.microsoft.com> wrote in message news:C61E7A7E-D2F8-439B-A637-CE4CA50535A8@microsoft.com... Sorry that my earlier description was not clear. The Namespace is "\\domainname\locationname". The namespace server is \\server1, and we are doing a Domain Based namespace. The type of replication is Full mesh and the bandwidth allowed is 256k. Last night, I deleted and recreated the entire thing. It worked last night and up until 3pm today. Here's the error that I'm seeing in the DFS Log. Here are two messages that I see in the event log: Event ID 4412 The DFS Replication service detected that a file was changed on multiple servers. A conflict resolution algorithm was used to determine the winning file. The losing file was moved to the Conflict and Deleted folder. Event ID 4202 The DFS Replication service has detected that the staging space in use for the replicated folder at local path F:\data is above the high watermark. The service will attempt to delete the oldest staging files. Performance may be affected. Thank you, Steve "steve" wrote: Hello, This issue is between two w2k3 r2 servers. The master is at the data center and he is Operations Master (global catalog server). The other is also a dc but at a different site. Both are in their unique zone and they seem to have healthy dns... From time to time, files stop flowing down to the receivingmember. Bouncing the DFS service is not correcting the problem this time though (it did in the past). I notice that when I go to \\servername1\dfsshare or \\dsfnamespace\dfsshare on the receiving member, he thinks that he has a full copy of whats on the sending member. If I go to the local drive of the receiving member, d:\dfsshare, there are no files. Could this be Wins? DNS? or DFS itself? Any help would be greatly appreciated. Steve

Here's the second command I issued and the results. Still things are not
flowing properly.

G:\>DFSRDIAG StaticRPC /Port:45000 /Mem:dsgad1.mycompany.com /V
[INFO] RPC port number: 45000, 45000
[INFO] Computer Name: dsgad1
[INFO] Computer DNS: dsgad1.mycompany.com
[INFO] Domain Name: Mycompany
[INFO] Domain DNS: mycompany.com
[INFO] Site Name: datacenter
[INFO] Connected to WMI services on computer: dsgad1.mycompany.com

[INFO] Execution Time: 1 seconds
Operation Succeeded


"Isaac Oben [MCITP,MCSE]" wrote:

Quote:

Hello Steve, Event ID: 5002 is sometimes associated with NIC issues..Can you check network card from both end make sure they are functioning properly? You can also run a portqry against port 135 to make sure it is listening etc.. Also recommend do a repadmin /showreps and look for replicatio error if any between the servers -- Isaac Oben [MCTIP:EA, MCSE] "steve" <steve@discussions.microsoft.com> wrote in message news:11993D35-C70C-49D8-A9F8-10C26D24C5FC@microsoft.com... Another error in the message Affected replicated folders: All replicated folders on this server. Description: DFS Replication cannot replicate with partner DSGAD1 due to a communication error. The DFS Replication service used partner DNS name DSGAD1.mydomain.COM, IP address 192.168.199.1, and WINS address DSGAD1 but failed with error ID: 1723 (The RPC server is too busy to complete this operation.). Event ID: 5002 Last occurred: Wednesday, April 22, 2009 at 5:34:03 PM (GMT-5:00) Suggested action: Check for network connectivity problems, for troubleshooting RPC issues see RPC KB 839880 and for additional troubleshooting information, see The Microsoft Web Site. "Isaac Oben [MCITP,MCSE]" wrote: Hello Steve, The first event 4412 is nothing to worry about. the second event, you may want to increase your staging folder quota -- Isaac Oben [MCTIP:EA, MCSE] "steve" <steve@discussions.microsoft.com> wrote in message news:C61E7A7E-D2F8-439B-A637-CE4CA50535A8@microsoft.com... Sorry that my earlier description was not clear. The Namespace is "\\domainname\locationname". The namespace server is \\server1, and we are doing a Domain Based namespace. The type of replication is Full mesh and the bandwidth allowed is 256k. Last night, I deleted and recreated the entire thing. It worked last night and up until 3pm today. Here's the error that I'm seeing in the DFS Log. Here are two messages that I see in the event log: Event ID 4412 The DFS Replication service detected that a file was changed on multiple servers. A conflict resolution algorithm was used to determine the winning file. The losing file was moved to the Conflict and Deleted folder. Event ID 4202 The DFS Replication service has detected that the staging space in use for the replicated folder at local path F:\data is above the high watermark. The service will attempt to delete the oldest staging files. Performance may be affected. Thank you, Steve "steve" wrote: Hello, This issue is between two w2k3 r2 servers. The master is at the data center and he is Operations Master (global catalog server). The other is also a dc but at a different site. Both are in their unique zone and they seem to have healthy dns... From time to time, files stop flowing down to the receivingmember. Bouncing the DFS service is not correcting the problem this time though (it did in the past). I notice that when I go to \\servername1\dfsshare or \\dsfnamespace\dfsshare on the receiving member, he thinks that he has a full copy of whats on the sending member. If I go to the local drive of the receiving member, d:\dfsshare, there are no files. Could this be Wins? DNS? or DFS itself? Any help would be greatly appreciated. Steve

steve wrote:

Quote:

Hello, This issue is between two w2k3 r2 servers. The master is at the data center and he is Operations Master (global catalog server). The other is also a dc but at a different site. Both are in their unique zone and they seem to have healthy dns... From time to time, files stop flowing down to the receivingmember. Bouncing the DFS service is not correcting the problem this time though (it did in the past). I notice that when I go to \\servername1\dfsshare or \\dsfnamespace\dfsshare on the receiving member, he thinks that he has a full copy of whats on the sending member. If I go to the local drive of the receiving member, d:\dfsshare, there are no files. Could this be Wins? DNS? or DFS itself? Any help would be greatly appreciated. Steve

Answer: This is possible through the DFS.

--
Message posted via http://www.winserverkb.com