Discussion:
Replication problem in DFS
(too old to reply)
Minas
2006-04-07 12:06:02 UTC
Permalink
Hello,

I have a strange problem with file replication, please show me a direction
if there is any.

I have two domain controllers in the network, each running Windows 2003,
Service Pack 1.

I created a distributed file system root on one of them, shared a folder on
each of these servers, added a link into the DFS root and specified these two
shares as targets. The system log shows everything went all right and
replication has started for this DFS link.

I could check that I can create a new file on one of these shares and see it
getting replicated in the other. Then I populated one of the shares with
production data and waited for the replication to complete. Almost everything
got replicated, except of some jpg files! These files have names like
137_3703.JPG and first visible difference difference between these files from
other jpg files (which replicated successfully) was that they were larger
(>1Meg). I have other files though which are much larger and have replicated
without any problems.

Checked security permissions of these files and they are no different than
others.

Another interesting observation: any copies of these unreplicated files
(created in file explorer window) do not replicate neither. I changed the
name, changed extension (changed .jpg to .txt), edited and deleted everything
in them -- no change -- these files do not get replicated. But if I open in
an editor and do "save
as" to a new name -- the new file gets replicated.

Installed sonar, could not see any errors.

Has anyone had similar problems? Am I missing something? Please help.

Thanks,
Minas.
Minas
2006-04-08 22:19:01 UTC
Permalink
Hello Ned Pyle,

I see you watch and answer to most questions in this group. You left my
question unanswered though...

Can you please advise where should I look into to troubleshoot this problem.

Please let me know if any additional details are needed.

Thanks,
Minas.
Post by Minas
Hello,
I have a strange problem with file replication, please show me a direction
if there is any.
I have two domain controllers in the network, each running Windows 2003,
Service Pack 1.
I created a distributed file system root on one of them, shared a folder on
each of these servers, added a link into the DFS root and specified these two
shares as targets. The system log shows everything went all right and
replication has started for this DFS link.
I could check that I can create a new file on one of these shares and see it
getting replicated in the other. Then I populated one of the shares with
production data and waited for the replication to complete. Almost everything
got replicated, except of some jpg files! These files have names like
137_3703.JPG and first visible difference difference between these files from
other jpg files (which replicated successfully) was that they were larger
(>1Meg). I have other files though which are much larger and have replicated
without any problems.
Checked security permissions of these files and they are no different than
others.
Another interesting observation: any copies of these unreplicated files
(created in file explorer window) do not replicate neither. I changed the
name, changed extension (changed .jpg to .txt), edited and deleted everything
in them -- no change -- these files do not get replicated. But if I open in
an editor and do "save
as" to a new name -- the new file gets replicated.
Installed sonar, could not see any errors.
Has anyone had similar problems? Am I missing something? Please help.
Thanks,
Minas.
Ned Pyle (MSFT)
2006-04-10 21:12:08 UTC
Permalink
I was hiding. :-)

Interesting issue. Even though it seems very unlikely based on what you
describe below, I would recommend checking out the following with DFSGUI.MSC

---------
1. Open the root
2. Under it, rt-click the link and choose properties.
3. On the replication tab, verify that 'File Filter' only has:
*.bak,*.tmp,~*
---------

If for some reason we see *.jpg there, it's being filtered. Very unlikely,
but worth the 10 seconds it will take to check.

It sounds more like there's some problem with files being locked. FRS will
not replicate files that are in use. Does some application service utilize
this namespace, just for JPG files? Are you letting your Anti-virus software
scan the DFS file structure (if so, just for testing, tell it to ignore that
directory tree temporarily and restart the service or computers).

As you can tell, I'm reaching at straws here. Based on your exact
description below, it doesn't make a lot of sense (especially when you
rename a file and it still fails to replicate until you open and close it
with notepad- that makes file locks and filters unlikely).

Let me know what you see,

Ned
Post by Minas
Hello Ned Pyle,
I see you watch and answer to most questions in this group. You left my
question unanswered though...
Can you please advise where should I look into to troubleshoot this problem.
Please let me know if any additional details are needed.
Thanks,
Minas.
Post by Minas
Hello,
I have a strange problem with file replication, please show me a direction
if there is any.
I have two domain controllers in the network, each running Windows 2003,
Service Pack 1.
I created a distributed file system root on one of them, shared a folder on
each of these servers, added a link into the DFS root and specified these two
shares as targets. The system log shows everything went all right and
replication has started for this DFS link.
I could check that I can create a new file on one of these shares and see it
getting replicated in the other. Then I populated one of the shares with
production data and waited for the replication to complete. Almost everything
got replicated, except of some jpg files! These files have names like
137_3703.JPG and first visible difference difference between these files from
other jpg files (which replicated successfully) was that they were larger
(>1Meg). I have other files though which are much larger and have replicated
without any problems.
Checked security permissions of these files and they are no different than
others.
Another interesting observation: any copies of these unreplicated files
(created in file explorer window) do not replicate neither. I changed the
name, changed extension (changed .jpg to .txt), edited and deleted everything
in them -- no change -- these files do not get replicated. But if I open in
an editor and do "save
as" to a new name -- the new file gets replicated.
Installed sonar, could not see any errors.
Has anyone had similar problems? Am I missing something? Please help.
Thanks,
Minas.
Minas
2006-04-11 13:16:03 UTC
Permalink
Hello Ned, thank you for your reply.

I tried all you said in your message and the problem did not resolve. To
show you what is actually happening, I ran several commands in command prompt
on server1.

The conclusions from my actions are:
-There is a certain file which does not replicate when copied into one of
replicated folders
-Any copes of this file do not replicate neither
-The file starts replicating as soon as I add a single byte to the end of
file (increase the size by 1 byte) using Hex Editor

Here is the log of my actions:

Start with empty directories:

Server1: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467

Directory of D:\Manufacturing

04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 118,211,911,680 bytes free

Server2: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248

Directory of D:\Manufacturing

04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,124,161,024 bytes free


Copy 136_3693.JPG file from a temp directory which I know will replicate

Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3693.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467

Directory of D:\Manufacturing

04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 118,211,862,528 bytes free

Server2: (show contents, replication success)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248

Directory of D:\Manufacturing

04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free

Copy 136_3697.JPG file from a temp directory which I know does not replicate:

Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3697.JPG .
1 file(s) copied.

D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467

Directory of D:\Manufacturing

04/11/2006 07:40 AM <DIR> .
04/11/2006 07:40 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 118,209,482,752 bytes free

Server2: (show contents, replication did not happen)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248

Directory of D:\Manufacturing

04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free


On Server1, Copy the non-replicated file 136_3697.JPG to new_file.txt file;
show that replication did not happen for the new file neither:
Server1:
D:\Manufacturing>copy 136_3697.JPG new_file.txt
1 file(s) copied.

D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467

Directory of D:\Manufacturing

04/11/2006 07:51 AM <DIR> .
04/11/2006 07:51 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,207,102,976 bytes free

Server2:
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248

Directory of D:\Manufacturing

04/11/2006 07:49 AM <DIR> .
04/11/2006 07:49 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,134,749,184 bytes free

On Server1, open 136_3697.JPG in a hex editor and add a single byte to the
end of the file and save. Show that the replication happened:

Server1: (dir after editing in Hex Editor program)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467

Directory of D:\Manufacturing

04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 118,205,399,040 bytes free

Server2:
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248

Directory of D:\Manufacturing

04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,129,989,632 bytes free

On Server 1, open the same file again in Hex Editor and delete that single
byte I added at the end in the previous step, show that replication still
works for this file (new_file.txt is still un-replicated though):

Server1: (dir after deleting 1 byte at the end)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467

Directory of D:\Manufacturing

04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,205,595,648 bytes free

Server2:
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248

Directory of D:\Manufacturing

04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 18,127,482,880 bytes free
Post by Ned Pyle (MSFT)
I was hiding. :-)
Interesting issue. Even though it seems very unlikely based on what you
describe below, I would recommend checking out the following with DFSGUI.MSC
---------
1. Open the root
2. Under it, rt-click the link and choose properties.
*.bak,*.tmp,~*
---------
If for some reason we see *.jpg there, it's being filtered. Very unlikely,
but worth the 10 seconds it will take to check.
It sounds more like there's some problem with files being locked. FRS will
not replicate files that are in use. Does some application service utilize
this namespace, just for JPG files? Are you letting your Anti-virus software
scan the DFS file structure (if so, just for testing, tell it to ignore that
directory tree temporarily and restart the service or computers).
As you can tell, I'm reaching at straws here. Based on your exact
description below, it doesn't make a lot of sense (especially when you
rename a file and it still fails to replicate until you open and close it
with notepad- that makes file locks and filters unlikely).
Let me know what you see,
Ned
Post by Minas
Hello Ned Pyle,
I see you watch and answer to most questions in this group. You left my
question unanswered though...
Can you please advise where should I look into to troubleshoot this problem.
Please let me know if any additional details are needed.
Thanks,
Minas.
Post by Minas
Hello,
I have a strange problem with file replication, please show me a direction
if there is any.
I have two domain controllers in the network, each running Windows 2003,
Service Pack 1.
I created a distributed file system root on one of them, shared a folder on
each of these servers, added a link into the DFS root and specified these two
shares as targets. The system log shows everything went all right and
replication has started for this DFS link.
I could check that I can create a new file on one of these shares and see it
getting replicated in the other. Then I populated one of the shares with
production data and waited for the replication to complete. Almost everything
got replicated, except of some jpg files! These files have names like
137_3703.JPG and first visible difference difference between these files from
other jpg files (which replicated successfully) was that they were larger
(>1Meg). I have other files though which are much larger and have replicated
without any problems.
Checked security permissions of these files and they are no different than
others.
Another interesting observation: any copies of these unreplicated files
(created in file explorer window) do not replicate neither. I changed the
name, changed extension (changed .jpg to .txt), edited and deleted everything
in them -- no change -- these files do not get replicated. But if I open in
an editor and do "save
as" to a new name -- the new file gets replicated.
Installed sonar, could not see any errors.
Has anyone had similar problems? Am I missing something? Please help.
Thanks,
Minas.
Minas
2006-04-11 14:57:02 UTC
Permalink
One more thing I found out is that the contents of the file doesn't have
anything to do with the problem -- I opened new_file.txt in the hex editor
and replaced everythig in it with '00' character (ASCII code 0). the file did
not replicate after I saved the file. Once again, it replicated as soon as I
added one byte to the end of the file.

It seams there is a problem in the ntfs attributes for the file which gets
copied from one file to the other until the size is changed. Is there a
command to access all attributes for a file?

Thanks,
Minas.
Post by Minas
Hello Ned, thank you for your reply.
I tried all you said in your message and the problem did not resolve. To
show you what is actually happening, I ran several commands in command prompt
on server1.
-There is a certain file which does not replicate when copied into one of
replicated folders
-Any copes of this file do not replicate neither
-The file starts replicating as soon as I add a single byte to the end of
file (increase the size by 1 byte) using Hex Editor
Server1: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 118,211,911,680 bytes free
Server2: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,124,161,024 bytes free
Copy 136_3693.JPG file from a temp directory which I know will replicate
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3693.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 118,211,862,528 bytes free
Server2: (show contents, replication success)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3697.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:40 AM <DIR> .
04/11/2006 07:40 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 118,209,482,752 bytes free
Server2: (show contents, replication did not happen)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
On Server1, Copy the non-replicated file 136_3697.JPG to new_file.txt file;
D:\Manufacturing>copy 136_3697.JPG new_file.txt
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:51 AM <DIR> .
04/11/2006 07:51 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,207,102,976 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:49 AM <DIR> .
04/11/2006 07:49 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,134,749,184 bytes free
On Server1, open 136_3697.JPG in a hex editor and add a single byte to the
Server1: (dir after editing in Hex Editor program)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 118,205,399,040 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,129,989,632 bytes free
On Server 1, open the same file again in Hex Editor and delete that single
byte I added at the end in the previous step, show that replication still
Server1: (dir after deleting 1 byte at the end)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,205,595,648 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 18,127,482,880 bytes free
Post by Ned Pyle (MSFT)
I was hiding. :-)
Interesting issue. Even though it seems very unlikely based on what you
describe below, I would recommend checking out the following with DFSGUI.MSC
---------
1. Open the root
2. Under it, rt-click the link and choose properties.
*.bak,*.tmp,~*
---------
If for some reason we see *.jpg there, it's being filtered. Very unlikely,
but worth the 10 seconds it will take to check.
It sounds more like there's some problem with files being locked. FRS will
not replicate files that are in use. Does some application service utilize
this namespace, just for JPG files? Are you letting your Anti-virus software
scan the DFS file structure (if so, just for testing, tell it to ignore that
directory tree temporarily and restart the service or computers).
As you can tell, I'm reaching at straws here. Based on your exact
description below, it doesn't make a lot of sense (especially when you
rename a file and it still fails to replicate until you open and close it
with notepad- that makes file locks and filters unlikely).
Let me know what you see,
Ned
Post by Minas
Hello Ned Pyle,
I see you watch and answer to most questions in this group. You left my
question unanswered though...
Can you please advise where should I look into to troubleshoot this problem.
Please let me know if any additional details are needed.
Thanks,
Minas.
Post by Minas
Hello,
I have a strange problem with file replication, please show me a direction
if there is any.
I have two domain controllers in the network, each running Windows 2003,
Service Pack 1.
I created a distributed file system root on one of them, shared a folder on
each of these servers, added a link into the DFS root and specified these two
shares as targets. The system log shows everything went all right and
replication has started for this DFS link.
I could check that I can create a new file on one of these shares and see it
getting replicated in the other. Then I populated one of the shares with
production data and waited for the replication to complete. Almost everything
got replicated, except of some jpg files! These files have names like
137_3703.JPG and first visible difference difference between these files from
other jpg files (which replicated successfully) was that they were larger
(>1Meg). I have other files though which are much larger and have replicated
without any problems.
Checked security permissions of these files and they are no different than
others.
Another interesting observation: any copies of these unreplicated files
(created in file explorer window) do not replicate neither. I changed the
name, changed extension (changed .jpg to .txt), edited and deleted everything
in them -- no change -- these files do not get replicated. But if I open in
an editor and do "save
as" to a new name -- the new file gets replicated.
Installed sonar, could not see any errors.
Has anyone had similar problems? Am I missing something? Please help.
Thanks,
Ned Pyle (MSFT)
2006-04-11 18:38:17 UTC
Permalink
Weird! To your question:

The FC command can be used to compare two files at a binary level and tell
differences between them (that's in box in 2003).
The FILEVER /V command can tell about further internal file metadata.
The ATTRIB command can tell basic attribute information about a file.
There are further PSS tools we can send out if you open a case.

I'd be interested in seeing what FRSDIAG has to offer, run on both the
upstream and downstream servers.
http://www.microsoft.com/downloads/details.aspx?FamilyID=43cb658e-8553-4de7-811a-562563eb5ebf&DisplayLang=en .
Honestly though, this looks like it's going to demand more attention than
the newsgroup will be able to answer in a timely manner. If you don't mind
waiting though, just attach the cabs and I'll look.

Ned
Post by Minas
One more thing I found out is that the contents of the file doesn't have
anything to do with the problem -- I opened new_file.txt in the hex editor
and replaced everythig in it with '00' character (ASCII code 0). the file did
not replicate after I saved the file. Once again, it replicated as soon as I
added one byte to the end of the file.
It seams there is a problem in the ntfs attributes for the file which gets
copied from one file to the other until the size is changed. Is there a
command to access all attributes for a file?
Thanks,
Minas.
Post by Minas
Hello Ned, thank you for your reply.
I tried all you said in your message and the problem did not resolve. To
show you what is actually happening, I ran several commands in command prompt
on server1.
-There is a certain file which does not replicate when copied into one of
replicated folders
-Any copes of this file do not replicate neither
-The file starts replicating as soon as I add a single byte to the end of
file (increase the size by 1 byte) using Hex Editor
Server1: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 118,211,911,680 bytes free
Server2: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,124,161,024 bytes free
Copy 136_3693.JPG file from a temp directory which I know will replicate
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3693.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 118,211,862,528 bytes free
Server2: (show contents, replication success)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3697.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:40 AM <DIR> .
04/11/2006 07:40 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 118,209,482,752 bytes free
Server2: (show contents, replication did not happen)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
On Server1, Copy the non-replicated file 136_3697.JPG to new_file.txt file;
D:\Manufacturing>copy 136_3697.JPG new_file.txt
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:51 AM <DIR> .
04/11/2006 07:51 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,207,102,976 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:49 AM <DIR> .
04/11/2006 07:49 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,134,749,184 bytes free
On Server1, open 136_3697.JPG in a hex editor and add a single byte to the
Server1: (dir after editing in Hex Editor program)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 118,205,399,040 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,129,989,632 bytes free
On Server 1, open the same file again in Hex Editor and delete that single
byte I added at the end in the previous step, show that replication still
Server1: (dir after deleting 1 byte at the end)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,205,595,648 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 18,127,482,880 bytes free
Post by Ned Pyle (MSFT)
I was hiding. :-)
Interesting issue. Even though it seems very unlikely based on what you
describe below, I would recommend checking out the following with DFSGUI.MSC
---------
1. Open the root
2. Under it, rt-click the link and choose properties.
*.bak,*.tmp,~*
---------
If for some reason we see *.jpg there, it's being filtered. Very unlikely,
but worth the 10 seconds it will take to check.
It sounds more like there's some problem with files being locked. FRS will
not replicate files that are in use. Does some application service utilize
this namespace, just for JPG files? Are you letting your Anti-virus software
scan the DFS file structure (if so, just for testing, tell it to ignore that
directory tree temporarily and restart the service or computers).
As you can tell, I'm reaching at straws here. Based on your exact
description below, it doesn't make a lot of sense (especially when you
rename a file and it still fails to replicate until you open and close it
with notepad- that makes file locks and filters unlikely).
Let me know what you see,
Ned
Post by Minas
Hello Ned Pyle,
I see you watch and answer to most questions in this group. You left my
question unanswered though...
Can you please advise where should I look into to troubleshoot this problem.
Please let me know if any additional details are needed.
Thanks,
Minas.
Post by Minas
Hello,
I have a strange problem with file replication, please show me a direction
if there is any.
I have two domain controllers in the network, each running Windows 2003,
Service Pack 1.
I created a distributed file system root on one of them, shared a
folder
on
each of these servers, added a link into the DFS root and specified
these
two
shares as targets. The system log shows everything went all right and
replication has started for this DFS link.
I could check that I can create a new file on one of these shares
and see
it
getting replicated in the other. Then I populated one of the shares with
production data and waited for the replication to complete. Almost everything
got replicated, except of some jpg files! These files have names like
137_3703.JPG and first visible difference difference between these
files
from
other jpg files (which replicated successfully) was that they were larger
(>1Meg). I have other files though which are much larger and have replicated
without any problems.
Checked security permissions of these files and they are no
different
than
others.
Another interesting observation: any copies of these unreplicated files
(created in file explorer window) do not replicate neither. I changed the
name, changed extension (changed .jpg to .txt), edited and deleted everything
in them -- no change -- these files do not get replicated. But if I
open
in
an editor and do "save
as" to a new name -- the new file gets replicated.
Installed sonar, could not see any errors.
Has anyone had similar problems? Am I missing something? Please help.
Thanks,
Minas
2006-04-12 14:10:02 UTC
Permalink
Thanks Ned,

