Fabrizio
Guest
|
 Posted:
Fri Jan 21, 2005 1:33 pm Post subject:
FRS in error state |
|
|
Hi there,
I have a Dfs topology where I setup the Dfs root on a SAN unit running
W2K. I have a couple of directories on a W2K server that I am trying
to replicate onto the same SAN unit that hosts the Dfs root. The
directoreis contain different number of subfolders/files and the total
size of each directory is 3 GB and 22 GB respectively. First, I add
the Dfs link and the link replica that replicates the 3GB directory
from my server to the SAN unit. Replication works fine, and everything
gets replicated. However, as soon as I add a 2nd link and the replica
to replicate the larger directory, the File Replication Service on the
source (i.e. primary) server goes into error state logging two events
in the File Replication Service event log which basically say that the
server could not be added as a replica member for the given Dfs link.
I remove the Dfs link and the replica and everything goes back to
normal. I add the link again, and I get the same events, event ID
13552 and one more (which I can't remember right now). I can't really
explain why it would work for the smaller directory, but not the
larger one. Some of the specifics my setup are:
- I only have these two links. There are no other Dfs links in my
entire system.
- Neither the Dfs server nor the server hosting the source directory
is a domain controller
- All my servers run W2K
- Staging area on all machines is set to 40 GB, working directory has
been reconfigured to a separate folder on the same partition as the
staging area. The total size of this partition is 90 GB.
- NTFS Journal File size has been reconfigured to 1 GB.
- The larger directory has a total of 200,000 files
- Jet database size is currently around 30 MB.
I don't believe I am exceeding any of FRS limitations. So, I can't
explain why FRS would go into error state with the larger directory
while it works just fine with the smaller on the same server.
Any help would be greatly appreciated.
thanks,
Fari |
|
Glenn L
Guest
|
| Posted:
Sat Jan 22, 2005 4:54 am Post subject:
Re: FRS in error state |
|
|
your best bet to troubleshoot this is FRSDIAG.
download it here
http://www.microsoft.com/downloads/details.aspx?FamilyId=43CB658E-8553-4DE7-811A-562563EB5EBF&displaylang=en
You will need to run FRSDIAG from XP or W2K3 against the W2K server.
First remove the second link.
Then stop the FRS service on source server and target servers.
Delete the NTFRS_0001 through 0005.log files on both servers. (gives you a
clean slate of logs to troubleshoot from)
Then start the FRS service on the source and target.
Then add the link and link targets.
As soon as the source server errors out, run FRSDIAG against it.
It returns lots of info and attempts to parse the log files to help you
understand what is going wrong with FRS.
--
Glenn L
CCNA, MCSE 2000/2003 + Security
"Fabrizio" <fuladi@yahoo.com> wrote in message
news:71f9c15c.0501202333.440cd957@posting.google.com...
| Quote: | Hi there,
I have a Dfs topology where I setup the Dfs root on a SAN unit running
W2K. I have a couple of directories on a W2K server that I am trying
to replicate onto the same SAN unit that hosts the Dfs root. The
directoreis contain different number of subfolders/files and the total
size of each directory is 3 GB and 22 GB respectively. First, I add
the Dfs link and the link replica that replicates the 3GB directory
from my server to the SAN unit. Replication works fine, and everything
gets replicated. However, as soon as I add a 2nd link and the replica
to replicate the larger directory, the File Replication Service on the
source (i.e. primary) server goes into error state logging two events
in the File Replication Service event log which basically say that the
server could not be added as a replica member for the given Dfs link.
I remove the Dfs link and the replica and everything goes back to
normal. I add the link again, and I get the same events, event ID
13552 and one more (which I can't remember right now). I can't really
explain why it would work for the smaller directory, but not the
larger one. Some of the specifics my setup are:
- I only have these two links. There are no other Dfs links in my
entire system.
- Neither the Dfs server nor the server hosting the source directory
is a domain controller
- All my servers run W2K
- Staging area on all machines is set to 40 GB, working directory has
been reconfigured to a separate folder on the same partition as the
staging area. The total size of this partition is 90 GB.
- NTFS Journal File size has been reconfigured to 1 GB.
- The larger directory has a total of 200,000 files
- Jet database size is currently around 30 MB.
I don't believe I am exceeding any of FRS limitations. So, I can't
explain why FRS would go into error state with the larger directory
while it works just fine with the smaller on the same server.
Any help would be greatly appreciated.
thanks,
Fari |
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in