Windows Server

Glenn L · Guest

I need a recap of the setup.
3 servers right? names, OS, SP levels?
two of them are replicating back and forth successfully right? which two

"Asgard Hostmaster" wrote:

Asgard Hostmaster · Guest

I have two servers at a remote data center, SB-2 and SB-3. Actually I have
three, but the third is linux, so can be ignored :-)

SB-2 is Windows 2000 standard
SB-3 is Windows 2003 standard
both have all the latest publicly released SPs, patches

SB-3 is currently the PDC, SB-2 has all other roles
SB-3 hosts the dfsroot
SYSVOL is now apparently replicating fine.
After getting that working I began adding other folders for replication.
First a folder of about 10mb total called ASGARD. It now seems to be
replicating just fine.
I then added the folder I'm particularly wanting to replicate, CLIENTWEBS.
Its about 8GB, 400 folders and well, heaps of files :-). Note that I have
increased the FRS staging space to 10Gb in the registry.

On SB-2, about 2 minutes after NTFRS is started I'm getting the errors below
in the event log and then NTFRS is shutdown. It restarts 20mins later and
the whole cycle starts again. If I remove CLIENTWEBS from the DFS set,
things start to work again

******************************************
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13552
Date: 10/22/2004
Time: 6:49:53 AM
User: N/A
Computer: SB-2
Description:
The File Replication Service is unable to add this computer to the following
replica set:
"DFSROOT|CLIENTWEBS"

This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0

The information below may help to resolve the problem:
Computer DNS name is "SB-2.asgard.net"
Replica set member name is "{717F03BF-916B-4CAC-A6E4-E14AD118275C}"
Replica set root path is "c:\inetpub\clients"
Replica staging directory path is "c:\frs-staging"
Replica working directory path is "c:\winnt\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorSuccess

Other event log messages may also help determine the problem. Correct the
problem and the service will attempt to restart replication automatically at
a later time.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
******************************************

******************************************
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13555
Date: 10/22/2004
Time: 6:49:58 AM
User: N/A
Computer: SB-2
Description:
The File Replication Service is in an error state. Files will not replicate
to or from one or all of the replica sets on this computer until the
following recovery steps are performed: <removed for brevity>
******************************************

******************************************
Event Type: Information
Event Source: NtFrs
Event Category: None
Event ID: 13516
Date: 10/22/2004
Time: 6:50:09 AM
User: N/A
Computer: SB-2
Description:
The File Replication Service is no longer preventing the computer SB-2 from
becoming a domain controller. The system volume has been successfully
initialized and the Netlogon service has been notified that the system
volume is now ready to be shared as SYSVOL.

Type "net share" to check for the SYSVOL share.
******************************************

******************************************
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13506
Date: 10/22/2004
Time: 6:55:50 AM
User: N/A
Computer: SB-2
Description:
The File Replication Service failed a consistency check
(!Cxtion->Inbound)
in "OutLogCleanupWorker:" at line 5000.

The File Replication Service will restart automatically at a later time. If
this problem persists a subsequent entry in this event log describes the
recovery procedure.
For more information about the automatic restart right click on My Computer
and then click on Manage, System Tools, Services, File Replication Service,
and Recovery.
******************************************

Glenn L · Guest

My experience with 13506 errors is limited.
The ones I have come across have required a restore of the replica member.
(blow away the FRS database)

Since you only have 2 replica members, it may be quicker to shotgun this
rather than troubleshooting anything furtherr.
Stop FRS on both systems.
pick the system you want to be the master replica.
HKLM\system\ccs\services\NTFRS\parameters\backup/restore\process at startup
Modify "burflags" to a HEX value of D4
Start FRS on this system.
The FRS service should complete its processing (walk the tree and create
file IDs for every folder and file in the dataset) before starting FRS on
the downstream partner.
When this process completes (NTFRS processor utilization drops to 0) proceed
to the other member.
HLKM\system\ccs\services\NTFRS\parameters\backup/restore\process at startup
Modify "burflags" to a HEX value of D2
Start FRS on this system.