I'll give another try to resolve this through the newsgroup.

I ran FILEVER and ATTRIB and did not see any significant difference between
attributes of replicating and non-replicating files.

I also ran frsdiag. I tried to send the cab files but got an error message
that the message is too large. Is there an alternative way to deliver this
to you? My email address is ***@yahoo.com.

Please help me with this last effort, I'll drop it if nothing shows here
neither.

Thanks a lot,
Minas.
Post by Ned Pyle (MSFT)
The FC command can be used to compare two files at a binary level and tell
differences between them (that's in box in 2003).
The FILEVER /V command can tell about further internal file metadata.
The ATTRIB command can tell basic attribute information about a file.
There are further PSS tools we can send out if you open a case.
I'd be interested in seeing what FRSDIAG has to offer, run on both the
upstream and downstream servers.
http://www.microsoft.com/downloads/details.aspx?FamilyID=43cb658e-8553-4de7-811a-562563eb5ebf&DisplayLang=en .
Honestly though, this looks like it's going to demand more attention than
the newsgroup will be able to answer in a timely manner. If you don't mind
waiting though, just attach the cabs and I'll look.
Ned
Post by Minas
One more thing I found out is that the contents of the file doesn't have
anything to do with the problem -- I opened new_file.txt in the hex editor
and replaced everythig in it with '00' character (ASCII code 0). the file did
not replicate after I saved the file. Once again, it replicated as soon
as
I
added one byte to the end of the file.
It seams there is a problem in the ntfs attributes for the file which gets
copied from one file to the other until the size is changed. Is there a
command to access all attributes for a file?
Thanks,
Minas.
Post by Minas
Hello Ned, thank you for your reply.
I tried all you said in your message and the problem did not resolve. To
show you what is actually happening, I ran several commands in command prompt
on server1.
-There is a certain file which does not replicate when copied into one of
replicated folders
-Any copes of this file do not replicate neither
-The file starts replicating as soon as I add a single byte to the end of
file (increase the size by 1 byte) using Hex Editor
Server1: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 118,211,911,680 bytes free
Server2: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,124,161,024 bytes free
Copy 136_3693.JPG file from a temp directory which I know will replicate
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3693.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 118,211,862,528 bytes free
Server2: (show contents, replication success)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3697.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:40 AM <DIR> .
04/11/2006 07:40 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 118,209,482,752 bytes free
Server2: (show contents, replication did not happen)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
On Server1, Copy the non-replicated file 136_3697.JPG to new_file.txt file;
D:\Manufacturing>copy 136_3697.JPG new_file.txt
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:51 AM <DIR> .
04/11/2006 07:51 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,207,102,976 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:49 AM <DIR> .
04/11/2006 07:49 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,134,749,184 bytes free
On Server1, open 136_3697.JPG in a hex editor and add a single byte to the
Server1: (dir after editing in Hex Editor program)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 118,205,399,040 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,129,989,632 bytes free
On Server 1, open the same file again in Hex Editor and delete that single
byte I added at the end in the previous step, show that replication still
Server1: (dir after deleting 1 byte at the end)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,205,595,648 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 18,127,482,880 bytes free
Post by Ned Pyle (MSFT)
I was hiding. :-)
Interesting issue. Even though it seems very unlikely based on what you
describe below, I would recommend checking out the following with DFSGUI.MSC
---------
1. Open the root
2. Under it, rt-click the link and choose properties.
*.bak,*.tmp,~*
---------
If for some reason we see *.jpg there, it's being filtered. Very unlikely,
but worth the 10 seconds it will take to check.
It sounds more like there's some problem with files being locked. FRS will
not replicate files that are in use. Does some application service utilize
this namespace, just for JPG files? Are you letting your Anti-virus software
scan the DFS file structure (if so, just for testing, tell it to
ignore
that
directory tree temporarily and restart the service or computers).
As you can tell, I'm reaching at straws here. Based on your exact
description below, it doesn't make a lot of sense (especially when you
rename a file and it still fails to replicate until you open and close it
with notepad- that makes file locks and filters unlikely).
Let me know what you see,
Ned
Post by Minas
Hello Ned Pyle,
I see you watch and answer to most questions in this group. You left my
question unanswered though...
Can you please advise where should I look into to troubleshoot this problem.
Please let me know if any additional details are needed.
Thanks,
Minas.
Post by Minas
Hello,
I have a strange problem with file replication, please show me a direction
if there is any.
I have two domain controllers in the network, each running Windows 2003,
Service Pack 1.
I created a distributed file system root on one of them, shared a
folder
on
each of these servers, added a link into the DFS root and specified
these
two
shares as targets. The system log shows everything went all right and
replication has started for this DFS link.
I could check that I can create a new file on one of these shares
and see
it
getting replicated in the other. Then I populated one of the shares with
production data and waited for the replication to complete. Almost everything
got replicated, except of some jpg files! These files have names like
137_3703.JPG and first visible difference difference between these
files
from
other jpg files (which replicated successfully) was that they were larger
(>1Meg). I have other files though which are much larger and have replicated
without any problems.
Checked security permissions of these files and they are no
different
than
others.
Another interesting observation: any copies of these unreplicated files
(created in file explorer window) do not replicate neither. I changed the
name, changed extension (changed .jpg to .txt), edited and deleted everything
in them -- no change -- these files do not get replicated. But if I
open
in
an editor and do "save
as" to a new name -- the new file gets replicated.
Installed sonar, could not see any errors.
Has anyone had similar problems? Am I missing something? Please help.
Thanks,
Minas
2006-04-12 14:10:30 UTC
Permalink
Thanks Ned,

I'll give another try to resolve this through the newsgroup.

I ran FILEVER and ATTRIB and did not see any significant difference between
attributes of replicating and non-replicating files.

I also ran frsdiag. I tried to send the cab files but got an error message
that the message is too large. Is there an alternative way to deliver this
to you? My email address is ***@yahoo.com.

Please help me with this last effort, I'll drop it if nothing shows here
neither.

Thanks a lot,
Minas.
Post by Ned Pyle (MSFT)
The FC command can be used to compare two files at a binary level and tell
differences between them (that's in box in 2003).
The FILEVER /V command can tell about further internal file metadata.
The ATTRIB command can tell basic attribute information about a file.
There are further PSS tools we can send out if you open a case.
I'd be interested in seeing what FRSDIAG has to offer, run on both the
upstream and downstream servers.
http://www.microsoft.com/downloads/details.aspx?FamilyID=43cb658e-8553-4de7-811a-562563eb5ebf&DisplayLang=en .
Honestly though, this looks like it's going to demand more attention than
the newsgroup will be able to answer in a timely manner. If you don't mind
waiting though, just attach the cabs and I'll look.
Ned
Post by Minas
One more thing I found out is that the contents of the file doesn't have
anything to do with the problem -- I opened new_file.txt in the hex editor
and replaced everythig in it with '00' character (ASCII code 0). the file did
not replicate after I saved the file. Once again, it replicated as soon
as
I
added one byte to the end of the file.
It seams there is a problem in the ntfs attributes for the file which gets
copied from one file to the other until the size is changed. Is there a
command to access all attributes for a file?
Thanks,
Minas.
Post by Minas
Hello Ned, thank you for your reply.
I tried all you said in your message and the problem did not resolve. To
show you what is actually happening, I ran several commands in command prompt
on server1.
-There is a certain file which does not replicate when copied into one of
replicated folders
-Any copes of this file do not replicate neither
-The file starts replicating as soon as I add a single byte to the end of
file (increase the size by 1 byte) using Hex Editor
Server1: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 118,211,911,680 bytes free
Server2: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,124,161,024 bytes free
Copy 136_3693.JPG file from a temp directory which I know will replicate
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3693.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 118,211,862,528 bytes free
Server2: (show contents, replication success)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3697.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:40 AM <DIR> .
04/11/2006 07:40 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 118,209,482,752 bytes free
Server2: (show contents, replication did not happen)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
On Server1, Copy the non-replicated file 136_3697.JPG to new_file.txt file;
D:\Manufacturing>copy 136_3697.JPG new_file.txt
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:51 AM <DIR> .
04/11/2006 07:51 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,207,102,976 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:49 AM <DIR> .
04/11/2006 07:49 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,134,749,184 bytes free
On Server1, open 136_3697.JPG in a hex editor and add a single byte to the
Server1: (dir after editing in Hex Editor program)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 118,205,399,040 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,129,989,632 bytes free
On Server 1, open the same file again in Hex Editor and delete that single
byte I added at the end in the previous step, show that replication still
Server1: (dir after deleting 1 byte at the end)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,205,595,648 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 18,127,482,880 bytes free
Post by Ned Pyle (MSFT)
I was hiding. :-)
Interesting issue. Even though it seems very unlikely based on what you
describe below, I would recommend checking out the following with DFSGUI.MSC
---------
1. Open the root
2. Under it, rt-click the link and choose properties.
*.bak,*.tmp,~*
---------
If for some reason we see *.jpg there, it's being filtered. Very unlikely,
but worth the 10 seconds it will take to check.
It sounds more like there's some problem with files being locked. FRS will
not replicate files that are in use. Does some application service utilize
this namespace, just for JPG files? Are you letting your Anti-virus software
scan the DFS file structure (if so, just for testing, tell it to
ignore
that
directory tree temporarily and restart the service or computers).
As you can tell, I'm reaching at straws here. Based on your exact
description below, it doesn't make a lot of sense (especially when you
rename a file and it still fails to replicate until you open and close it
with notepad- that makes file locks and filters unlikely).
Let me know what you see,
Ned
Post by Minas
Hello Ned Pyle,
I see you watch and answer to most questions in this group. You left my
question unanswered though...
Can you please advise where should I look into to troubleshoot this problem.
Please let me know if any additional details are needed.
Thanks,
Minas.
Post by Minas
Hello,
I have a strange problem with file replication, please show me a direction
if there is any.
I have two domain controllers in the network, each running Windows 2003,
Service Pack 1.
I created a distributed file system root on one of them, shared a
folder
on
each of these servers, added a link into the DFS root and specified
these
two
shares as targets. The system log shows everything went all right and
replication has started for this DFS link.
I could check that I can create a new file on one of these shares
and see
it
getting replicated in the other. Then I populated one of the shares with
production data and waited for the replication to complete. Almost everything
got replicated, except of some jpg files! These files have names like
137_3703.JPG and first visible difference difference between these
files
from
other jpg files (which replicated successfully) was that they were larger
(>1Meg). I have other files though which are much larger and have replicated
without any problems.
Checked security permissions of these files and they are no
different
than
others.
Another interesting observation: any copies of these unreplicated files
(created in file explorer window) do not replicate neither. I changed the
name, changed extension (changed .jpg to .txt), edited and deleted everything
in them -- no change -- these files do not get replicated. But if I
open
in
an editor and do "save
as" to a new name -- the new file gets replicated.
Installed sonar, could not see any errors.
Has anyone had similar problems? Am I missing something? Please help.
Thanks,
Ned Pyle (MSFT)
2006-04-12 16:05:42 UTC
Permalink
Hi,

If you can share the CAB's somewhere I can get to them (do you have an FTP
server or the like?) I can grab them. Otherwise you are going to need to
open a case and work it normally through an engineer here, and they can use
the upload system (which is tied to a support case).
Post by Minas
Thanks Ned,
I'll give another try to resolve this through the newsgroup.
I ran FILEVER and ATTRIB and did not see any significant difference between
attributes of replicating and non-replicating files.
I also ran frsdiag. I tried to send the cab files but got an error message
that the message is too large. Is there an alternative way to deliver this
Please help me with this last effort, I'll drop it if nothing shows here
neither.
Thanks a lot,
Minas.
Post by Ned Pyle (MSFT)
The FC command can be used to compare two files at a binary level and tell
differences between them (that's in box in 2003).
The FILEVER /V command can tell about further internal file metadata.
The ATTRIB command can tell basic attribute information about a file.
There are further PSS tools we can send out if you open a case.
I'd be interested in seeing what FRSDIAG has to offer, run on both the
upstream and downstream servers.
http://www.microsoft.com/downloads/details.aspx?FamilyID=43cb658e-8553-4de7-811a-562563eb5ebf&DisplayLang=en .
Honestly though, this looks like it's going to demand more attention than
the newsgroup will be able to answer in a timely manner. If you don't mind
waiting though, just attach the cabs and I'll look.
Ned
Post by Minas
One more thing I found out is that the contents of the file doesn't have
anything to do with the problem -- I opened new_file.txt in the hex editor
and replaced everythig in it with '00' character (ASCII code 0). the
file
did
not replicate after I saved the file. Once again, it replicated as soon
as
I
added one byte to the end of the file.
It seams there is a problem in the ntfs attributes for the file which gets
copied from one file to the other until the size is changed. Is there a
command to access all attributes for a file?
Thanks,
Minas.
Post by Minas
Hello Ned, thank you for your reply.
I tried all you said in your message and the problem did not resolve. To
show you what is actually happening, I ran several commands in command prompt
on server1.
-There is a certain file which does not replicate when copied into one of
replicated folders
-Any copes of this file do not replicate neither
-The file starts replicating as soon as I add a single byte to the end of
file (increase the size by 1 byte) using Hex Editor
Server1: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 118,211,911,680 bytes free
Server2: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,124,161,024 bytes free
Copy 136_3693.JPG file from a temp directory which I know will replicate
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3693.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 118,211,862,528 bytes free
Server2: (show contents, replication success)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3697.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:40 AM <DIR> .
04/11/2006 07:40 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 118,209,482,752 bytes free
Server2: (show contents, replication did not happen)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
On Server1, Copy the non-replicated file 136_3697.JPG to new_file.txt file;
D:\Manufacturing>copy 136_3697.JPG new_file.txt
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:51 AM <DIR> .
04/11/2006 07:51 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,207,102,976 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:49 AM <DIR> .
04/11/2006 07:49 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,134,749,184 bytes free
On Server1, open 136_3697.JPG in a hex editor and add a single byte to the
Server1: (dir after editing in Hex Editor program)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 118,205,399,040 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,129,989,632 bytes free
On Server 1, open the same file again in Hex Editor and delete that single
byte I added at the end in the previous step, show that replication still
Server1: (dir after deleting 1 byte at the end)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,205,595,648 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 18,127,482,880 bytes free
Post by Ned Pyle (MSFT)
I was hiding. :-)
Interesting issue. Even though it seems very unlikely based on what you
describe below, I would recommend checking out the following with DFSGUI.MSC
---------
1. Open the root
2. Under it, rt-click the link and choose properties.
*.bak,*.tmp,~*
---------
If for some reason we see *.jpg there, it's being filtered. Very unlikely,
but worth the 10 seconds it will take to check.
It sounds more like there's some problem with files being locked. FRS will
not replicate files that are in use. Does some application service utilize
this namespace, just for JPG files? Are you letting your Anti-virus software
scan the DFS file structure (if so, just for testing, tell it to
ignore
that
directory tree temporarily and restart the service or computers).
As you can tell, I'm reaching at straws here. Based on your exact
description below, it doesn't make a lot of sense (especially when you
rename a file and it still fails to replicate until you open and
close
it
with notepad- that makes file locks and filters unlikely).
Let me know what you see,
Ned
Post by Minas
Hello Ned Pyle,
I see you watch and answer to most questions in this group. You
left
my
question unanswered though...
Can you please advise where should I look into to troubleshoot this problem.
Please let me know if any additional details are needed.
Thanks,
Minas.
Post by Minas
Hello,
I have a strange problem with file replication, please show me a direction
if there is any.
I have two domain controllers in the network, each running Windows 2003,
Service Pack 1.
I created a distributed file system root on one of them, shared a
folder
on
each of these servers, added a link into the DFS root and specified
these
two
shares as targets. The system log shows everything went all right and
replication has started for this DFS link.
I could check that I can create a new file on one of these shares
and see
it
getting replicated in the other. Then I populated one of the
shares
with
production data and waited for the replication to complete. Almost
everything
got replicated, except of some jpg files! These files have names like
137_3703.JPG and first visible difference difference between these
files
from
other jpg files (which replicated successfully) was that they were larger
(>1Meg). I have other files though which are much larger and have
replicated
without any problems.
Checked security permissions of these files and they are no
different
than
others.
Another interesting observation: any copies of these unreplicated files
(created in file explorer window) do not replicate neither. I changed the
name, changed extension (changed .jpg to .txt), edited and deleted
everything
in them -- no change -- these files do not get replicated. But if I
open
in
an editor and do "save
as" to a new name -- the new file gets replicated.
Installed sonar, could not see any errors.
Has anyone had similar problems? Am I missing something? Please help.
Thanks,
Minas Hambardzumyan
2006-04-12 17:10:40 UTC
Permalink
Please download them from folowing links:

http://vorotan.com/server1_on_2006-04-12_at_8.17.57_AM_FRSDiag.CAB
http://vorotan.com/server2_on_2006-04-12_at_8.13.26_AM_FRSDiag.CAB

