Event ID: 13508

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I've got a shared folder that has been replicating across two servers with no
problems for at least a year. Suddenly its stopped replicating. I'm getting
the 13508 error on both servers.

netdiag /est:dns doesn't report any problems
frsdiag only reports a huge backlog error (not too surprising since I've
spent a week on this)

SYSVOL seems to be replicating but not my dfs root.

The only other factors are that my dfs share is now over 5Gb - don't know if
thats a problem but I've a got a staging area of 6Gb anyway. And the DNS
test (in dns manager) passes the simple test but fails the recursive test on
both servers.
 
Update:

Definitely working on the sysvol folder just not on my dfs root.

Also checked time is sync'ed across all DCs

Also verified enough disk space, checked and defragged.
 
Been through the suggestions now - still no joy.

When I bounce the FRS Service (after 5 mins) I get 13508 for both sysvol and
my dfs share, then shortly after I get 13509 but only for sysvol. If there
is a DNS problem why does it work for sysvol?
 
Hmmm...either the Dfs link is OK, or there's bigger issues. Check back in
the logs for a JRNL_WRAP_ERROR. Otherwise, you're going to have to get one
of the Dfs utils and run that.

What about deleting the replica's and starting again?


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net


Been through the suggestions now - still no joy.

When I bounce the FRS Service (after 5 mins) I get 13508 for both sysvol and
my dfs share, then shortly after I get 13509 but only for sysvol. If there
is a DNS problem why does it work for sysvol?
 
Hi

The 13508 indicates that the replication partner can't be contacted. The
13509 indicates that this has been rectified. You can see this (and it can
be quite normal) if you're replicating across a WAN link that has
intermittent availability.

Take a look at FRSDiag from

http://www.microsoft.com/windowsserver2003/technologies/fileandprint/file/dfs/tshootfrs.mspx

It gets installed under \Program Files\Windows Resource Kits\Tools\FRSDiag

Run it on each server (better to run on each server individually rather than
across the network so events get interpreted correctly) with all option
ticked as well as Tools -> Build GUID2Name for Targer Server(s).

You'll get a bunch of info as well as an FRSDiag.txt file which summarises
things and possibly provides some actions. Other stuff worth looking at is
repadmin_showconn.txt and repadmin_showreps.txt.

It might be as simple as Paul suggests where you can just remove and
re-create the replicas.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Thanks guys - all working now - I've got that sync'ing feeling again.

Last night I moved the data out of the replicating folders, deleted the
folders, recreated and reshared them, added them back to the dfs, then moved
the root data back and it all started sync'ing again.

Thought there may have been disk issues but not sign of any after a full
scan of all drives.

Mark Renoden said:
Hi

The 13508 indicates that the replication partner can't be contacted. The
13509 indicates that this has been rectified. You can see this (and it can
be quite normal) if you're replicating across a WAN link that has
intermittent availability.

Take a look at FRSDiag from

http://www.microsoft.com/windowsserver2003/technologies/fileandprint/file/dfs/tshootfrs.mspx

It gets installed under \Program Files\Windows Resource Kits\Tools\FRSDiag

Run it on each server (better to run on each server individually rather than
across the network so events get interpreted correctly) with all option
ticked as well as Tools -> Build GUID2Name for Targer Server(s).

You'll get a bunch of info as well as an FRSDiag.txt file which summarises
things and possibly provides some actions. Other stuff worth looking at is
repadmin_showconn.txt and repadmin_showreps.txt.

It might be as simple as Paul suggests where you can just remove and
re-create the replicas.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.

ptwilliams said:
Hmmm...either the Dfs link is OK, or there's bigger issues. Check back in
the logs for a JRNL_WRAP_ERROR. Otherwise, you're going to have to get
one
of the Dfs utils and run that.

What about deleting the replica's and starting again?


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net


Been through the suggestions now - still no joy.

When I bounce the FRS Service (after 5 mins) I get 13508 for both sysvol
and
my dfs share, then shortly after I get 13509 but only for sysvol. If
there
is a DNS problem why does it work for sysvol?
Click to expand...
Click to expand...
 
Back
Top