All data should synchronize.

--
Glenn L
CCNA, MCSE 2000, MCSE 2003 + Security

"Asgard Hostmaster" <hostmaster@_remove_asgard.net> wrote in message
news:eFhtckDuEHA.3392@TK2MSFTNGP10.phx.gbl...

Asgard Hostmaster · Guest

Hi Glen,

Already tried that numerous times. However, I have made some progress in
narrowing the problem. NTFRS is only dying when my main replication folder
is added. If I add small test folders, then everything now works fine.
Adding the main folder, around 8GB, all seems to be working, ie no errors,
but there is no replication. I assume this is because the source machine is
still processing the files. So, I've tried just leaving it to see what
happens. The ntfrs.jdb file keeps growing, after about a day it's around
150mb or so and at this point the NTFRS service keeps crashing every 30 mins
or so. If I remove the problem link, rename the jet folder, and restart,
then replication on the other folders works just fine.

So it either means NTFRS just doesn't like that folder, or it's hitting some
other problem when the journal gets too big (yes I had raised the size in
the registry).

"Glenn L" <the.only@gmail.com> wrote in message
news:usitfOeuEHA.1992@TK2MSFTNGP10.phx.gbl...

admir · Guest

Hi there,

I have exectly the same problem. (Error 13508)

I have bean posting this issue for sometime but no response. I Have 2
replicas. One of them is a folder with about 30 subfolders and other is
about 800 subfolders. The one with 800 subfolders is having trouble
replicating. The real kouse of this is unknown to me but I have notesd
that stagging folder is on diferent partition then replica. So what I am
about to do is change the location of the frs stagging folder to the
same partition as replica.

Annyway I will let you know.

Gr,

Admir
"Asgard Hostmaster" <hostmaster@asgard_remove_.net> wrote in message
news:uUOF1MZsEHA.2460@TK2MSFTNGP09.phx.gbl...

admir · Guest

Hi there,

I have not changed the location of the stagging folder. I just made sure I
have inaffspace on the disks and that staging space is inaff.
Next think I did is I gave full rights to "SYSTEM" on evry posible folder
that had to do anything with DFS and its replicas.
After that I restarted FRS. in the begining I get event id 13508 on both
servers after 10 minutes or so one of the servers (The one that is running
DFS root and where replicas are) starts showing even id 13509, saying that
replication started. This applayes for both folders. (the big one and the
small one)

On the other hand other server that is holding the originals is still
showing event id 13508.

In ntfrs log files (NtFrs_0001.log tru NtFrs_0005.log) shows this error
several times.

FrsOpenSourceFileById 68736:00:00 80256:00:00 S0 10 56 21> ++ ERROR -
NtCreateFile failed NTStatus STATUS_OPLOCK_NOT_GRANTED

What does this mean and how can I fix it?

On the server where dfs root is runing I get folowing Errors several times:

<RcsCreateSeedingCxtion 9548 7078 S0 12 2 44> X ERROR - no parent computer
found for DFSROOT|CURSI WStatus ERROR_FILE_NOT_FOUND

And

FrsOpenSourceFileById 2832 3344 S0 12 2 10> ++ ERROR - NtCreateFile failed
NTStatus STATUS_OBJECT_NAME_NOT_FOUND

I am realy confused cos sysvol is replicating just fine and the other folder
(folder with less subfolders) too.

please help.

"Asgard Hostmaster" <hostmaster@asgard_remove_.net> wrote in message
news:uUOF1MZsEHA.2460@TK2MSFTNGP09.phx.gbl...

Asgard Hostmaster · Guest

I've given up trying to replicate the large folder, I'm now looking at
trying to setup replication for each individual subfolder and see if I can
narrow the problem down

"admir" <admir@kuub3.nl> wrote in message
news:ujkab2AvEHA.3728@TK2MSFTNGP12.phx.gbl...

	Windows Server Forum Index -> DFS and FRS	All times are GMT Goto page Previous 1, 2
Page 2 of 2