Minas
Post by Ned Pyle (MSFT)
Hi,
If you can share the CAB's somewhere I can get to them (do you have an FTP
server or the like?) I can grab them. Otherwise you are going to need to
open a case and work it normally through an engineer here, and they can
use the upload system (which is tied to a support case).
Post by Minas
Thanks Ned,
I'll give another try to resolve this through the newsgroup.
I ran FILEVER and ATTRIB and did not see any significant difference between
attributes of replicating and non-replicating files.
I also ran frsdiag. I tried to send the cab files but got an error message
that the message is too large. Is there an alternative way to deliver this
Please help me with this last effort, I'll drop it if nothing shows here
neither.
Thanks a lot,
Minas.
Post by Ned Pyle (MSFT)
The FC command can be used to compare two files at a binary level and tell
differences between them (that's in box in 2003).
The FILEVER /V command can tell about further internal file metadata.
The ATTRIB command can tell basic attribute information about a file.
There are further PSS tools we can send out if you open a case.
I'd be interested in seeing what FRSDIAG has to offer, run on both the
upstream and downstream servers.
http://www.microsoft.com/downloads/details.aspx?FamilyID=43cb658e-8553-4de7-811a-562563eb5ebf&DisplayLang=en .
Honestly though, this looks like it's going to demand more attention than
the newsgroup will be able to answer in a timely manner. If you don't mind
waiting though, just attach the cabs and I'll look.
Ned
Post by Minas
One more thing I found out is that the contents of the file doesn't have
anything to do with the problem -- I opened new_file.txt in the hex editor
and replaced everythig in it with '00' character (ASCII code 0). the
file
did
not replicate after I saved the file. Once again, it replicated as soon
as
I
added one byte to the end of the file.
It seams there is a problem in the ntfs attributes for the file which gets
copied from one file to the other until the size is changed. Is there a
command to access all attributes for a file?
Thanks,
Minas.
Post by Minas
Hello Ned, thank you for your reply.
I tried all you said in your message and the problem did not resolve. To
show you what is actually happening, I ran several commands in command prompt
on server1.
-There is a certain file which does not replicate when copied into one of
replicated folders
-Any copes of this file do not replicate neither
-The file starts replicating as soon as I add a single byte to the end of
file (increase the size by 1 byte) using Hex Editor
Server1: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 118,211,911,680 bytes free
Server2: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,124,161,024 bytes free
Copy 136_3693.JPG file from a temp directory which I know will replicate
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3693.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 118,211,862,528 bytes free
Server2: (show contents, replication success)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3697.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:40 AM <DIR> .
04/11/2006 07:40 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 118,209,482,752 bytes free
Server2: (show contents, replication did not happen)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
On Server1, Copy the non-replicated file 136_3697.JPG to new_file.txt file;
D:\Manufacturing>copy 136_3697.JPG new_file.txt
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:51 AM <DIR> .
04/11/2006 07:51 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,207,102,976 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:49 AM <DIR> .
04/11/2006 07:49 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,134,749,184 bytes free
On Server1, open 136_3697.JPG in a hex editor and add a single byte to the
Server1: (dir after editing in Hex Editor program)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 118,205,399,040 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,129,989,632 bytes free
On Server 1, open the same file again in Hex Editor and delete that single
byte I added at the end in the previous step, show that replication still
Server1: (dir after deleting 1 byte at the end)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,205,595,648 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 18,127,482,880 bytes free
Post by Ned Pyle (MSFT)
I was hiding. :-)
Interesting issue. Even though it seems very unlikely based on what you
describe below, I would recommend checking out the following with DFSGUI.MSC
---------
1. Open the root
2. Under it, rt-click the link and choose properties.
*.bak,*.tmp,~*
---------
If for some reason we see *.jpg there, it's being filtered. Very unlikely,
but worth the 10 seconds it will take to check.
It sounds more like there's some problem with files being locked.
FRS
will
not replicate files that are in use. Does some application service utilize
this namespace, just for JPG files? Are you letting your Anti-virus software
scan the DFS file structure (if so, just for testing, tell it to
ignore
that
directory tree temporarily and restart the service or computers).
As you can tell, I'm reaching at straws here. Based on your exact
description below, it doesn't make a lot of sense (especially when you
rename a file and it still fails to replicate until you open and
close
it
with notepad- that makes file locks and filters unlikely).
Let me know what you see,
Ned
Post by Minas
Hello Ned Pyle,
I see you watch and answer to most questions in this group. You
left
my
question unanswered though...
Can you please advise where should I look into to troubleshoot
this
problem.
Please let me know if any additional details are needed.
Thanks,
Minas.
Post by Minas
Hello,
I have a strange problem with file replication, please show me a
direction
if there is any.
I have two domain controllers in the network, each running
Windows
2003,
Service Pack 1.
I created a distributed file system root on one of them, shared a
folder
on
each of these servers, added a link into the DFS root and specified
these
two
shares as targets. The system log shows everything went all right and
replication has started for this DFS link.
I could check that I can create a new file on one of these shares
and see
it
getting replicated in the other. Then I populated one of the
shares
with
production data and waited for the replication to complete. Almost
everything
got replicated, except of some jpg files! These files have names like
137_3703.JPG and first visible difference difference between these
files
from
other jpg files (which replicated successfully) was that they
were
larger
(>1Meg). I have other files though which are much larger and have
replicated
without any problems.
Checked security permissions of these files and they are no
different
than
others.
Another interesting observation: any copies of these unreplicated files
(created in file explorer window) do not replicate neither. I changed the
name, changed extension (changed .jpg to .txt), edited and deleted
everything
in them -- no change -- these files do not get replicated. But if I
open
in
an editor and do "save
as" to a new name -- the new file gets replicated.
Installed sonar, could not see any errors.
Has anyone had similar problems? Am I missing something? Please help.
Thanks,
Ned Pyle (MSFT)
2006-04-12 22:32:42 UTC
Permalink
Grabbed 'em. Sorry for the dealy, it's been one of those days. I will
examine these and get back to you ASAP.

Ned
Post by Minas Hambardzumyan
http://vorotan.com/server1_on_2006-04-12_at_8.17.57_AM_FRSDiag.CAB
http://vorotan.com/server2_on_2006-04-12_at_8.13.26_AM_FRSDiag.CAB
Minas
Post by Ned Pyle (MSFT)
Hi,
If you can share the CAB's somewhere I can get to them (do you have an
FTP server or the like?) I can grab them. Otherwise you are going to need
to open a case and work it normally through an engineer here, and they
can use the upload system (which is tied to a support case).
Post by Minas
Thanks Ned,
I'll give another try to resolve this through the newsgroup.
I ran FILEVER and ATTRIB and did not see any significant difference between
attributes of replicating and non-replicating files.
I also ran frsdiag. I tried to send the cab files but got an error message
that the message is too large. Is there an alternative way to deliver this
Please help me with this last effort, I'll drop it if nothing shows here
neither.
Thanks a lot,
Minas.
Post by Ned Pyle (MSFT)
The FC command can be used to compare two files at a binary level and tell
differences between them (that's in box in 2003).
The FILEVER /V command can tell about further internal file metadata.
The ATTRIB command can tell basic attribute information about a file.
There are further PSS tools we can send out if you open a case.
I'd be interested in seeing what FRSDIAG has to offer, run on both the
upstream and downstream servers.
http://www.microsoft.com/downloads/details.aspx?FamilyID=43cb658e-8553-4de7-811a-562563eb5ebf&DisplayLang=en .
Honestly though, this looks like it's going to demand more attention than
the newsgroup will be able to answer in a timely manner. If you don't mind
waiting though, just attach the cabs and I'll look.
Ned
Post by Minas
One more thing I found out is that the contents of the file doesn't have
anything to do with the problem -- I opened new_file.txt in the hex editor
and replaced everythig in it with '00' character (ASCII code 0). the
file
did
not replicate after I saved the file. Once again, it replicated as soon
as
I
added one byte to the end of the file.
It seams there is a problem in the ntfs attributes for the file which gets
copied from one file to the other until the size is changed. Is there a
command to access all attributes for a file?
Thanks,
Minas.
Post by Minas
Hello Ned, thank you for your reply.
I tried all you said in your message and the problem did not resolve. To
show you what is actually happening, I ran several commands in
command
prompt
on server1.
-There is a certain file which does not replicate when copied into
one
of
replicated folders
-Any copes of this file do not replicate neither
-The file starts replicating as soon as I add a single byte to the
end
of
file (increase the size by 1 byte) using Hex Editor
Server1: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 118,211,911,680 bytes free
Server2: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,124,161,024 bytes free
Copy 136_3693.JPG file from a temp directory which I know will replicate
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3693.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 118,211,862,528 bytes free
Server2: (show contents, replication success)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3697.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:40 AM <DIR> .
04/11/2006 07:40 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 118,209,482,752 bytes free
Server2: (show contents, replication did not happen)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
On Server1, Copy the non-replicated file 136_3697.JPG to new_file.txt file;
D:\Manufacturing>copy 136_3697.JPG new_file.txt
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:51 AM <DIR> .
04/11/2006 07:51 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,207,102,976 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:49 AM <DIR> .
04/11/2006 07:49 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,134,749,184 bytes free
On Server1, open 136_3697.JPG in a hex editor and add a single byte
to
the
Server1: (dir after editing in Hex Editor program)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 118,205,399,040 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,129,989,632 bytes free
On Server 1, open the same file again in Hex Editor and delete that single
byte I added at the end in the previous step, show that replication still
Server1: (dir after deleting 1 byte at the end)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,205,595,648 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 18,127,482,880 bytes free
Post by Ned Pyle (MSFT)
I was hiding. :-)
Interesting issue. Even though it seems very unlikely based on what you
describe below, I would recommend checking out the following with DFSGUI.MSC
---------
1. Open the root
2. Under it, rt-click the link and choose properties.
*.bak,*.tmp,~*
---------
If for some reason we see *.jpg there, it's being filtered. Very unlikely,
but worth the 10 seconds it will take to check.
It sounds more like there's some problem with files being locked.
FRS
will
not replicate files that are in use. Does some application service utilize
this namespace, just for JPG files? Are you letting your Anti-virus software
scan the DFS file structure (if so, just for testing, tell it to
ignore
that
directory tree temporarily and restart the service or computers).
As you can tell, I'm reaching at straws here. Based on your exact
description below, it doesn't make a lot of sense (especially when you
rename a file and it still fails to replicate until you open and
close
it
with notepad- that makes file locks and filters unlikely).
Let me know what you see,
Ned
Post by Minas
Hello Ned Pyle,
I see you watch and answer to most questions in this group. You
left
my
question unanswered though...
Can you please advise where should I look into to troubleshoot
this
problem.
Please let me know if any additional details are needed.
Thanks,
Minas.
Post by Minas
Hello,
I have a strange problem with file replication, please show me a
direction
if there is any.
I have two domain controllers in the network, each running
Windows
2003,
Service Pack 1.
I created a distributed file system root on one of them, shared a
folder
on
each of these servers, added a link into the DFS root and specified
these
two
shares as targets. The system log shows everything went all
right
and
replication has started for this DFS link.
I could check that I can create a new file on one of these shares
and see
it
getting replicated in the other. Then I populated one of the
shares
with
production data and waited for the replication to complete. Almost
everything
got replicated, except of some jpg files! These files have names like
137_3703.JPG and first visible difference difference between these
files
from
other jpg files (which replicated successfully) was that they
were
larger
(>1Meg). I have other files though which are much larger and have
replicated
without any problems.
Checked security permissions of these files and they are no
different
than
others.
Another interesting observation: any copies of these
unreplicated
files
(created in file explorer window) do not replicate neither. I
changed the
name, changed extension (changed .jpg to .txt), edited and deleted
everything
in them -- no change -- these files do not get replicated. But if I
open
in
an editor and do "save
as" to a new name -- the new file gets replicated.
Installed sonar, could not see any errors.
Has anyone had similar problems? Am I missing something? Please help.
Thanks,
Ned Pyle (MSFT)
2006-04-13 13:23:42 UTC
Permalink
I must admit, I'm a bit confused here:

From basic examination, everything looks good - no misconfig, no old FRS, no
filters - all is well. So I dug further into the NTFRS_0005.log from both
servers. What I see is:

On server1, 136_3697.txt is renamed to 136_3697.jpg and change order is sent
out (at 4/11-07:33:29).
On server2, 136_3697.jpg is transferred in successfully to pre-install (at
4/11-07:33:29)
At 4/11-07:34:27, it's done again, and works again.
At 4/11-07:44:28 , it looks like maybe the file was overwritten with the
same file? It replicates again without issues.
At 4/11-07:46:40, we get a temporary copy of the file (was this when it was
opened in a hex editor?)
At 4/11-07:46:41 the 136_3697.jpg.Hex Editor 3 temp save file shows up -
that replicates fine too.

So, the logs claim everything is replicating normally. I must admit - I'm
scratching my head here, Minas.

Ned
Post by Ned Pyle (MSFT)
Grabbed 'em. Sorry for the dealy, it's been one of those days. I will
examine these and get back to you ASAP.
Ned
Post by Minas Hambardzumyan
http://vorotan.com/server1_on_2006-04-12_at_8.17.57_AM_FRSDiag.CAB
http://vorotan.com/server2_on_2006-04-12_at_8.13.26_AM_FRSDiag.CAB
Minas
Post by Ned Pyle (MSFT)
Hi,
If you can share the CAB's somewhere I can get to them (do you have an
FTP server or the like?) I can grab them. Otherwise you are going to
need to open a case and work it normally through an engineer here, and
they can use the upload system (which is tied to a support case).
Post by Minas
Thanks Ned,
I'll give another try to resolve this through the newsgroup.
I ran FILEVER and ATTRIB and did not see any significant difference between
attributes of replicating and non-replicating files.
I also ran frsdiag. I tried to send the cab files but got an error message
that the message is too large. Is there an alternative way to deliver this
Please help me with this last effort, I'll drop it if nothing shows here
neither.
Thanks a lot,
Minas.
Post by Ned Pyle (MSFT)
The FC command can be used to compare two files at a binary level and tell
differences between them (that's in box in 2003).
The FILEVER /V command can tell about further internal file metadata.
The ATTRIB command can tell basic attribute information about a file.
There are further PSS tools we can send out if you open a case.
I'd be interested in seeing what FRSDIAG has to offer, run on both the
upstream and downstream servers.
http://www.microsoft.com/downloads/details.aspx?FamilyID=43cb658e-8553-4de7-811a-562563eb5ebf&DisplayLang=en .
Honestly though, this looks like it's going to demand more attention than
the newsgroup will be able to answer in a timely manner. If you don't mind
waiting though, just attach the cabs and I'll look.
Ned
Post by Minas
One more thing I found out is that the contents of the file doesn't have
anything to do with the problem -- I opened new_file.txt in the hex editor
and replaced everythig in it with '00' character (ASCII code 0). the
file
did
not replicate after I saved the file. Once again, it replicated as soon
as
I
added one byte to the end of the file.
It seams there is a problem in the ntfs attributes for the file which gets
copied from one file to the other until the size is changed. Is there a
command to access all attributes for a file?
Thanks,
Minas.
Post by Minas
Hello Ned, thank you for your reply.
I tried all you said in your message and the problem did not resolve. To
show you what is actually happening, I ran several commands in
command
prompt
on server1.
-There is a certain file which does not replicate when copied into
one
of
replicated folders
-Any copes of this file do not replicate neither
-The file starts replicating as soon as I add a single byte to the
end
of
file (increase the size by 1 byte) using Hex Editor
Server1: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 118,211,911,680 bytes free
Server2: (show empty)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:34 AM <DIR> .
04/11/2006 07:34 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,124,161,024 bytes free
Copy 136_3693.JPG file from a temp directory which I know will replicate
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3693.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 118,211,862,528 bytes free
Server2: (show contents, replication success)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
Server1: ( copy and show contents)
D:\Manufacturing>copy d:\temp\frs_test_files\136_3697.JPG .
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:40 AM <DIR> .
04/11/2006 07:40 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 118,209,482,752 bytes free
Server2: (show contents, replication did not happen)
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:37 AM <DIR> .
04/11/2006 07:37 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,124,111,872 bytes free
On Server1, Copy the non-replicated file 136_3697.JPG to
new_file.txt
file;
D:\Manufacturing>copy 136_3697.JPG new_file.txt
1 file(s) copied.
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:51 AM <DIR> .
04/11/2006 07:51 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,207,102,976 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:49 AM <DIR> .
04/11/2006 07:49 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,134,749,184 bytes free
On Server1, open 136_3697.JPG in a hex editor and add a single byte
to
the
Server1: (dir after editing in Hex Editor program)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 118,205,399,040 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:54 AM <DIR> .
04/11/2006 07:54 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:54 AM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,129,989,632 bytes free
On Server 1, open the same file again in Hex Editor and delete that single
byte I added at the end in the previous step, show that replication still
Server1: (dir after deleting 1 byte at the end)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 new_file.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 118,205,595,648 bytes free
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/11/2006 07:56 AM <DIR> .
04/11/2006 07:56 AM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/11/2006 07:56 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 18,127,482,880 bytes free
Post by Ned Pyle (MSFT)
I was hiding. :-)
Interesting issue. Even though it seems very unlikely based on
what
you
describe below, I would recommend checking out the following with
DFSGUI.MSC
---------
1. Open the root
2. Under it, rt-click the link and choose properties.
*.bak,*.tmp,~*
---------
If for some reason we see *.jpg there, it's being filtered. Very unlikely,
but worth the 10 seconds it will take to check.
It sounds more like there's some problem with files being locked.
FRS
will
not replicate files that are in use. Does some application service utilize
this namespace, just for JPG files? Are you letting your
Anti-virus
software
scan the DFS file structure (if so, just for testing, tell it to
ignore
that
directory tree temporarily and restart the service or computers).
As you can tell, I'm reaching at straws here. Based on your exact
description below, it doesn't make a lot of sense (especially when you
rename a file and it still fails to replicate until you open and
close
it
with notepad- that makes file locks and filters unlikely).
Let me know what you see,
Ned
Post by Minas
Hello Ned Pyle,
I see you watch and answer to most questions in this group. You
left
my
question unanswered though...
Can you please advise where should I look into to troubleshoot
this
problem.
Please let me know if any additional details are needed.
Thanks,
Minas.
Post by Minas
Hello,
I have a strange problem with file replication, please show me a
direction
if there is any.
I have two domain controllers in the network, each running
Windows
2003,
Service Pack 1.
I created a distributed file system root on one of them, shared a
folder
on
each of these servers, added a link into the DFS root and specified
these
two
shares as targets. The system log shows everything went all
right
and
replication has started for this DFS link.
I could check that I can create a new file on one of these shares
and see
it
getting replicated in the other. Then I populated one of the
shares
with
production data and waited for the replication to complete. Almost
everything
got replicated, except of some jpg files! These files have
names
like
137_3703.JPG and first visible difference difference between these
files
from
other jpg files (which replicated successfully) was that they
were
larger
(>1Meg). I have other files though which are much larger and have
replicated
without any problems.
Checked security permissions of these files and they are no
different
than
others.
Another interesting observation: any copies of these
unreplicated
files
(created in file explorer window) do not replicate neither. I
changed the
name, changed extension (changed .jpg to .txt), edited and deleted
everything
in them -- no change -- these files do not get replicated. But if I
open
in
an editor and do "save
as" to a new name -- the new file gets replicated.
Installed sonar, could not see any errors.
Has anyone had similar problems? Am I missing something? Please help.
Thanks,
Minas Hambardzumyan
2006-04-13 21:02:11 UTC
Permalink
Ned,

