Re: Event ID: 13508

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Mark Renoden [MSFT] (markreno_at_online.microsoft.com)
Date: 11/15/04


Date: Tue, 16 Nov 2004 09:06:01 +1100

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: markreno@online.microsoft.com
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" <ptw2001@hotmail.com> wrote in message 
news:OmmVgy0yEHA.3236@TK2MSFTNGP15.phx.gbl...
> 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
>
>
> "TonyR" <TonyR@discussions.microsoft.com> wrote in message
> news:97CC33C9-F444-480B-AD05-9C89FF790D4E@microsoft.com...
> 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?
>
> "ptwilliams" wrote:
>
>> There are a number of good FRS tools out there - quite a few MS ones.
>>
>> Have a look at this and try following some of the suggestions:
>>  --
>> http://www.eventid.net/display.asp?eventid=13508&eventno=349&source=NtFrs&phase=1
>>
>>
>> -- 
>>
>> Paul Williams
>>
>> http://www.msresource.net
>> http://forums.msresource.net
>>
>>
>> "TonyR" <TonyR@discussions.microsoft.com> wrote in message
>> news:ED38F9BE-6DB6-41A3-8405-88DDD45C439A@microsoft.com...
>> 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.
>>
>> "TonyR" wrote:
>>
>> > 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.
>>
>>
>>
>
> 


Relevant Pages

  • FRS and DFS debug
    ... I'm trying to diagnose issues that I'm having with replicating some shares across some servers. ... sysvol shares though, seem to replicate ok between the three servers. ... I installed Ultrasound on ubiq-serv9, but when I have it show the FRS namespaces, it only shows sysvol (maybe why ClientApps isnt replicating). ... The log entry contains the following replacement strings:'CLIENTAPPS', ' "UBIQ-SERV10.company.local"', ' ...
    (microsoft.public.windows.server.general)
  • Re: Event ID: 13508
    ... Hmmm...either the Dfs link is OK, ... When I bounce the FRS Service I get 13508 for both sysvol and my dfs share, then shortly after I get 13509 but only for sysvol. ... Suddenly its stopped replicating. ... >> the 13508 error on both servers. ...
    (microsoft.public.win2000.active_directory)
  • Re: Sysvol not replicating, tryed everythiing, need help!
    ... restore for the SYSVOL on one DC, ... on the DC not replicating the SYSVOL check on the CO from which DC the ... Both servers are DNS servers and they point to themselves as the primary ...
    (microsoft.public.windows.server.active_directory)
  • Re: Event ID: 13508
    ... is a DNS problem why does it work for sysvol? ... > Definitely working on the sysvol folder just not on my dfs root. ... Suddenly its stopped replicating. ... >> both servers. ...
    (microsoft.public.win2000.active_directory)
  • Re: damn event ID 1202
    ... last section about your error code you can enable debugging of scecli ... OK message for each GPO if they are replicating correctly or "errors found" ... > Would it be better, to remove AD from these Server2k machines, and make ... > them members servers so they dont have to take all the GP Replications? ...
    (microsoft.public.win2000.group_policy)