I started my test after 7:34am (you can see this by looking at the date/time
on directories "." and ".." in my message). So the only log entry that is
very suspicious is the one at 7:44am.

To make sure we are looking at right data at right time, I repeated my
actions -- now recording the time of each command execution. I have the
transcript below. According to it, I ran commands from 14:19 to 14:31. I ran
FRSDIAG on both servers after finishing my commands and have frs logs
between those time points also inserted here. The first log reference to
file name 136_3697.JPG is at 14:30:02 on Server#1 and 13:30:03 on Server#2.
This is right after I added a single byte in the hex editor (my dir command
after it was executed at 14:30:09). Also, there is no reference to the
136_3697.TXT in the log files.

Looks like the file actually does not get replicated. To finish once and
forever I decided to send my failing file to you -- to see if it will get
replicated on your side. This is where interesting things started to happen.
I will write about those in my next message -- not to mix with the mess I
have here.

Minas.

Server#1: The current time is: 14:19:48.25 (Empty Directory)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467

Directory of D:\Manufacturing

04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 116,651,122,688 bytes free

Server#2: The current time is: 14:19:52.63
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248

Directory of D:\Manufacturing

04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,077,216,768 bytes free


Server#1: The current time is: 14:21:31.80 (copy 136_3693.JPG which
replicates)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467

Directory of D:\Manufacturing

04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 116,651,040,768 bytes free

Server#2: The current time is: 14:21:33.85
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248

Directory of D:\Manufacturing

04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,134,848 bytes free

Server#1: The current time is: 14:22:40.27 (copy 136_3697.JPG which does not
replicate)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467

Directory of D:\Manufacturing

04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free

server#2: The current time is: 14:22:41.59
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248

Directory of D:\Manufacturing

04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free

Server#1: The current time is: 14:25:30.76 (fill 136_3697.JPG with ASCII 0
character, still no replication)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467

Directory of D:\Manufacturing

04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free

Server#2: The current time is: 14:25:31.57
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248

Directory of D:\Manufacturing

04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free


Server#1: The current time is: 14:28:01.16 (copy 136_3697.JPG 136_3697.txt,
no replication for both)
Enter the new time:

D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467

Directory of D:\Manufacturing

04/13/2006 02:27 PM <DIR> .
04/13/2006 02:27 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 116,646,313,984 bytes free

Server#2: The current time is: 14:28:02.18
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248

Directory of D:\Manufacturing

04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free

Server#1: The current time is: 14:30:09.99 (after adding 1 byte to the end
of 136_3697.JPG, now replication worked for 136_3697.JPG)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467

Directory of D:\Manufacturing

04/13/2006 02:29 PM <DIR> .
04/13/2006 02:29 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/13/2006 02:29 PM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 116,646,305,792 bytes free

Server#2: The current time is: 14:30:11.14
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248

Directory of D:\Manufacturing

04/13/2006 02:30 PM <DIR> .
04/13/2006 02:30 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/13/2006 02:29 PM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,074,779,648 bytes free



Server#1 FRS Log:
<FrsStageCsSubmitTransfer: 5988: 1828: S1: 14:21:22> Stage: submit
transfer 0xf6faa8
<ProcessOpenByIdStatus: 4452: 3025: S1: 14:21:22> ++
699e7b2a-1ea4-41bc-956f6431c20bf9b6 ObjectId Open failed; NTStatus:
STATUS_OPLOCK_NOT_GRANTED
<FrsOpenSourceFileById: 4452: 3372: S0: 14:21:22> ++ ERROR -
NtCreateFile failed : NTStatus: STATUS_OPLOCK_NOT_GRANTED
4/13-14:21:23 :T: CoG: 45c90bcc CxtG: 92dea886 [LclCo ] Name:
136_3693.JPG
4/13-14:21:23 :T: EventTime: Thu Apr 13, 2006 14:21:19 Ver:
0
4/13-14:21:23 :T: FileG: 699e7b2a-1ea4-41bc-956f6431c20bf9b6 FID:
00020000 00000b8e
4/13-14:21:23 :T: ParentG: 9dae1abb-37fd-4376-ac879c64a5cd61a2 Size:
00000000 0000c000
4/13-14:21:23 :T: OrigG: 28400de8-945d-4a0f-b3772d622dfdd28e Attr:
00000020
4/13-14:21:23 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
ReplicaName: AOS|MANUFACTURING (4)
4/13-14:21:23 :T: CoFlags: 0100042c [Content Locn LclCo NewFile
CmpresStage ]
4/13-14:21:23 :T: UsnReason: 00008003 [DatOvrWrt DatExt Info ]
4/13-14:21:23 :T: CxtionG: 92dea886-2851-4337-92e0ac801fcec1b8
4/13-14:21:23 :T: CheckSum: d3c1d9d5 75067e65 96a97ef1 e33dcd4c
4/13-14:21:23 :T: CoArrival: <null>
4/13-14:21:23 :T: FullPathName: \\.\D:\Manufacturing\136_3693.JPG
<FrsHashCalcString: 2660: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<FrsHashCalcString: 2660: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<FrsDsFindComputer: 2672: 8796: S2: 14:22:26> :DS: Computer
FQDN is cn=ofna,ou=domain controllers,dc=aos,dc=local
<FrsDsFindComputer: 2672: 8802: S2: 14:22:26> :DS: Computer's
dns name is ofna.AOS.local
<FrsDsFindComputer: 2672: 8816: S2: 14:22:26> :DS: Settings
reference is cn=ntds
settings,cn=ofna,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<FrsDsGetSubscribers: 2672: 8249: S0: 14:22:26> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2672: 8249: S0: 14:22:26> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<ThSupWaitThread: 3120: 505: S1: 14:26:23> :S: StageCs:
Waiting
<ThSupWaitThread: 3120: 533: S1: 14:26:23> :S: StageCs:
normal wait
<ThSupWaitThread: 3120: 505: S1: 14:26:23> :S: FetchCs:
Waiting
<ThSupWaitThread: 3120: 533: S1: 14:26:23> :S: FetchCs:
normal wait
<ThSupWaitThread: 3120: 505: S1: 14:26:23> :S: SndCs:
Waiting
<ThSupWaitThread: 3120: 533: S1: 14:26:23> :S: SndCs: normal
wait
<ThSupWaitThread: 3120: 505: S1: 14:27:26> :S: ReplicaCs:
Waiting
<ThSupWaitThread: 3120: 533: S1: 14:27:26> :S: ReplicaCs:
normal wait
<FrsDsFindComputer: 2672: 8796: S2: 14:27:26> :DS: Computer
FQDN is cn=ofna,ou=domain controllers,dc=aos,dc=local
<FrsDsFindComputer: 2672: 8802: S2: 14:27:26> :DS: Computer's
dns name is ofna.AOS.local
<FrsDsFindComputer: 2672: 8816: S2: 14:27:26> :DS: Settings
reference is cn=ntds
settings,cn=ofna,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<DbgPrintThreadIds: 2672: 1021: S2: 14:27:26> :H: Known thread
IDs -
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: First
: 440
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: Shutdown
: 2616
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: FrsDs
: 2672
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: SndCs
: 5472
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: DelCs
: 2776
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: OutLog
: 2780
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: ReplicaCs
: 4440
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: JRNL
: 2940
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: DBCs
: 2944
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: JrnlRead
: 3664
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: COAccept
: 3684
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: ChgOrdRetryCS
: 1376
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: Wait
: 880
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: ThCs
: 3120
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: VvJoinCs
: 3196
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: FetchCs
: 5964
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: StageCs
: 4452
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: InstallCs
: 2396
<FrsPrintAllocStats: 2672: 234: S2: 14:27:26>
<FrsPrintAllocStats: 2672: 235: S2: 14:27:26> NTFRS MEMORY
USAGE:
<FrsPrintAllocStats: 2672: 238: S2: 14:27:26> ENABLE STATS
: FALSE
<FrsPrintAllocStats: 2672: 242: S2: 14:27:26> Alloced
: 694537 KB (3350000 calls)
<FrsPrintAllocStats: 2672: 246: S2: 14:27:26> Freed
: 0 KB (0 calls)
<FrsPrintAllocStats: 2672: 249: S2: 14:27:26> Delta
: 0 KB
<FrsPrintAllocStats: 2672: 252: S2: 14:27:26> Max delta
: 0 KB
<FrsPrintAllocStats: 2672: 255: S2: 14:27:26> Addr Range
: 36522 KB
<FrsPrintAllocStats: 2672: 256: S2: 14:27:26> OnFreeList
: 0
<FrsPrintAllocStats: 2672: 257: S2: 14:27:26> ReAllocs
: 3346884
<FrsPrintAllocStats: 2672: 258: S2: 14:27:26> NewAllocs
: 3116
<FrsPrintAllocStats: 2672: 259: S2: 14:27:26> MinAddr
: 0x00255810
<FrsPrintAllocStats: 2672: 260: S2: 14:27:26> MaxAddr
: 0x02600060
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
THREAD_CONTEXT_TYPE : 14 Calls, 5 Max, 3 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
REPLICA_TYPE : 13608 Calls, 5 Max, 4 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
REPLICA_THREAD_TYPE : 13676 Calls, 11 Max, 2 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
CONFIG_NODE_TYPE : 144189 Calls, 21 Max, 1 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26> CXTION_TYPE
: 27219 Calls, 11 Max, 9 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26> GUID/RPC
HANDLE : 2 Calls, 2 Max, 2 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26> THREAD_TYPE
: 13270 Calls, 19 Max, 10 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
GEN_TABLE_TYPE : 135877 Calls, 47 Max, 39 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
JBUFFER_TYPE : 3 Calls, 3 Max, 3 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
VOLUME_MONITOR_ENTRY_TYPE : 2 Calls, 2 Max, 1 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
COMMAND_PACKET_TYPE : 178685 Calls, 24 Max, 13 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
GENERIC_HASH_TABLE_TYPE : 3 Calls, 3 Max, 3 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
CHANGE_ORDER_ENTRY_TYPE : 67 Calls, 11 Max, 0 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
FILTER_TABLE_ENTRY_TYPE : 26 Calls, 26 Max, 26 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
QHASH_TABLE_TYPE : 30 Calls, 25 Max, 23 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
OUT_LOG_PARTNER_TYPE : 4 Calls, 3 Max, 3 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
WILDCARD_FILTER_ENTRY_TYPE: 15 Calls, 15 Max, 15 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
REPARSE_TAG_TABLE_TYPE : 24360 Calls, 3 Max, 3 busy
<FrsPrintAllocStats: 2672: 270: S2: 14:27:26>
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 0 to
15 : 506712 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 16 to
31 : 602127 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 32 to
47 : 405311 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 48 to
63 : 46755 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 64 to
79 : 382512 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 80 to
95 : 227138 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 96 to
111 : 16375 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 112 to
127 : 41941 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 128 to
143 : 46735 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 144 to
159 : 168993 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 160 to
175 : 11013 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 176 to
191 : 106007 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 192 to
207 : 62546 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 208 to
223 : 64959 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 224 to
239 : 165087 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 240 to
255 : 48934 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 256 to
271 : 29230 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 272 to
287 : 52086 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 288 to
303 : 16243 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 304 to
319 : 21725 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 320 to
335 : 3 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 352 to
367 : 10974 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 368 to
383 : 10972 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 384 to
399 : 836 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 416 to
431 : 13609 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 512 to
527 : 8748 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 560 to
575 : 27218 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 608 to
623 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 640 to
655 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 784 to
799 : 41679 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 800 to
815 : 40614 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 848 to
863 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 864 to
879 : 13779 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 880 to
895 : 13667 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 944 to
959 : 27502 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 976 to
991 : 67 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1008 to
1023 : 13667 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1024 to
1039 : 6112 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1088 to
1103 : 13779 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1104 to
1119 : 13779 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1184 to
1199 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1200 to
1215 : 4 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1216 to
1231 : 27502 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1408 to
1423 : 55 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1616 to
1631 : 3 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1792 to
1807 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2048 to
2063 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2128 to
2143 : 13610 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2160 to
2175 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2480 to
2495 : 10 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2544 to
2559 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2736 to
2751 : 13610 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 3152 to
3167 : 11 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 3264 to
3279 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 4000 to
4015 : 13611 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 4096 to
4111 : 4 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 4976 to
4991 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 4992 to
5007 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 5504 to
5519 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 5632 to
5647 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 7856 to
7871 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 8192 to
8207 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 8448 to
8463 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 9744 to
9759 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 10368 to
10383 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 12080 to
12095 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 13120 to
13135 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 13696 to
13711 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 16368 to
16383 : 2119 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 280: S2: 14:27:26>
<FrsDsGetSubscribers: 2672: 8249: S0: 14:27:26> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<ThSupWaitThread: 3120: 505: S1: 14:27:26> :S: ReplicaCs:
Waiting
<ThSupWaitThread: 3120: 533: S1: 14:27:26> :S: ReplicaCs:
normal wait
<ThSupWaitThread: 3120: 505: S1: 14:27:26> :S: ReplicaCs:
Waiting
<ThSupWaitThread: 3120: 533: S1: 14:27:26> :S: ReplicaCs:
normal wait
<FrsDsGetSubscribers: 2672: 8249: S0: 14:27:26> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<FrsStageCsSubmitTransfer: 6104: 1828: S1: 14:30:02> Stage: submit
transfer 0xf6f980
<ProcessOpenByIdStatus: 4548: 3025: S1: 14:30:02> ++
7ff26913-b482-422f-873ebf0c7f6ffb77 ObjectId Open failed; NTStatus:
STATUS_OPLOCK_NOT_GRANTED
<FrsOpenSourceFileById: 4548: 3372: S0: 14:30:02> ++ ERROR -
NtCreateFile failed : NTStatus: STATUS_OPLOCK_NOT_GRANTED
4/13-14:30:02 :T: CoG: d7f4d1be CxtG: 92dea886 [LclCo ] Name:
136_3697.JPG
4/13-14:30:02 :T: EventTime: Thu Apr 13, 2006 14:29:59 Ver:
0
4/13-14:30:02 :T: FileG: 7ff26913-b482-422f-873ebf0c7f6ffb77 FID:
00020000 00000b94
4/13-14:30:02 :T: ParentG: 9dae1abb-37fd-4376-ac879c64a5cd61a2 Size:
00000000 00245000
4/13-14:30:02 :T: OrigG: 28400de8-945d-4a0f-b3772d622dfdd28e Attr:
00000120
4/13-14:30:02 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
ReplicaName: AOS|MANUFACTURING (4)
4/13-14:30:02 :T: CoFlags: 0100042c [Content Locn LclCo NewFile
CmpresStage ]
4/13-14:30:02 :T: UsnReason: 0000a803 [RenNew DatOvrWrt DatExt Info
Security ]
4/13-14:30:02 :T: CxtionG: 92dea886-2851-4337-92e0ac801fcec1b8
4/13-14:30:02 :T: CheckSum: 84893f8c f279b69f 9ec5d039 8a3713e0
4/13-14:30:02 :T: CoArrival: <null>
4/13-14:30:02 :T: FullPathName: \\.\D:\Manufacturing\136_3697.JPG
<FrsHashCalcString: 2660: 4842: S0: 14:30:02> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<FrsHashCalcString: 2660: 4842: S0: 14:30:03> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<RcsSetCxtionSchedule: 4312: 7365: S0: 14:30:32> :X: b454415e,
schedule is on
<RcsSetCxtionSchedule: 4312: 7365: S0: 14:30:32> :X: 242cdbff,
schedule is on
<RcsSetCxtionSchedule: 4312: 7365: S0: 14:30:32> :X: 6177bd09,
schedule is on
<RcsSetCxtionSchedule: 4312: 7365: S0: 14:30:32> :X: f938acb4,
schedule is on


Server#2 FRS log:
<FrsDsFindComputer: 2508: 8796: S2: 14:19:02> :DS: Computer
FQDN is cn=amber,ou=domain controllers,dc=aos,dc=local
<FrsDsFindComputer: 2508: 8802: S2: 14:19:02> :DS: Computer's
dns name is amber.AOS.local
<FrsDsFindComputer: 2508: 8816: S2: 14:19:02> :DS: Settings
reference is cn=ntds
settings,cn=amber,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<FrsDsGetSubscribers: 2508: 8249: S0: 14:19:02> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2508: 8249: S0: 14:19:02> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<FrsHashCalcString: 7284: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1005
<MainWait: 7916: 598: S0: 14:21:23> Wait thread has
started.
<FrsHashCalcString: 7284: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1005
4/13-14:21:23 :T: CoG: 45c90bcc CxtG: b454415e [RemCo ] Name:
136_3693.JPG
4/13-14:21:23 :T: EventTime: Thu Apr 13, 2006 14:21:19 Ver:
0
4/13-14:21:23 :T: FileG: 699e7b2a-1ea4-41bc-956f6431c20bf9b6 FID:
00360000 0000007b
4/13-14:21:23 :T: ParentG: bcae7bcc-3d73-4ff1-9f59b1fcf4514680 Size:
00000000 0000c000
4/13-14:21:23 :T: OrigG: 28400de8-945d-4a0f-b3772d622dfdd28e Attr:
00000020
4/13-14:21:23 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
ReplicaName: AOS|MANUFACTURING (19)
4/13-14:21:23 :T: CoFlags: 0100040c [Content Locn NewFile CmpresStage ]
4/13-14:21:23 :T: UsnReason: 00008003 [DatOvrWrt DatExt Info ]
4/13-14:21:23 :T: CxtionG: b454415e-05a1-4c63-b668367fefd85bf4
4/13-14:21:23 :T: CheckSum: d3c1d9d5 75067e65 96a97ef1 e33dcd4c
4/13-14:21:23 :T: CoArrival: Thu Apr 13, 2006 14:21:23
4/13-14:21:23 :T: FullPathName:
\\?\D:\Manufacturing\DO_NOT_REMOVE_NtFrs_PreInstall_Directory\NTFRS_45c90bcc-ef87-441c-9f71433bfd0abb9f
<FrsDsFindComputer: 2508: 8796: S2: 14:24:02> :DS: Computer
FQDN is cn=amber,ou=domain controllers,dc=aos,dc=local
<FrsDsFindComputer: 2508: 8802: S2: 14:24:02> :DS: Computer's
dns name is amber.AOS.local
<FrsDsFindComputer: 2508: 8816: S2: 14:24:02> :DS: Settings
reference is cn=ntds
settings,cn=amber,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<FrsDsGetSubscribers: 2508: 8249: S0: 14:24:02> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2508: 8249: S0: 14:24:02> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<ThSupWaitThread: 4072: 505: S1: 14:26:23> :S: FetchCs:
Waiting
<ThSupWaitThread: 4072: 533: S1: 14:26:23> :S: FetchCs:
normal wait
<ThSupWaitThread: 4072: 505: S1: 14:26:23> :S: InstallCs:
Waiting
<ThSupWaitThread: 4072: 533: S1: 14:26:23> :S: InstallCs:
normal wait
<ThSupWaitThread: 4072: 505: S1: 14:26:23> :S: SndCs:
Waiting
<ThSupWaitThread: 4072: 533: S1: 14:26:23> :S: SndCs: normal
wait
<ThSupWaitThread: 4072: 505: S1: 14:29:02> :S: ReplicaCs:
Waiting
<ThSupWaitThread: 4072: 533: S1: 14:29:02> :S: ReplicaCs:
normal wait
<ThSupWaitThread: 4072: 505: S1: 14:29:02> :S: ReplicaCs:
Waiting
<ThSupWaitThread: 4072: 533: S1: 14:29:02> :S: ReplicaCs:
normal wait
<ThSupWaitThread: 4072: 505: S1: 14:29:02> :S: ReplicaCs:
Waiting
<ThSupWaitThread: 4072: 533: S1: 14:29:02> :S: ReplicaCs:
normal wait
<FrsDsFindComputer: 2508: 8796: S2: 14:29:02> :DS: Computer
FQDN is cn=amber,ou=domain controllers,dc=aos,dc=local
<FrsDsFindComputer: 2508: 8802: S2: 14:29:02> :DS: Computer's
dns name is amber.AOS.local
<FrsDsFindComputer: 2508: 8816: S2: 14:29:02> :DS: Settings
reference is cn=ntds
settings,cn=amber,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<FrsDsGetSubscribers: 2508: 8249: S0: 14:29:02> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2508: 8249: S0: 14:29:02> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<FrsHashCalcString: 7284: 4842: S0: 14:30:02> Name =
S-1-5-21-3820246116-1162185781-4246705241-1005
<FrsHashCalcString: 7284: 4842: S0: 14:30:02> Name =
S-1-5-21-3820246116-1162185781-4246705241-1005
4/13-14:30:03 :T: CoG: d7f4d1be CxtG: b454415e [RemCo ] Name:
136_3697.JPG
4/13-14:30:03 :T: EventTime: Thu Apr 13, 2006 14:29:59 Ver:
0
4/13-14:30:03 :T: FileG: 7ff26913-b482-422f-873ebf0c7f6ffb77 FID:
00980000 0000136c
4/13-14:30:03 :T: ParentG: bcae7bcc-3d73-4ff1-9f59b1fcf4514680 Size:
00000000 00245000
4/13-14:30:03 :T: OrigG: 28400de8-945d-4a0f-b3772d622dfdd28e Attr:
00000120
4/13-14:30:03 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
ReplicaName: AOS|MANUFACTURING (19)
4/13-14:30:03 :T: CoFlags: 0100040c [Content Locn NewFile CmpresStage ]
4/13-14:30:03 :T: UsnReason: 0000a803 [RenNew DatOvrWrt DatExt Info
Security ]
4/13-14:30:03 :T: CxtionG: b454415e-05a1-4c63-b668367fefd85bf4
4/13-14:30:03 :T: CheckSum: 84893f8c f279b69f 9ec5d039 8a3713e0
4/13-14:30:03 :T: CoArrival: Thu Apr 13, 2006 14:30:02
4/13-14:30:03 :T: FullPathName:
\\?\D:\Manufacturing\DO_NOT_REMOVE_NtFrs_PreInstall_Directory\NTFRS_d7f4d1be-c1d2-48ad-87e151cc4ea9d7f4
<RcsSetCxtionSchedule: 7544: 7365: S0: 14:30:55> :X: 6177bd09,
schedule is on
<RcsSetCxtionSchedule: 7544: 7365: S0: 14:30:55> :X: f938acb4,
schedule is on
<RcsSetCxtionSchedule: 7544: 7365: S0: 14:30:55> :X: b454415e,
schedule is on
<RcsSetCxtionSchedule: 7544: 7365: S0: 14:30:56> :X: 242cdbff,
schedule is on
Post by Ned Pyle (MSFT)
From basic examination, everything looks good - no misconfig, no old FRS,
no filters - all is well. So I dug further into the NTFRS_0005.log from
On server1, 136_3697.txt is renamed to 136_3697.jpg and change order is
sent out (at 4/11-07:33:29).
On server2, 136_3697.jpg is transferred in successfully to pre-install (at
4/11-07:33:29)
At 4/11-07:34:27, it's done again, and works again.
At 4/11-07:44:28 , it looks like maybe the file was overwritten with the
same file? It replicates again without issues.
At 4/11-07:46:40, we get a temporary copy of the file (was this when it
was opened in a hex editor?)
At 4/11-07:46:41 the 136_3697.jpg.Hex Editor 3 temp save file shows up -
that replicates fine too.
So, the logs claim everything is replicating normally. I must admit - I'm
scratching my head here, Minas.
Ned
Minas Hambardzumyan
2006-04-13 21:32:12 UTC
Permalink
My plan was to upload the file to the web site, download and check that it
still does not replicate and then ask you to download it and check on your
side. The first step was to upload the file and I had to use a web interface
on the web server to upload the file. I tried to do this and got an error
message -- the file failed to upload!

One other test -- I zipped the file in file explorer window and saw that zip
file replicates successfully. I then unzipped the file to find out that now
the extracted file does get replicated too!

So the conclusion is that the file *IS* the problem in the whole picture.

Now the question is the following:

Which property of a file has following features:
- It gets cloned and assigned to the new file when a copy of a file is
created (even when copied to a network drive)
- It does not change when the file contents changes (keeping file size the
same)
- It gets reinitialized though when the file size is changed
- It gets reinitialized when a file is zipped and then unzipped
- FRS may fail for some values of this property

I'll spend some time to investigate this. Please tell me if you have any
ideas.

Also, FRS log files have messages like these:
<FrsDsGetSubscribers: 2672: 8249: S0: 14:12:26> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2672: 8249: S0: 14:12:26> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!

Do you know what are these about?

Thanks,
Minas.
Post by Minas Hambardzumyan
Ned,
I started my test after 7:34am (you can see this by looking at the
date/time on directories "." and ".." in my message). So the only log
entry that is very suspicious is the one at 7:44am.
To make sure we are looking at right data at right time, I repeated my
actions -- now recording the time of each command execution. I have the
transcript below. According to it, I ran commands from 14:19 to 14:31. I
ran FRSDIAG on both servers after finishing my commands and have frs logs
between those time points also inserted here. The first log reference to
file name 136_3697.JPG is at 14:30:02 on Server#1 and 13:30:03 on
Server#2. This is right after I added a single byte in the hex editor (my
dir command after it was executed at 14:30:09). Also, there is no
reference to the 136_3697.TXT in the log files.
Looks like the file actually does not get replicated. To finish once and
forever I decided to send my failing file to you -- to see if it will get
replicated on your side. This is where interesting things started to
happen. I will write about those in my next message -- not to mix with the
mess I have here.
Minas.
Server#1: The current time is: 14:19:48.25 (Empty Directory)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 116,651,122,688 bytes free
Server#2: The current time is: 14:19:52.63
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,077,216,768 bytes free
Server#1: The current time is: 14:21:31.80 (copy 136_3693.JPG which
replicates)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 116,651,040,768 bytes free
Server#2: The current time is: 14:21:33.85
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,134,848 bytes free
Server#1: The current time is: 14:22:40.27 (copy 136_3697.JPG which does
not replicate)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free
server#2: The current time is: 14:22:41.59
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:25:30.76 (fill 136_3697.JPG with ASCII 0
character, still no replication)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free
Server#2: The current time is: 14:25:31.57
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:28:01.16 (copy 136_3697.JPG
136_3697.txt, no replication for both)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:27 PM <DIR> .
04/13/2006 02:27 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 116,646,313,984 bytes free
Server#2: The current time is: 14:28:02.18
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:30:09.99 (after adding 1 byte to the end
of 136_3697.JPG, now replication worked for 136_3697.JPG)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:29 PM <DIR> .
04/13/2006 02:29 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/13/2006 02:29 PM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 116,646,305,792 bytes free
Server#2: The current time is: 14:30:11.14
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:30 PM <DIR> .
04/13/2006 02:30 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/13/2006 02:29 PM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,074,779,648 bytes free
<FrsStageCsSubmitTransfer: 5988: 1828: S1: 14:21:22> Stage: submit
transfer 0xf6faa8
<ProcessOpenByIdStatus: 4452: 3025: S1: 14:21:22> ++
STATUS_OPLOCK_NOT_GRANTED
<FrsOpenSourceFileById: 4452: 3372: S0: 14:21:22> ++ ERROR -
NtCreateFile failed : NTStatus: STATUS_OPLOCK_NOT_GRANTED
4/13-14:21:23 :T: CoG: 45c90bcc CxtG: 92dea886 [LclCo ]
Name: 136_3693.JPG
0
00020000 00000b8e
4/13-14:21:23 :T: ParentG: 9dae1abb-37fd-4376-ac879c64a5cd61a2
Size: 00000000 0000c000
4/13-14:21:23 :T: OrigG: 28400de8-945d-4a0f-b3772d622dfdd28e
Attr: 00000020
4/13-14:21:23 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
ReplicaName: AOS|MANUFACTURING (4)
4/13-14:21:23 :T: CoFlags: 0100042c [Content Locn LclCo NewFile
CmpresStage ]
4/13-14:21:23 :T: UsnReason: 00008003 [DatOvrWrt DatExt Info ]
4/13-14:21:23 :T: CxtionG: 92dea886-2851-4337-92e0ac801fcec1b8
4/13-14:21:23 :T: CheckSum: d3c1d9d5 75067e65 96a97ef1 e33dcd4c
4/13-14:21:23 :T: CoArrival: <null>
4/13-14:21:23 :T: FullPathName: \\.\D:\Manufacturing\136_3693.JPG
<FrsHashCalcString: 2660: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<FrsHashCalcString: 2660: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<FrsDsFindComputer: 2672: 8796: S2: 14:22:26> :DS: Computer
FQDN is cn=ofna,ou=domain controllers,dc=aos,dc=local
<FrsDsFindComputer: 2672: 8802: S2: 14:22:26> :DS: Computer's
dns name is ofna.AOS.local
<FrsDsFindComputer: 2672: 8816: S2: 14:22:26> :DS: Settings
reference is cn=ntds
settings,cn=ofna,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<FrsDsGetSubscribers: 2672: 8249: S0: 14:22:26> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2672: 8249: S0: 14:22:26> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
Waiting
normal wait
Waiting
normal wait
Waiting
normal wait
Waiting
normal wait
<FrsDsFindComputer: 2672: 8796: S2: 14:27:26> :DS: Computer
FQDN is cn=ofna,ou=domain controllers,dc=aos,dc=local
<FrsDsFindComputer: 2672: 8802: S2: 14:27:26> :DS: Computer's
dns name is ofna.AOS.local
<FrsDsFindComputer: 2672: 8816: S2: 14:27:26> :DS: Settings
reference is cn=ntds
settings,cn=ofna,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<DbgPrintThreadIds: 2672: 1021: S2: 14:27:26> :H: Known
thread IDs -
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: First : 440
2616
2672
5472
2776
2780
4440
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: JRNL : 2940
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: DBCs : 2944
3664
3684
ChgOrdRetryCS : 1376
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: Wait : 880
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: ThCs : 3120
3196
5964
4452
2396
<FrsPrintAllocStats: 2672: 234: S2: 14:27:26>
<FrsPrintAllocStats: 2672: 235: S2: 14:27:26> NTFRS MEMORY
<FrsPrintAllocStats: 2672: 238: S2: 14:27:26> ENABLE STATS
: FALSE
694537 KB (3350000 calls)
0 KB (0 calls)
0 KB
0 KB
36522 KB
0
3346884
3116
0x00255810
0x02600060
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
THREAD_CONTEXT_TYPE : 14 Calls, 5 Max, 3 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26> REPLICA_TYPE
: 13608 Calls, 5 Max, 4 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
REPLICA_THREAD_TYPE : 13676 Calls, 11 Max, 2 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
CONFIG_NODE_TYPE : 144189 Calls, 21 Max, 1 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
CXTION_TYPE : 27219 Calls, 11 Max, 9 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26> GUID/RPC
HANDLE : 2 Calls, 2 Max, 2 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
THREAD_TYPE : 13270 Calls, 19 Max, 10 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26> GEN_TABLE_TYPE
: 135877 Calls, 47 Max, 39 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26> JBUFFER_TYPE
: 3 Calls, 3 Max, 3 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
VOLUME_MONITOR_ENTRY_TYPE : 2 Calls, 2 Max, 1 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
COMMAND_PACKET_TYPE : 178685 Calls, 24 Max, 13 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
GENERIC_HASH_TABLE_TYPE : 3 Calls, 3 Max, 3 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
CHANGE_ORDER_ENTRY_TYPE : 67 Calls, 11 Max, 0 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
FILTER_TABLE_ENTRY_TYPE : 26 Calls, 26 Max, 26 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
QHASH_TABLE_TYPE : 30 Calls, 25 Max, 23 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
OUT_LOG_PARTNER_TYPE : 4 Calls, 3 Max, 3 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
WILDCARD_FILTER_ENTRY_TYPE: 15 Calls, 15 Max, 15 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
REPARSE_TAG_TABLE_TYPE : 24360 Calls, 3 Max, 3 busy
<FrsPrintAllocStats: 2672: 270: S2: 14:27:26>
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 0 to
15 : 506712 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 16 to
31 : 602127 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 32 to
47 : 405311 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 48 to
63 : 46755 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 64 to
79 : 382512 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 80 to
95 : 227138 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 96 to
111 : 16375 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 112 to
127 : 41941 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 128 to
143 : 46735 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 144 to
159 : 168993 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 160 to
175 : 11013 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 176 to
191 : 106007 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 192 to
207 : 62546 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 208 to
223 : 64959 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 224 to
239 : 165087 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 240 to
255 : 48934 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 256 to
271 : 29230 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 272 to
287 : 52086 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 288 to
303 : 16243 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 304 to
319 : 21725 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 320 to
335 : 3 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 352 to
367 : 10974 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 368 to
383 : 10972 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 384 to
399 : 836 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 416 to
431 : 13609 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 512 to
527 : 8748 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 560 to
575 : 27218 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 608 to
623 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 640 to
655 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 784 to
799 : 41679 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 800 to
815 : 40614 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 848 to
863 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 864 to
879 : 13779 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 880 to
895 : 13667 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 944 to
959 : 27502 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 976 to
991 : 67 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1008 to
1023 : 13667 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1024 to
1039 : 6112 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1088 to
1103 : 13779 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1104 to
1119 : 13779 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1184 to
1199 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1200 to
1215 : 4 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1216 to
1231 : 27502 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1408 to
1423 : 55 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1616 to
1631 : 3 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1792 to
1807 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2048 to
2063 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2128 to
2143 : 13610 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2160 to
2175 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2480 to
2495 : 10 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2544 to
2559 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2736 to
2751 : 13610 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 3152 to
3167 : 11 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 3264 to
3279 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 4000 to
4015 : 13611 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 4096 to
4111 : 4 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 4976 to
4991 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 4992 to
5007 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 5504 to
5519 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 5632 to
5647 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 7856 to
7871 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 8192 to
8207 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 8448 to
8463 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 9744 to
9759 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 10368 to
10383 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 12080 to
12095 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 13120 to
13135 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 13696 to
13711 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 16368 to
16383 : 2119 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 280: S2: 14:27:26>
<FrsDsGetSubscribers: 2672: 8249: S0: 14:27:26> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
Waiting
normal wait
Waiting
normal wait
<FrsDsGetSubscribers: 2672: 8249: S0: 14:27:26> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<FrsStageCsSubmitTransfer: 6104: 1828: S1: 14:30:02> Stage: submit
transfer 0xf6f980
<ProcessOpenByIdStatus: 4548: 3025: S1: 14:30:02> ++
STATUS_OPLOCK_NOT_GRANTED
<FrsOpenSourceFileById: 4548: 3372: S0: 14:30:02> ++ ERROR -
NtCreateFile failed : NTStatus: STATUS_OPLOCK_NOT_GRANTED
4/13-14:30:02 :T: CoG: d7f4d1be CxtG: 92dea886 [LclCo ]
Name: 136_3697.JPG
0
00020000 00000b94
4/13-14:30:02 :T: ParentG: 9dae1abb-37fd-4376-ac879c64a5cd61a2
Size: 00000000 00245000
4/13-14:30:02 :T: OrigG: 28400de8-945d-4a0f-b3772d622dfdd28e
Attr: 00000120
4/13-14:30:02 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
ReplicaName: AOS|MANUFACTURING (4)
4/13-14:30:02 :T: CoFlags: 0100042c [Content Locn LclCo NewFile
CmpresStage ]
4/13-14:30:02 :T: UsnReason: 0000a803 [RenNew DatOvrWrt DatExt Info
Security ]
4/13-14:30:02 :T: CxtionG: 92dea886-2851-4337-92e0ac801fcec1b8
4/13-14:30:02 :T: CheckSum: 84893f8c f279b69f 9ec5d039 8a3713e0
4/13-14:30:02 :T: CoArrival: <null>
4/13-14:30:02 :T: FullPathName: \\.\D:\Manufacturing\136_3697.JPG
<FrsHashCalcString: 2660: 4842: S0: 14:30:02> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<FrsHashCalcString: 2660: 4842: S0: 14:30:03> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<RcsSetCxtionSchedule: 4312: 7365: S0: 14:30:32> :X: b454415e,
schedule is on
<RcsSetCxtionSchedule: 4312: 7365: S0: 14:30:32> :X: 242cdbff,
schedule is on
<RcsSetCxtionSchedule: 4312: 7365: S0: 14:30:32> :X: 6177bd09,
schedule is on
<RcsSetCxtionSchedule: 4312: 7365: S0: 14:30:32> :X: f938acb4,
schedule is on
<FrsDsFindComputer: 2508: 8796: S2: 14:19:02> :DS: Computer
FQDN is cn=amber,ou=domain controllers,dc=aos,dc=local
<FrsDsFindComputer: 2508: 8802: S2: 14:19:02> :DS: Computer's
dns name is amber.AOS.local
<FrsDsFindComputer: 2508: 8816: S2: 14:19:02> :DS: Settings
reference is cn=ntds
settings,cn=amber,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<FrsDsGetSubscribers: 2508: 8249: S0: 14:19:02> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2508: 8249: S0: 14:19:02> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<FrsHashCalcString: 7284: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1005
<MainWait: 7916: 598: S0: 14:21:23> Wait thread has
started.
<FrsHashCalcString: 7284: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1005
4/13-14:21:23 :T: CoG: 45c90bcc CxtG: b454415e [RemCo ]
Name: 136_3693.JPG
0
00360000 0000007b
4/13-14:21:23 :T: ParentG: bcae7bcc-3d73-4ff1-9f59b1fcf4514680
Size: 00000000 0000c000
4/13-14:21:23 :T: OrigG: 28400de8-945d-4a0f-b3772d622dfdd28e
Attr: 00000020
4/13-14:21:23 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
ReplicaName: AOS|MANUFACTURING (19)
4/13-14:21:23 :T: CoFlags: 0100040c [Content Locn NewFile
CmpresStage ]
4/13-14:21:23 :T: UsnReason: 00008003 [DatOvrWrt DatExt Info ]
4/13-14:21:23 :T: CxtionG: b454415e-05a1-4c63-b668367fefd85bf4
4/13-14:21:23 :T: CheckSum: d3c1d9d5 75067e65 96a97ef1 e33dcd4c
4/13-14:21:23 :T: CoArrival: Thu Apr 13, 2006 14:21:23
\\?\D:\Manufacturing\DO_NOT_REMOVE_NtFrs_PreInstall_Directory\NTFRS_45c90bcc-ef87-441c-9f71433bfd0abb9f
<FrsDsFindComputer: 2508: 8796: S2: 14:24:02> :DS: Computer
FQDN is cn=amber,ou=domain controllers,dc=aos,dc=local
<FrsDsFindComputer: 2508: 8802: S2: 14:24:02> :DS: Computer's
dns name is amber.AOS.local
<FrsDsFindComputer: 2508: 8816: S2: 14:24:02> :DS: Settings
reference is cn=ntds
settings,cn=amber,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<FrsDsGetSubscribers: 2508: 8249: S0: 14:24:02> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2508: 8249: S0: 14:24:02> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
Waiting
normal wait
Waiting
normal wait
Waiting
normal wait
Waiting
normal wait
Waiting
normal wait
Waiting
normal wait
<FrsDsFindComputer: 2508: 8796: S2: 14:29:02> :DS: Computer
FQDN is cn=amber,ou=domain controllers,dc=aos,dc=local
<FrsDsFindComputer: 2508: 8802: S2: 14:29:02> :DS: Computer's
dns name is amber.AOS.local
<FrsDsFindComputer: 2508: 8816: S2: 14:29:02> :DS: Settings
reference is cn=ntds
settings,cn=amber,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<FrsDsGetSubscribers: 2508: 8249: S0: 14:29:02> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2508: 8249: S0: 14:29:02> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<FrsHashCalcString: 7284: 4842: S0: 14:30:02> Name =
S-1-5-21-3820246116-1162185781-4246705241-1005
<FrsHashCalcString: 7284: 4842: S0: 14:30:02> Name =
S-1-5-21-3820246116-1162185781-4246705241-1005
4/13-14:30:03 :T: CoG: d7f4d1be CxtG: b454415e [RemCo ]
Name: 136_3697.JPG
0
00980000 0000136c
4/13-14:30:03 :T: ParentG: bcae7bcc-3d73-4ff1-9f59b1fcf4514680
Size: 00000000 00245000
4/13-14:30:03 :T: OrigG: 28400de8-945d-4a0f-b3772d622dfdd28e
Attr: 00000120
4/13-14:30:03 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
ReplicaName: AOS|MANUFACTURING (19)
4/13-14:30:03 :T: CoFlags: 0100040c [Content Locn NewFile
CmpresStage ]
4/13-14:30:03 :T: UsnReason: 0000a803 [RenNew DatOvrWrt DatExt Info
Security ]
4/13-14:30:03 :T: CxtionG: b454415e-05a1-4c63-b668367fefd85bf4
4/13-14:30:03 :T: CheckSum: 84893f8c f279b69f 9ec5d039 8a3713e0
4/13-14:30:03 :T: CoArrival: Thu Apr 13, 2006 14:30:02
\\?\D:\Manufacturing\DO_NOT_REMOVE_NtFrs_PreInstall_Directory\NTFRS_d7f4d1be-c1d2-48ad-87e151cc4ea9d7f4
<RcsSetCxtionSchedule: 7544: 7365: S0: 14:30:55> :X: 6177bd09,
schedule is on
<RcsSetCxtionSchedule: 7544: 7365: S0: 14:30:55> :X: f938acb4,
schedule is on
<RcsSetCxtionSchedule: 7544: 7365: S0: 14:30:55> :X: b454415e,
schedule is on
<RcsSetCxtionSchedule: 7544: 7365: S0: 14:30:56> :X: 242cdbff,
schedule is on
Post by Ned Pyle (MSFT)
From basic examination, everything looks good - no misconfig, no old FRS,
no filters - all is well. So I dug further into the NTFRS_0005.log from
On server1, 136_3697.txt is renamed to 136_3697.jpg and change order is
sent out (at 4/11-07:33:29).
On server2, 136_3697.jpg is transferred in successfully to pre-install
(at 4/11-07:33:29)
At 4/11-07:34:27, it's done again, and works again.
At 4/11-07:44:28 , it looks like maybe the file was overwritten with the
same file? It replicates again without issues.
At 4/11-07:46:40, we get a temporary copy of the file (was this when it
was opened in a hex editor?)
At 4/11-07:46:41 the 136_3697.jpg.Hex Editor 3 temp save file shows up -
that replicates fine too.
So, the logs claim everything is replicating normally. I must admit - I'm
scratching my head here, Minas.
Ned
John Brineman
2006-04-20 20:34:01 UTC
Permalink
I just installed Version R2 and set up DFS replication and had the identical
problem. It was laso with a .jpg file. There were 8 files in the folder an
3 of them replicated. The others did not. I will try some of your tweaks to
verify.
Thanks,
John Brineman
Post by Minas Hambardzumyan
My plan was to upload the file to the web site, download and check that it
still does not replicate and then ask you to download it and check on your
side. The first step was to upload the file and I had to use a web interface
on the web server to upload the file. I tried to do this and got an error
message -- the file failed to upload!
One other test -- I zipped the file in file explorer window and saw that zip
file replicates successfully. I then unzipped the file to find out that now
the extracted file does get replicated too!
So the conclusion is that the file *IS* the problem in the whole picture.
- It gets cloned and assigned to the new file when a copy of a file is
created (even when copied to a network drive)
- It does not change when the file contents changes (keeping file size the
same)
- It gets reinitialized though when the file size is changed
- It gets reinitialized when a file is zipped and then unzipped
- FRS may fail for some values of this property
I'll spend some time to investigate this. Please tell me if you have any
ideas.
<FrsDsGetSubscribers: 2672: 8249: S0: 14:12:26> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2672: 8249: S0: 14:12:26> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
Do you know what are these about?
Thanks,
Minas.
Post by Minas Hambardzumyan
Ned,
I started my test after 7:34am (you can see this by looking at the
date/time on directories "." and ".." in my message). So the only log
entry that is very suspicious is the one at 7:44am.
To make sure we are looking at right data at right time, I repeated my
actions -- now recording the time of each command execution. I have the
transcript below. According to it, I ran commands from 14:19 to 14:31. I
ran FRSDIAG on both servers after finishing my commands and have frs logs
between those time points also inserted here. The first log reference to
file name 136_3697.JPG is at 14:30:02 on Server#1 and 13:30:03 on
Server#2. This is right after I added a single byte in the hex editor (my
dir command after it was executed at 14:30:09). Also, there is no
reference to the 136_3697.TXT in the log files.
Looks like the file actually does not get replicated. To finish once and
forever I decided to send my failing file to you -- to see if it will get
replicated on your side. This is where interesting things started to
happen. I will write about those in my next message -- not to mix with the
mess I have here.
Minas.
Server#1: The current time is: 14:19:48.25 (Empty Directory)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 116,651,122,688 bytes free
Server#2: The current time is: 14:19:52.63
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,077,216,768 bytes free
Server#1: The current time is: 14:21:31.80 (copy 136_3693.JPG which
replicates)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 116,651,040,768 bytes free
Server#2: The current time is: 14:21:33.85
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,134,848 bytes free
Server#1: The current time is: 14:22:40.27 (copy 136_3697.JPG which does
not replicate)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free
server#2: The current time is: 14:22:41.59
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:25:30.76 (fill 136_3697.JPG with ASCII 0
character, still no replication)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free
Server#2: The current time is: 14:25:31.57
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:28:01.16 (copy 136_3697.JPG
136_3697.txt, no replication for both)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:27 PM <DIR> .
04/13/2006 02:27 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 116,646,313,984 bytes free
Server#2: The current time is: 14:28:02.18
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:30:09.99 (after adding 1 byte to the end
of 136_3697.JPG, now replication worked for 136_3697.JPG)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:29 PM <DIR> .
04/13/2006 02:29 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/13/2006 02:29 PM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 116,646,305,792 bytes free
Server#2: The current time is: 14:30:11.14
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:30 PM <DIR> .
04/13/2006 02:30 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/13/2006 02:29 PM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,074,779,648 bytes free
<FrsStageCsSubmitTransfer: 5988: 1828: S1: 14:21:22> Stage: submit
transfer 0xf6faa8
<ProcessOpenByIdStatus: 4452: 3025: S1: 14:21:22> ++
STATUS_OPLOCK_NOT_GRANTED
<FrsOpenSourceFileById: 4452: 3372: S0: 14:21:22> ++ ERROR -
NtCreateFile failed : NTStatus: STATUS_OPLOCK_NOT_GRANTED
4/13-14:21:23 :T: CoG: 45c90bcc CxtG: 92dea886 [LclCo ]
Name: 136_3693.JPG
0
00020000 00000b8e
4/13-14:21:23 :T: ParentG: 9dae1abb-37fd-4376-ac879c64a5cd61a2
Size: 00000000 0000c000
4/13-14:21:23 :T: OrigG: 28400de8-945d-4a0f-b3772d622dfdd28e
Attr: 00000020
4/13-14:21:23 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
ReplicaName: AOS|MANUFACTURING (4)
4/13-14:21:23 :T: CoFlags: 0100042c [Content Locn LclCo NewFile
CmpresStage ]
4/13-14:21:23 :T: UsnReason: 00008003 [DatOvrWrt DatExt Info ]
4/13-14:21:23 :T: CxtionG: 92dea886-2851-4337-92e0ac801fcec1b8
4/13-14:21:23 :T: CheckSum: d3c1d9d5 75067e65 96a97ef1 e33dcd4c
4/13-14:21:23 :T: CoArrival: <null>
4/13-14:21:23 :T: FullPathName: \\.\D:\Manufacturing\136_3693.JPG
<FrsHashCalcString: 2660: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<FrsHashCalcString: 2660: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<FrsDsFindComputer: 2672: 8796: S2: 14:22:26> :DS: Computer
FQDN is cn=ofna,ou=domain controllers,dc=aos,dc=local
<FrsDsFindComputer: 2672: 8802: S2: 14:22:26> :DS: Computer's
dns name is ofna.AOS.local
<FrsDsFindComputer: 2672: 8816: S2: 14:22:26> :DS: Settings
reference is cn=ntds
settings,cn=ofna,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<FrsDsGetSubscribers: 2672: 8249: S0: 14:22:26> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2672: 8249: S0: 14:22:26> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
Waiting
normal wait
Waiting
normal wait
Waiting
normal wait
Waiting
Ned Pyle (MSFT)
2006-04-20 21:24:11 UTC
Permalink
Hi John,

Keep in mind that all the previous thread was with FRS (Version 1, NTFRS).
If you are using DFSR it's going to be totally different. For that you'd
want to look at the DFSR debug logs and the DFSR health report, to start.

Ned
Post by John Brineman
I just installed Version R2 and set up DFS replication and had the identical
problem. It was laso with a .jpg file. There were 8 files in the folder an
3 of them replicated. The others did not. I will try some of your tweaks to
verify.
Thanks,
John Brineman
Post by Minas Hambardzumyan
My plan was to upload the file to the web site, download and check that it
still does not replicate and then ask you to download it and check on your
side. The first step was to upload the file and I had to use a web interface
on the web server to upload the file. I tried to do this and got an error
message -- the file failed to upload!
One other test -- I zipped the file in file explorer window and saw that zip
file replicates successfully. I then unzipped the file to find out that now
the extracted file does get replicated too!
So the conclusion is that the file *IS* the problem in the whole picture.
- It gets cloned and assigned to the new file when a copy of a file is
created (even when copied to a network drive)
- It does not change when the file contents changes (keeping file size the
same)
- It gets reinitialized though when the file size is changed
- It gets reinitialized when a file is zipped and then unzipped
- FRS may fail for some values of this property
I'll spend some time to investigate this. Please tell me if you have any
ideas.
<FrsDsGetSubscribers: 2672: 8249: S0: 14:12:26> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2672: 8249: S0: 14:12:26> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
Do you know what are these about?
Thanks,
Minas.
Post by Minas Hambardzumyan
Ned,
I started my test after 7:34am (you can see this by looking at the
date/time on directories "." and ".." in my message). So the only log
entry that is very suspicious is the one at 7:44am.
To make sure we are looking at right data at right time, I repeated my
actions -- now recording the time of each command execution. I have the
transcript below. According to it, I ran commands from 14:19 to 14:31. I
ran FRSDIAG on both servers after finishing my commands and have frs logs
between those time points also inserted here. The first log reference to
file name 136_3697.JPG is at 14:30:02 on Server#1 and 13:30:03 on
Server#2. This is right after I added a single byte in the hex editor (my
dir command after it was executed at 14:30:09). Also, there is no
reference to the 136_3697.TXT in the log files.
Looks like the file actually does not get replicated. To finish once and
forever I decided to send my failing file to you -- to see if it will get
replicated on your side. This is where interesting things started to
happen. I will write about those in my next message -- not to mix with the
mess I have here.
Minas.
Server#1: The current time is: 14:19:48.25 (Empty Directory)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 116,651,122,688 bytes free
Server#2: The current time is: 14:19:52.63
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,077,216,768 bytes free
Server#1: The current time is: 14:21:31.80 (copy 136_3693.JPG which
replicates)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 116,651,040,768 bytes free
Server#2: The current time is: 14:21:33.85
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,134,848 bytes free
Server#1: The current time is: 14:22:40.27 (copy 136_3697.JPG which does
not replicate)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free
server#2: The current time is: 14:22:41.59
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:25:30.76 (fill 136_3697.JPG with ASCII 0
character, still no replication)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free
Server#2: The current time is: 14:25:31.57
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:28:01.16 (copy 136_3697.JPG
136_3697.txt, no replication for both)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:27 PM <DIR> .
04/13/2006 02:27 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 116,646,313,984 bytes free
Server#2: The current time is: 14:28:02.18
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:30:09.99 (after adding 1 byte to the end
of 136_3697.JPG, now replication worked for 136_3697.JPG)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:29 PM <DIR> .
04/13/2006 02:29 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/13/2006 02:29 PM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 116,646,305,792 bytes free
Server#2: The current time is: 14:30:11.14
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:30 PM <DIR> .
04/13/2006 02:30 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/13/2006 02:29 PM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,074,779,648 bytes free
<FrsStageCsSubmitTransfer: 5988: 1828: S1: 14:21:22> Stage: submit
transfer 0xf6faa8
<ProcessOpenByIdStatus: 4452: 3025: S1: 14:21:22> ++
STATUS_OPLOCK_NOT_GRANTED
<FrsOpenSourceFileById: 4452: 3372: S0: 14:21:22> ++ ERROR -
NtCreateFile failed : NTStatus: STATUS_OPLOCK_NOT_GRANTED
4/13-14:21:23 :T: CoG: 45c90bcc CxtG: 92dea886 [LclCo ]
Name: 136_3693.JPG
4/13-14:21:23 :T: EventTime: Thu Apr 13, 2006 14:21:19
0
4/13-14:21:23 :T: FileG: 699e7b2a-1ea4-41bc-956f6431c20bf9b6
00020000 00000b8e
4/13-14:21:23 :T: ParentG: 9dae1abb-37fd-4376-ac879c64a5cd61a2
Size: 00000000 0000c000
4/13-14:21:23 :T: OrigG: 28400de8-945d-4a0f-b3772d622dfdd28e
Attr: 00000020
4/13-14:21:23 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
ReplicaName: AOS|MANUFACTURING (4)
4/13-14:21:23 :T: CoFlags: 0100042c [Content Locn LclCo NewFile
CmpresStage ]
4/13-14:21:23 :T: UsnReason: 00008003 [DatOvrWrt DatExt Info ]
4/13-14:21:23 :T: CxtionG: 92dea886-2851-4337-92e0ac801fcec1b8
4/13-14:21:23 :T: CheckSum: d3c1d9d5 75067e65 96a97ef1 e33dcd4c
4/13-14:21:23 :T: CoArrival: <null>
4/13-14:21:23 :T: FullPathName: \\.\D:\Manufacturing\136_3693.JPG
<FrsHashCalcString: 2660: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<FrsHashCalcString: 2660: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<FrsDsFindComputer: 2672: 8796: S2: 14:22:26> :DS: Computer
FQDN is cn=ofna,ou=domain controllers,dc=aos,dc=local
<FrsDsFindComputer: 2672: 8802: S2: 14:22:26> :DS: Computer's
dns name is ofna.AOS.local
<FrsDsFindComputer: 2672: 8816: S2: 14:22:26> :DS: Settings
reference is cn=ntds
settings,cn=ofna,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<FrsDsGetSubscribers: 2672: 8249: S0: 14:22:26> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2672: 8249: S0: 14:22:26> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
Waiting
normal wait
Waiting
normal wait
Waiting
normal wait
Waiting
John Brineman
2006-04-21 13:08:02 UTC
Permalink
I understand that. I reviewed the health report not the debug logs. Zipping
and unzipping the file had the same affect as Minas got. The file started
replicating. This is a jpg file that has been downloaded (and jpeg
compressed) from a camera. I would assume from the file name that Minas has
that he has the same source for the file.
Thanks
John Brineman
Post by Ned Pyle (MSFT)
Hi John,
Keep in mind that all the previous thread was with FRS (Version 1, NTFRS).
If you are using DFSR it's going to be totally different. For that you'd
want to look at the DFSR debug logs and the DFSR health report, to start.
Ned
Post by John Brineman
I just installed Version R2 and set up DFS replication and had the identical
problem. It was laso with a .jpg file. There were 8 files in the folder an
3 of them replicated. The others did not. I will try some of your tweaks to
verify.
Thanks,
John Brineman
Post by Minas Hambardzumyan
My plan was to upload the file to the web site, download and check that it
still does not replicate and then ask you to download it and check on your
side. The first step was to upload the file and I had to use a web interface
on the web server to upload the file. I tried to do this and got an error
message -- the file failed to upload!
One other test -- I zipped the file in file explorer window and saw that zip
file replicates successfully. I then unzipped the file to find out that now
the extracted file does get replicated too!
So the conclusion is that the file *IS* the problem in the whole picture.
- It gets cloned and assigned to the new file when a copy of a file is
created (even when copied to a network drive)
- It does not change when the file contents changes (keeping file size the
same)
- It gets reinitialized though when the file size is changed
- It gets reinitialized when a file is zipped and then unzipped
- FRS may fail for some values of this property
I'll spend some time to investigate this. Please tell me if you have any
ideas.
<FrsDsGetSubscribers: 2672: 8249: S0: 14:12:26> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2672: 8249: S0: 14:12:26> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
Do you know what are these about?
Thanks,
Minas.
Post by Minas Hambardzumyan
Ned,
I started my test after 7:34am (you can see this by looking at the
date/time on directories "." and ".." in my message). So the only log
entry that is very suspicious is the one at 7:44am.
To make sure we are looking at right data at right time, I repeated my
actions -- now recording the time of each command execution. I have the
transcript below. According to it, I ran commands from 14:19 to 14:31. I
ran FRSDIAG on both servers after finishing my commands and have frs logs
between those time points also inserted here. The first log reference to
file name 136_3697.JPG is at 14:30:02 on Server#1 and 13:30:03 on
Server#2. This is right after I added a single byte in the hex editor (my
dir command after it was executed at 14:30:09). Also, there is no
reference to the 136_3697.TXT in the log files.
Looks like the file actually does not get replicated. To finish once and
forever I decided to send my failing file to you -- to see if it will get
replicated on your side. This is where interesting things started to
happen. I will write about those in my next message -- not to mix with the
mess I have here.
Minas.
Server#1: The current time is: 14:19:48.25 (Empty Directory)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 116,651,122,688 bytes free
Server#2: The current time is: 14:19:52.63
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,077,216,768 bytes free
Server#1: The current time is: 14:21:31.80 (copy 136_3693.JPG which
replicates)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 116,651,040,768 bytes free
Server#2: The current time is: 14:21:33.85
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,134,848 bytes free
Server#1: The current time is: 14:22:40.27 (copy 136_3697.JPG which does
not replicate)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free
server#2: The current time is: 14:22:41.59
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:25:30.76 (fill 136_3697.JPG with ASCII 0
character, still no replication)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free
Server#2: The current time is: 14:25:31.57
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:28:01.16 (copy 136_3697.JPG
136_3697.txt, no replication for both)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:27 PM <DIR> .
04/13/2006 02:27 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 116,646,313,984 bytes free
Server#2: The current time is: 14:28:02.18
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:30:09.99 (after adding 1 byte to the end
of 136_3697.JPG, now replication worked for 136_3697.JPG)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:29 PM <DIR> .
04/13/2006 02:29 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/13/2006 02:29 PM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 116,646,305,792 bytes free
Server#2: The current time is: 14:30:11.14
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:30 PM <DIR> .
04/13/2006 02:30 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/13/2006 02:29 PM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,074,779,648 bytes free
<FrsStageCsSubmitTransfer: 5988: 1828: S1: 14:21:22> Stage: submit
transfer 0xf6faa8
<ProcessOpenByIdStatus: 4452: 3025: S1: 14:21:22> ++
STATUS_OPLOCK_NOT_GRANTED
<FrsOpenSourceFileById: 4452: 3372: S0: 14:21:22> ++ ERROR -
NtCreateFile failed : NTStatus: STATUS_OPLOCK_NOT_GRANTED
4/13-14:21:23 :T: CoG: 45c90bcc CxtG: 92dea886 [LclCo ]
Name: 136_3693.JPG
4/13-14:21:23 :T: EventTime: Thu Apr 13, 2006 14:21:19
0
4/13-14:21:23 :T: FileG: 699e7b2a-1ea4-41bc-956f6431c20bf9b6
00020000 00000b8e
4/13-14:21:23 :T: ParentG: 9dae1abb-37fd-4376-ac879c64a5cd61a2
Size: 00000000 0000c000
4/13-14:21:23 :T: OrigG: 28400de8-945d-4a0f-b3772d622dfdd28e
Attr: 00000020
4/13-14:21:23 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
Ned Pyle (MSFT)
2006-04-22 02:11:29 UTC
Permalink
Very interesting. Have either of you opened a case with PSS?
Post by John Brineman
I understand that. I reviewed the health report not the debug logs.
Zipping
and unzipping the file had the same affect as Minas got. The file started
replicating. This is a jpg file that has been downloaded (and jpeg
compressed) from a camera. I would assume from the file name that Minas has
that he has the same source for the file.
Thanks
John Brineman
Post by Ned Pyle (MSFT)
Hi John,
Keep in mind that all the previous thread was with FRS (Version 1, NTFRS).
If you are using DFSR it's going to be totally different. For that you'd
want to look at the DFSR debug logs and the DFSR health report, to start.
Ned
Post by John Brineman
I just installed Version R2 and set up DFS replication and had the identical
problem. It was laso with a .jpg file. There were 8 files in the
folder
an
3 of them replicated. The others did not. I will try some of your
tweaks
to
verify.
Thanks,
John Brineman
Post by Minas Hambardzumyan
My plan was to upload the file to the web site, download and check
that
it
still does not replicate and then ask you to download it and check on your
side. The first step was to upload the file and I had to use a web interface
on the web server to upload the file. I tried to do this and got an error
message -- the file failed to upload!
One other test -- I zipped the file in file explorer window and saw
that
zip
file replicates successfully. I then unzipped the file to find out
that
now
the extracted file does get replicated too!
So the conclusion is that the file *IS* the problem in the whole picture.
- It gets cloned and assigned to the new file when a copy of a file is
created (even when copied to a network drive)
- It does not change when the file contents changes (keeping file size the
same)
- It gets reinitialized though when the file size is changed
- It gets reinitialized when a file is zipped and then unzipped
- FRS may fail for some values of this property
I'll spend some time to investigate this. Please tell me if you have any
ideas.
<FrsDsGetSubscribers: 2672: 8249: S0: 14:12:26> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2672: 8249: S0: 14:12:26> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
Do you know what are these about?
Thanks,
Minas.
Post by Minas Hambardzumyan
Ned,
I started my test after 7:34am (you can see this by looking at the
date/time on directories "." and ".." in my message). So the only log
entry that is very suspicious is the one at 7:44am.
To make sure we are looking at right data at right time, I repeated my
actions -- now recording the time of each command execution. I have the
transcript below. According to it, I ran commands from 14:19 to
14:31.
I
ran FRSDIAG on both servers after finishing my commands and have frs logs
between those time points also inserted here. The first log
reference
to
file name 136_3697.JPG is at 14:30:02 on Server#1 and 13:30:03 on
Server#2. This is right after I added a single byte in the hex
editor
(my
dir command after it was executed at 14:30:09). Also, there is no
reference to the 136_3697.TXT in the log files.
Looks like the file actually does not get replicated. To finish once and
forever I decided to send my failing file to you -- to see if it
will
get
replicated on your side. This is where interesting things started to
happen. I will write about those in my next message -- not to mix
with
the
mess I have here.
Minas.
Server#1: The current time is: 14:19:48.25 (Empty Directory)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 116,651,122,688 bytes free
Server#2: The current time is: 14:19:52.63
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,077,216,768 bytes free
Server#1: The current time is: 14:21:31.80 (copy 136_3693.JPG which
replicates)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 116,651,040,768 bytes free
Server#2: The current time is: 14:21:33.85
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,134,848 bytes free
Server#1: The current time is: 14:22:40.27 (copy 136_3697.JPG which does
not replicate)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free
server#2: The current time is: 14:22:41.59
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:25:30.76 (fill 136_3697.JPG with ASCII 0
character, still no replication)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free
Server#2: The current time is: 14:25:31.57
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:28:01.16 (copy 136_3697.JPG
136_3697.txt, no replication for both)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:27 PM <DIR> .
04/13/2006 02:27 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 116,646,313,984 bytes free
Server#2: The current time is: 14:28:02.18
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:30:09.99 (after adding 1 byte to
the
end
of 136_3697.JPG, now replication worked for 136_3697.JPG)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:29 PM <DIR> .
04/13/2006 02:29 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/13/2006 02:29 PM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 116,646,305,792 bytes free
Server#2: The current time is: 14:30:11.14
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:30 PM <DIR> .
04/13/2006 02:30 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/13/2006 02:29 PM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,074,779,648 bytes free
<FrsStageCsSubmitTransfer: 5988: 1828: S1: 14:21:22> Stage: submit
transfer 0xf6faa8
<ProcessOpenByIdStatus: 4452: 3025: S1: 14:21:22> ++
STATUS_OPLOCK_NOT_GRANTED
<FrsOpenSourceFileById: 4452: 3372: S0: 14:21:22> ++ ERROR -
NtCreateFile failed : NTStatus: STATUS_OPLOCK_NOT_GRANTED
4/13-14:21:23 :T: CoG: 45c90bcc CxtG: 92dea886 [LclCo ]
Name: 136_3693.JPG
4/13-14:21:23 :T: EventTime: Thu Apr 13, 2006 14:21:19
0
4/13-14:21:23 :T: FileG: 699e7b2a-1ea4-41bc-956f6431c20bf9b6
00020000 00000b8e
4/13-14:21:23 :T: ParentG: 9dae1abb-37fd-4376-ac879c64a5cd61a2
Size: 00000000 0000c000
4/13-14:21:23 :T: OrigG: 28400de8-945d-4a0f-b3772d622dfdd28e
Attr: 00000020
4/13-14:21:23 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
John Brineman
2006-04-24 13:48:02 UTC
Permalink
I have not. I am in a testing stage for Server2003R2. I have been using DFS
(with ntfrs) for several years (probably 4 or 5) and have not observed this
behavior. On the other hand I have used it only with stable files (reference
material) and not with active files or this type of file.
I probably will open a case after some more testing.
Thanks,
John Brineman
Post by Ned Pyle (MSFT)
Very interesting. Have either of you opened a case with PSS?
Post by John Brineman
I understand that. I reviewed the health report not the debug logs.
Zipping
and unzipping the file had the same affect as Minas got. The file started
replicating. This is a jpg file that has been downloaded (and jpeg
compressed) from a camera. I would assume from the file name that Minas has
that he has the same source for the file.
Thanks
John Brineman
Post by Ned Pyle (MSFT)
Hi John,
Keep in mind that all the previous thread was with FRS (Version 1, NTFRS).
If you are using DFSR it's going to be totally different. For that you'd
want to look at the DFSR debug logs and the DFSR health report, to start.
Ned
Post by John Brineman
I just installed Version R2 and set up DFS replication and had the identical
problem. It was laso with a .jpg file. There were 8 files in the
folder
an
3 of them replicated. The others did not. I will try some of your
tweaks
to
verify.
Thanks,
John Brineman
Post by Minas Hambardzumyan
My plan was to upload the file to the web site, download and check
that
it
still does not replicate and then ask you to download it and check on your
side. The first step was to upload the file and I had to use a web interface
on the web server to upload the file. I tried to do this and got an error
message -- the file failed to upload!
One other test -- I zipped the file in file explorer window and saw
that
zip
file replicates successfully. I then unzipped the file to find out
that
now
the extracted file does get replicated too!
So the conclusion is that the file *IS* the problem in the whole picture.
- It gets cloned and assigned to the new file when a copy of a file is
created (even when copied to a network drive)
- It does not change when the file contents changes (keeping file size the
same)
- It gets reinitialized though when the file size is changed
- It gets reinitialized when a file is zipped and then unzipped
- FRS may fail for some values of this property
I'll spend some time to investigate this. Please tell me if you have any
ideas.
<FrsDsGetSubscribers: 2672: 8249: S0: 14:12:26> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2672: 8249: S0: 14:12:26> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
Do you know what are these about?
Thanks,
Minas.
Post by Minas Hambardzumyan
Ned,
I started my test after 7:34am (you can see this by looking at the
date/time on directories "." and ".." in my message). So the only log
entry that is very suspicious is the one at 7:44am.
To make sure we are looking at right data at right time, I repeated my
actions -- now recording the time of each command execution. I have the
transcript below. According to it, I ran commands from 14:19 to
14:31.
I
ran FRSDIAG on both servers after finishing my commands and have frs logs
between those time points also inserted here. The first log
reference
to
file name 136_3697.JPG is at 14:30:02 on Server#1 and 13:30:03 on
Server#2. This is right after I added a single byte in the hex
editor
(my
dir command after it was executed at 14:30:09). Also, there is no
reference to the 136_3697.TXT in the log files.
Looks like the file actually does not get replicated. To finish once and
forever I decided to send my failing file to you -- to see if it
will
get
replicated on your side. This is where interesting things started to
happen. I will write about those in my next message -- not to mix
with
the
mess I have here.
Minas.
Server#1: The current time is: 14:19:48.25 (Empty Directory)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 116,651,122,688 bytes free
Server#2: The current time is: 14:19:52.63
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,077,216,768 bytes free
Server#1: The current time is: 14:21:31.80 (copy 136_3693.JPG which
replicates)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 116,651,040,768 bytes free
Server#2: The current time is: 14:21:33.85
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,134,848 bytes free
Server#1: The current time is: 14:22:40.27 (copy 136_3697.JPG which does
not replicate)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free
server#2: The current time is: 14:22:41.59
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:25:30.76 (fill 136_3697.JPG with ASCII 0
character, still no replication)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free
Server#2: The current time is: 14:25:31.57
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:28:01.16 (copy 136_3697.JPG
136_3697.txt, no replication for both)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:27 PM <DIR> .
04/13/2006 02:27 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 116,646,313,984 bytes free
Server#2: The current time is: 14:28:02.18
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:30:09.99 (after adding 1 byte to
the
end
of 136_3697.JPG, now replication worked for 136_3697.JPG)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:29 PM <DIR> .
04/13/2006 02:29 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/13/2006 02:29 PM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 116,646,305,792 bytes free
Server#2: The current time is: 14:30:11.14
D:\Manufacturing>dir
Volume in drive D is Data Volume
Ned Pyle (MSFT)
2006-04-20 21:22:54 UTC
Permalink
Crud, I lost track of this thread - sorry for the delay in response!

The NTFRSSubscriber object failures you see are due to an orphaned replica
member (i.e. a DC that was removed without being properly DCPROMO'ed or a
DFS/FRS member that was removed from the domain without telling DFS about
it). There is a thread from yesterday between myself and another customer on
this.

The issue with the JPG, where it's not being changed in any tangible way
except moving it in and out of the replica set and then it starts
replicaitng fine makes no sense to me at all except that if there was ever
any lock to it, it would have been cleared out. I'm scratching my head
otherwise...
Post by Minas Hambardzumyan
My plan was to upload the file to the web site, download and check that it
still does not replicate and then ask you to download it and check on your
side. The first step was to upload the file and I had to use a web
interface on the web server to upload the file. I tried to do this and got
an error message -- the file failed to upload!
One other test -- I zipped the file in file explorer window and saw that
zip file replicates successfully. I then unzipped the file to find out
that now the extracted file does get replicated too!
So the conclusion is that the file *IS* the problem in the whole picture.
- It gets cloned and assigned to the new file when a copy of a file is
created (even when copied to a network drive)
- It does not change when the file contents changes (keeping file size the
same)
- It gets reinitialized though when the file size is changed
- It gets reinitialized when a file is zipped and then unzipped
- FRS may fail for some values of this property
I'll spend some time to investigate this. Please tell me if you have any
ideas.
<FrsDsGetSubscribers: 2672: 8249: S0: 14:12:26> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2672: 8249: S0: 14:12:26> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
Do you know what are these about?
Thanks,
Minas.
Post by Minas Hambardzumyan
Ned,
I started my test after 7:34am (you can see this by looking at the
date/time on directories "." and ".." in my message). So the only log
entry that is very suspicious is the one at 7:44am.
To make sure we are looking at right data at right time, I repeated my
actions -- now recording the time of each command execution. I have the
transcript below. According to it, I ran commands from 14:19 to 14:31. I
ran FRSDIAG on both servers after finishing my commands and have frs logs
between those time points also inserted here. The first log reference to
file name 136_3697.JPG is at 14:30:02 on Server#1 and 13:30:03 on
Server#2. This is right after I added a single byte in the hex editor (my
dir command after it was executed at 14:30:09). Also, there is no
reference to the 136_3697.TXT in the log files.
Looks like the file actually does not get replicated. To finish once and
forever I decided to send my failing file to you -- to see if it will get
replicated on your side. This is where interesting things started to
happen. I will write about those in my next message -- not to mix with
the mess I have here.
Minas.
Server#1: The current time is: 14:19:48.25 (Empty Directory)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 116,651,122,688 bytes free
Server#2: The current time is: 14:19:52.63
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:07 PM <DIR> .
04/13/2006 02:07 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 18,077,216,768 bytes free
Server#1: The current time is: 14:21:31.80 (copy 136_3693.JPG which
replicates)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 116,651,040,768 bytes free
Server#2: The current time is: 14:21:33.85
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,134,848 bytes free
Server#1: The current time is: 14:22:40.27 (copy 136_3697.JPG which does
not replicate)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free
server#2: The current time is: 14:22:41.59
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:25:30.76 (fill 136_3697.JPG with ASCII
0 character, still no replication)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:22 PM <DIR> .
04/13/2006 02:22 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
2 File(s) 2,423,831 bytes
2 Dir(s) 116,648,693,760 bytes free
Server#2: The current time is: 14:25:31.57
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:28:01.16 (copy 136_3697.JPG
136_3697.txt, no replication for both)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:27 PM <DIR> .
04/13/2006 02:27 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,941 bytes
2 Dir(s) 116,646,313,984 bytes free
Server#2: The current time is: 14:28:02.18
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:21 PM <DIR> .
04/13/2006 02:21 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
1 File(s) 46,721 bytes
2 Dir(s) 18,077,167,616 bytes free
Server#1: The current time is: 14:30:09.99 (after adding 1 byte to the
end of 136_3697.JPG, now replication worked for 136_3697.JPG)
D:\Manufacturing>dir
Volume in drive D is Data
Volume Serial Number is 84E5-4467
Directory of D:\Manufacturing
04/13/2006 02:29 PM <DIR> .
04/13/2006 02:29 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/13/2006 02:29 PM 2,377,111 136_3697.JPG
12/11/2004 10:59 AM 2,377,110 136_3697.txt
3 File(s) 4,800,942 bytes
2 Dir(s) 116,646,305,792 bytes free
Server#2: The current time is: 14:30:11.14
D:\Manufacturing>dir
Volume in drive D is Data Volume
Volume Serial Number is F845-F248
Directory of D:\Manufacturing
04/13/2006 02:30 PM <DIR> .
04/13/2006 02:30 PM <DIR> ..
12/11/2004 04:32 PM 46,721 136_3693.JPG
04/13/2006 02:29 PM 2,377,111 136_3697.JPG
2 File(s) 2,423,832 bytes
2 Dir(s) 18,074,779,648 bytes free
<FrsStageCsSubmitTransfer: 5988: 1828: S1: 14:21:22> Stage: submit
transfer 0xf6faa8
<ProcessOpenByIdStatus: 4452: 3025: S1: 14:21:22> ++
STATUS_OPLOCK_NOT_GRANTED
<FrsOpenSourceFileById: 4452: 3372: S0: 14:21:22> ++ ERROR -
NtCreateFile failed : NTStatus: STATUS_OPLOCK_NOT_GRANTED
4/13-14:21:23 :T: CoG: 45c90bcc CxtG: 92dea886 [LclCo ]
Name: 136_3693.JPG
4/13-14:21:23 :T: EventTime: Thu Apr 13, 2006 14:21:19
Ver: 0
4/13-14:21:23 :T: FileG: 699e7b2a-1ea4-41bc-956f6431c20bf9b6
FID: 00020000 00000b8e
00000000 0000c000
00000020
4/13-14:21:23 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
ReplicaName: AOS|MANUFACTURING (4)
4/13-14:21:23 :T: CoFlags: 0100042c [Content Locn LclCo NewFile
CmpresStage ]
4/13-14:21:23 :T: UsnReason: 00008003 [DatOvrWrt DatExt Info ]
4/13-14:21:23 :T: CxtionG: 92dea886-2851-4337-92e0ac801fcec1b8
4/13-14:21:23 :T: CheckSum: d3c1d9d5 75067e65 96a97ef1 e33dcd4c
4/13-14:21:23 :T: CoArrival: <null>
4/13-14:21:23 :T: FullPathName: \\.\D:\Manufacturing\136_3693.JPG
<FrsHashCalcString: 2660: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<FrsHashCalcString: 2660: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<FrsDsFindComputer: 2672: 8796: S2: 14:22:26> :DS: Computer
FQDN is cn=ofna,ou=domain controllers,dc=aos,dc=local
Computer's dns name is ofna.AOS.local
<FrsDsFindComputer: 2672: 8816: S2: 14:22:26> :DS: Settings
reference is cn=ntds
settings,cn=ofna,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<FrsDsGetSubscribers: 2672: 8249: S0: 14:22:26> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2672: 8249: S0: 14:22:26> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
Waiting
normal wait
Waiting
normal wait
Waiting
normal wait
Waiting
normal wait
<FrsDsFindComputer: 2672: 8796: S2: 14:27:26> :DS: Computer
FQDN is cn=ofna,ou=domain controllers,dc=aos,dc=local
Computer's dns name is ofna.AOS.local
<FrsDsFindComputer: 2672: 8816: S2: 14:27:26> :DS: Settings
reference is cn=ntds
settings,cn=ofna,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<DbgPrintThreadIds: 2672: 1021: S2: 14:27:26> :H: Known
thread IDs -
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: First : 440
2616
2672
5472
2776
2780
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: ReplicaCs
: 4440
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: JRNL : 2940
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: DBCs : 2944
3664
3684
ChgOrdRetryCS : 1376
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: Wait : 880
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: ThCs : 3120
3196
5964
4452
<DbgPrintThreadIds: 2672: 1029: S2: 14:27:26> :H: InstallCs
: 2396
<FrsPrintAllocStats: 2672: 234: S2: 14:27:26>
<FrsPrintAllocStats: 2672: 235: S2: 14:27:26> NTFRS MEMORY
<FrsPrintAllocStats: 2672: 238: S2: 14:27:26> ENABLE
STATS : FALSE
694537 KB (3350000 calls)
<FrsPrintAllocStats: 2672: 246: S2: 14:27:26> Freed : 0
KB (0 calls)
<FrsPrintAllocStats: 2672: 249: S2: 14:27:26> Delta : 0
KB
0 KB
<FrsPrintAllocStats: 2672: 255: S2: 14:27:26> Addr Range
: 36522 KB
<FrsPrintAllocStats: 2672: 256: S2: 14:27:26> OnFreeList
: 0
3346884
3116
0x00255810
0x02600060
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
THREAD_CONTEXT_TYPE : 14 Calls, 5 Max, 3 busy
13608 Calls, 5 Max, 4 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
REPLICA_THREAD_TYPE : 13676 Calls, 11 Max, 2 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
CONFIG_NODE_TYPE : 144189 Calls, 21 Max, 1 busy
27219 Calls, 11 Max, 9 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26> GUID/RPC
HANDLE : 2 Calls, 2 Max, 2 busy
13270 Calls, 19 Max, 10 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26> GEN_TABLE_TYPE
: 135877 Calls, 47 Max, 39 busy
3 Calls, 3 Max, 3 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
VOLUME_MONITOR_ENTRY_TYPE : 2 Calls, 2 Max, 1 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
COMMAND_PACKET_TYPE : 178685 Calls, 24 Max, 13 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
GENERIC_HASH_TABLE_TYPE : 3 Calls, 3 Max, 3 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
CHANGE_ORDER_ENTRY_TYPE : 67 Calls, 11 Max, 0 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
FILTER_TABLE_ENTRY_TYPE : 26 Calls, 26 Max, 26 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
QHASH_TABLE_TYPE : 30 Calls, 25 Max, 23 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
OUT_LOG_PARTNER_TYPE : 4 Calls, 3 Max, 3 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
WILDCARD_FILTER_ENTRY_TYPE: 15 Calls, 15 Max, 15 busy
<FrsPrintAllocStats: 2672: 268: S2: 14:27:26>
REPARSE_TAG_TABLE_TYPE : 24360 Calls, 3 Max, 3 busy
<FrsPrintAllocStats: 2672: 270: S2: 14:27:26>
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 0
to 15 : 506712 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 16
to 31 : 602127 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 32
to 47 : 405311 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 48
to 63 : 46755 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 64
to 79 : 382512 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 80
to 95 : 227138 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 96
to 111 : 16375 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 112
to 127 : 41941 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 128
to 143 : 46735 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 144
to 159 : 168993 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 160
to 175 : 11013 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 176
to 191 : 106007 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 192
to 207 : 62546 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 208
to 223 : 64959 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 224
to 239 : 165087 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 240
to 255 : 48934 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 256
to 271 : 29230 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 272
to 287 : 52086 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 288
to 303 : 16243 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 304
to 319 : 21725 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 320
to 335 : 3 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 352
to 367 : 10974 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 368
to 383 : 10972 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 384
to 399 : 836 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 416
to 431 : 13609 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 512
to 527 : 8748 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 560
to 575 : 27218 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 608
to 623 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 640
to 655 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 784
to 799 : 41679 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 800
to 815 : 40614 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 848
to 863 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 864
to 879 : 13779 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 880
to 895 : 13667 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 944
to 959 : 27502 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 976
to 991 : 67 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1008
to 1023 : 13667 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1024
to 1039 : 6112 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1088
to 1103 : 13779 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1104
to 1119 : 13779 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1184
to 1199 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1200
to 1215 : 4 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1216
to 1231 : 27502 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1408
to 1423 : 55 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1616
to 1631 : 3 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 1792
to 1807 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2048
to 2063 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2128
to 2143 : 13610 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2160
to 2175 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2480
to 2495 : 10 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2544
to 2559 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 2736
to 2751 : 13610 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 3152
to 3167 : 11 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 3264
to 3279 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 4000
to 4015 : 13611 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 4096
to 4111 : 4 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 4976
to 4991 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 4992
to 5007 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 5504
to 5519 : 2 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 5632
to 5647 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 7856
to 7871 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 8192
to 8207 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 8448
to 8463 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 9744
to 9759 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 10368
to 10383 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 12080
to 12095 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 13120
to 13135 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 13696
to 13711 : 1 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 278: S2: 14:27:26> 16368
to 16383 : 2119 Calls, 0 Max, 0 busy
<FrsPrintAllocStats: 2672: 280: S2: 14:27:26>
<FrsDsGetSubscribers: 2672: 8249: S0: 14:27:26> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
Waiting
normal wait
Waiting
normal wait
<FrsDsGetSubscribers: 2672: 8249: S0: 14:27:26> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=ofna,ou=domain controllers,dc=aos,dc=local!
<FrsStageCsSubmitTransfer: 6104: 1828: S1: 14:30:02> Stage: submit
transfer 0xf6f980
<ProcessOpenByIdStatus: 4548: 3025: S1: 14:30:02> ++
STATUS_OPLOCK_NOT_GRANTED
<FrsOpenSourceFileById: 4548: 3372: S0: 14:30:02> ++ ERROR -
NtCreateFile failed : NTStatus: STATUS_OPLOCK_NOT_GRANTED
4/13-14:30:02 :T: CoG: d7f4d1be CxtG: 92dea886 [LclCo ]
Name: 136_3697.JPG
4/13-14:30:02 :T: EventTime: Thu Apr 13, 2006 14:29:59
Ver: 0
4/13-14:30:02 :T: FileG: 7ff26913-b482-422f-873ebf0c7f6ffb77
FID: 00020000 00000b94
00000000 00245000
00000120
4/13-14:30:02 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
ReplicaName: AOS|MANUFACTURING (4)
4/13-14:30:02 :T: CoFlags: 0100042c [Content Locn LclCo NewFile
CmpresStage ]
4/13-14:30:02 :T: UsnReason: 0000a803 [RenNew DatOvrWrt DatExt Info
Security ]
4/13-14:30:02 :T: CxtionG: 92dea886-2851-4337-92e0ac801fcec1b8
4/13-14:30:02 :T: CheckSum: 84893f8c f279b69f 9ec5d039 8a3713e0
4/13-14:30:02 :T: CoArrival: <null>
4/13-14:30:02 :T: FullPathName: \\.\D:\Manufacturing\136_3697.JPG
<FrsHashCalcString: 2660: 4842: S0: 14:30:02> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<FrsHashCalcString: 2660: 4842: S0: 14:30:03> Name =
S-1-5-21-3820246116-1162185781-4246705241-1175
<RcsSetCxtionSchedule: 4312: 7365: S0: 14:30:32> :X: b454415e,
schedule is on
<RcsSetCxtionSchedule: 4312: 7365: S0: 14:30:32> :X: 242cdbff,
schedule is on
<RcsSetCxtionSchedule: 4312: 7365: S0: 14:30:32> :X: 6177bd09,
schedule is on
<RcsSetCxtionSchedule: 4312: 7365: S0: 14:30:32> :X: f938acb4,
schedule is on
<FrsDsFindComputer: 2508: 8796: S2: 14:19:02> :DS: Computer
FQDN is cn=amber,ou=domain controllers,dc=aos,dc=local
Computer's dns name is amber.AOS.local
<FrsDsFindComputer: 2508: 8816: S2: 14:19:02> :DS: Settings
reference is cn=ntds
settings,cn=amber,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<FrsDsGetSubscribers: 2508: 8249: S0: 14:19:02> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2508: 8249: S0: 14:19:02> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<FrsHashCalcString: 7284: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1005
<MainWait: 7916: 598: S0: 14:21:23> Wait thread
has started.
<FrsHashCalcString: 7284: 4842: S0: 14:21:23> Name =
S-1-5-21-3820246116-1162185781-4246705241-1005
4/13-14:21:23 :T: CoG: 45c90bcc CxtG: b454415e [RemCo ]
Name: 136_3693.JPG
4/13-14:21:23 :T: EventTime: Thu Apr 13, 2006 14:21:19
Ver: 0
4/13-14:21:23 :T: FileG: 699e7b2a-1ea4-41bc-956f6431c20bf9b6
FID: 00360000 0000007b
00000000 0000c000
00000020
4/13-14:21:23 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
ReplicaName: AOS|MANUFACTURING (19)
4/13-14:21:23 :T: CoFlags: 0100040c [Content Locn NewFile
CmpresStage ]
4/13-14:21:23 :T: UsnReason: 00008003 [DatOvrWrt DatExt Info ]
4/13-14:21:23 :T: CxtionG: b454415e-05a1-4c63-b668367fefd85bf4
4/13-14:21:23 :T: CheckSum: d3c1d9d5 75067e65 96a97ef1 e33dcd4c
4/13-14:21:23 :T: CoArrival: Thu Apr 13, 2006 14:21:23
\\?\D:\Manufacturing\DO_NOT_REMOVE_NtFrs_PreInstall_Directory\NTFRS_45c90bcc-ef87-441c-9f71433bfd0abb9f
<FrsDsFindComputer: 2508: 8796: S2: 14:24:02> :DS: Computer
FQDN is cn=amber,ou=domain controllers,dc=aos,dc=local
Computer's dns name is amber.AOS.local
<FrsDsFindComputer: 2508: 8816: S2: 14:24:02> :DS: Settings
reference is cn=ntds
settings,cn=amber,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<FrsDsGetSubscribers: 2508: 8249: S0: 14:24:02> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2508: 8249: S0: 14:24:02> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
Waiting
normal wait
Waiting
normal wait
Waiting
normal wait
Waiting
normal wait
Waiting
normal wait
Waiting
normal wait
<FrsDsFindComputer: 2508: 8796: S2: 14:29:02> :DS: Computer
FQDN is cn=amber,ou=domain controllers,dc=aos,dc=local
Computer's dns name is amber.AOS.local
<FrsDsFindComputer: 2508: 8816: S2: 14:29:02> :DS: Settings
reference is cn=ntds
settings,cn=amber,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=aos,dc=local
<FrsDsGetSubscribers: 2508: 8249: S0: 14:29:02> :DS: No
NTFRSSubscriber object found under cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<FrsDsGetSubscribers: 2508: 8249: S0: 14:29:02> :DS: No
NTFRSSubscriber object found under
cn=4dbc857f-f66c-46dc-aec8-7d3cf3355892,cn=dfs volumes,cn=ntfrs
subscriptions,cn=amber,ou=domain controllers,dc=aos,dc=local!
<FrsHashCalcString: 7284: 4842: S0: 14:30:02> Name =
S-1-5-21-3820246116-1162185781-4246705241-1005
<FrsHashCalcString: 7284: 4842: S0: 14:30:02> Name =
S-1-5-21-3820246116-1162185781-4246705241-1005
4/13-14:30:03 :T: CoG: d7f4d1be CxtG: b454415e [RemCo ]
Name: 136_3697.JPG
4/13-14:30:03 :T: EventTime: Thu Apr 13, 2006 14:29:59
Ver: 0
4/13-14:30:03 :T: FileG: 7ff26913-b482-422f-873ebf0c7f6ffb77
FID: 00980000 0000136c
00000000 00245000
00000120
4/13-14:30:03 :T: LocnCmd: Create State: IBCO_COMMIT_STARTED
ReplicaName: AOS|MANUFACTURING (19)
4/13-14:30:03 :T: CoFlags: 0100040c [Content Locn NewFile
CmpresStage ]
4/13-14:30:03 :T: UsnReason: 0000a803 [RenNew DatOvrWrt DatExt Info
Security ]
4/13-14:30:03 :T: CxtionG: b454415e-05a1-4c63-b668367fefd85bf4
4/13-14:30:03 :T: CheckSum: 84893f8c f279b69f 9ec5d039 8a3713e0
4/13-14:30:03 :T: CoArrival: Thu Apr 13, 2006 14:30:02
\\?\D:\Manufacturing\DO_NOT_REMOVE_NtFrs_PreInstall_Directory\NTFRS_d7f4d1be-c1d2-48ad-87e151cc4ea9d7f4
<RcsSetCxtionSchedule: 7544: 7365: S0: 14:30:55> :X: 6177bd09,
schedule is on
<RcsSetCxtionSchedule: 7544: 7365: S0: 14:30:55> :X: f938acb4,
schedule is on
<RcsSetCxtionSchedule: 7544: 7365: S0: 14:30:55> :X: b454415e,
schedule is on
<RcsSetCxtionSchedule: 7544: 7365: S0: 14:30:56> :X: 242cdbff,
schedule is on
Post by Ned Pyle (MSFT)
From basic examination, everything looks good - no misconfig, no old
FRS, no filters - all is well. So I dug further into the NTFRS_0005.log
On server1, 136_3697.txt is renamed to 136_3697.jpg and change order is
sent out (at 4/11-07:33:29).
On server2, 136_3697.jpg is transferred in successfully to pre-install
(at 4/11-07:33:29)
At 4/11-07:34:27, it's done again, and works again.
At 4/11-07:44:28 , it looks like maybe the file was overwritten with the
same file? It replicates again without issues.
At 4/11-07:46:40, we get a temporary copy of the file (was this when it
was opened in a hex editor?)
At 4/11-07:46:41 the 136_3697.jpg.Hex Editor 3 temp save file shows up -
that replicates fine too.
So, the logs claim everything is replicating normally. I must admit -
I'm scratching my head here, Minas.
Ned
Continue reading on narkive:
Loading...