Solved

FRS Replication Problem: Event ID 13508 w/o 13509

Posted on 2008-06-25
14
1,048 Views
Last Modified: 2012-05-05
Event Type:      Warning
Event Source:      NtFrs
Event Category:      None
Event ID:      13508
Date:            6/25/2008
Time:            12:39:12 AM
User:            N/A
Computer:      ATCSERVERMIA
Description:
The File Replication Service is having trouble enabling replication from FLTSERVER1POM to ATCSERVERMIA for d:\fileshares using the DNS name fltserver1pom.FreightlinerSF.com. FRS will keep retrying.
 Following are some of the reasons you would see this warning.
 
 [1] FRS can not correctly resolve the DNS name fltserver1pom.FreightlinerSF.com from this computer.
 [2] FRS is not running on fltserver1pom.FreightlinerSF.com.
 [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
 
 This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

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

Reasons 1 and 2 above are not an issue, but I don't know how to check on 3.  Using repadmin /showreps come back with successful results on all tests:
C:\Documents and Settings\Administrator.FREIGHTLINERSF>repadmin /showreps
Miami\ATCSERVERMIA
DC Options: IS_GC
Site Options: (none)
DC object GUID: 3b20b6a9-c3d8-46c4-bf68-c9a4e07e65ab
DC invocationID: bc4f7892-44b9-4726-a367-e0dc2243af5b

==== INBOUND NEIGHBORS ======================================

DC=FreightlinerSF,DC=com
    Pompano\FLTSERVER1POM via RPC
        DC object GUID: 57aac232-69d0-4f8e-8098-97d9c3d04ba6
        Last attempt @ 2008-06-25 11:57:14 was successful.
    Riviera\ATCSERVERWPB via RPC
        DC object GUID: 4791dc94-0d7b-4d7a-b22c-1f767990df94
        Last attempt @ 2008-06-25 12:57:14 was successful.

CN=Configuration,DC=FreightlinerSF,DC=com
    Pompano\FLTSERVER1POM via RPC
        DC object GUID: 57aac232-69d0-4f8e-8098-97d9c3d04ba6
        Last attempt @ 2008-06-25 11:57:14 was successful.
    Riviera\ATCSERVERWPB via RPC
        DC object GUID: 4791dc94-0d7b-4d7a-b22c-1f767990df94
        Last attempt @ 2008-06-25 12:57:14 was successful.

CN=Schema,CN=Configuration,DC=FreightlinerSF,DC=com
    Pompano\FLTSERVER1POM via RPC
        DC object GUID: 57aac232-69d0-4f8e-8098-97d9c3d04ba6
        Last attempt @ 2008-06-25 11:57:14 was successful.
    Riviera\ATCSERVERWPB via RPC
        DC object GUID: 4791dc94-0d7b-4d7a-b22c-1f767990df94
        Last attempt @ 2008-06-25 12:57:14 was successful.

DC=DomainDnsZones,DC=FreightlinerSF,DC=com
    Pompano\FLTSERVER1POM via RPC
        DC object GUID: 57aac232-69d0-4f8e-8098-97d9c3d04ba6
        Last attempt @ 2008-06-25 11:57:14 was successful.
    Riviera\ATCSERVERWPB via RPC
        DC object GUID: 4791dc94-0d7b-4d7a-b22c-1f767990df94
        Last attempt @ 2008-06-25 12:57:14 was successful.

DC=ForestDnsZones,DC=FreightlinerSF,DC=com
    Pompano\FLTSERVER1POM via RPC
        DC object GUID: 57aac232-69d0-4f8e-8098-97d9c3d04ba6
        Last attempt @ 2008-06-25 11:57:14 was successful.
    Riviera\ATCSERVERWPB via RPC
        DC object GUID: 4791dc94-0d7b-4d7a-b22c-1f767990df94
        Last attempt @ 2008-06-25 12:57:14 was successful.

The following is the result of ntfrstul, but like the previous poster of the related message, I don't know if this means success:
C:\Documents and Settings\Administrator.FREIGHTLINERSF>ntfrsutl version fltserver1pom.freightlinersf.com
NtFrsApi Version Information
   NtFrsApi Major      : 0
   NtFrsApi Minor      : 0
   NtFrsApi Compiled on: Feb 16 2007 20:01:19
NtFrs Version Information
   NtFrs Major        : 0
   NtFrs Minor        : 0
   NtFrs Compiled on  : Feb 16 2007 20:01:30
   Latest changes:
   Install Override fix
OS Version 5.2 (3790) -
SP (2.0) SM: 0x0110  PT: 0x02
Processor:  INTEL Level: 0x000f  Revision: 0x0209  Processor num/mask: 4/0000000f

I have also downloaded and run FRSDIAG.exe from Microsoft's site and have a whole list of the tests it ran, but am obviously unable to make sense of them.  There were some failure among them.  Would it do any good to post that .cab file?  I was hoping to avoid calling Microsoft and having them ding us for the charge.
0
Comment
Question by:fabiouness
  • 7
  • 4
  • 3
14 Comments
 
LVL 24

Expert Comment

by:ryansoto
ID: 21868202
How do you know that DNS isnt an issue?
To rule that out I would run a dcdiag and a netdiag and see what errors return if any.
0
 

Author Comment

by:fabiouness
ID: 21869638
Well, I say DNS isn't an issue only in reference to being able to ping the FQDN of the replicating partner with no issue, and vice versa.  Both servers can browse each other and all workstations can access each server's shares.  DCdiag on the problem server resulted in passed tests for all except frsevent.  As for netdiag on the problem server, one warning after NetBT name test (which still passed):  At least one of the Workstation Service, Messenger Service, WINS names is missing.  WINS test skipped as no WINS server configured for that interface.  DNS test passed but it said that all DNS entries for DC are registered on that particular server and that other DCs also have some of the names registered.  It repeated this exact statement for the PDC replicating partner as well.  
0
 
LVL 24

Expert Comment

by:ryansoto
ID: 21870516
OK that doesnt look to be the issue -
Can you run replmon and see what happens
http://www.mcmcse.com/microsoft/guides/replmon.shtml

0
 

Author Comment

by:fabiouness
ID: 21875965
Replmon showed no replication errors, but it appears that that program only checks for replication of sysvol, not DFS volumes?  
0
 
LVL 24

Expert Comment

by:ryansoto
ID: 21876473
0
 
LVL 24

Expert Comment

by:ryansoto
ID: 21876485
0
 

Author Comment

by:fabiouness
ID: 21877977
The DNS settings were already set that way.  I will read through these links.  Thanks.

0
Complete Microsoft Windows PC® & Mac Backup

Backup and recovery solutions to protect all your PCs & Mac– on-premises or in remote locations. Acronis backs up entire PC or Mac with patented reliable disk imaging technology and you will be able to restore workstations to a new, dissimilar hardware in minutes.

 
LVL 38

Expert Comment

by:ChiefIT
ID: 21896214
There is a link that may be right up your alley, on this page: (troubleshooting 13508 without 13509)
http://technet.microsoft.com/en-us/library/bb727056.aspx#EMAA

I was thinking a journal wrap. But, check this out first.
0
 

Author Comment

by:fabiouness
ID: 21903412
Looks like I may have to try that BURFLAGS registry tweak spelled out in a link from one of these articles, however, I figured I'd post the results of running ntfrsutl sets on the server that can't get the proper replication of the fileshares set.  I only cut out the portion that related to this set, not the sysvol info.  Can anyone tell me if this looks correct?

Replica: FILESHARES (1e066f65-a720-4a6d-97d6b8f84c7fc169)
      ComputerName : ATCSERVERMIA
      Member      : {0366E5F0-267B-4ADB-9DA9-EA11D971AA87} (bb1096ee-09df-4d8f-b76de671b53312f1)
      Name        : FILESHARES (bb1096ee-09df-4d8f-b76de671b53312f1)
      RootGuid    : 4d386317-8c83-48ef-b70cd51617cedb09
      OrigGuid    : 8223643e-3a84-4b33-9cab0ab5960747a6
      Reference     : 2
      CnfFlags      : 00000015 Flags [Multimaster Primary Online ]
      RepSetObjFlags: 00000000 Flags [<Flags Clear>]
      SetType       : 3
      Consistent    : 1
      IsOpen        : 1
      IsJournaling  : 1
      IsAccepting   : 1
      IsSeeding     : 0
      NeedsUpdate   : 0
      ServiceState  : 3  (ACTIVE)
      FStatus       : FrsErrorSuccess
      Number        : 10
      Root          : d:\fileshares
      Stage         : d:\frs-staging
      Volume        : \\.\D:
      FileFilter    : *.bak,*.tmp,~*
      DirFilter     :
      Expires       : 00000000 00000000
      InLogRetry    : 0
      InLogSeq      : 0
      ApiState      : 0
      ApiStatus     : 0
      ApiHack       : 0
      OutLogSeq     : 2
      OutLogJLx     : 1
      OutLogJTx     : -1
      OutLogMax     : 0
      OutLogMin     : 2
      OutLogState   : 5
      OutLogVV's    : 0
      OutLogClean   : 0
      PreinstallFID : 002e0000 00002b7e
      InLogCommit   : 00000000 00ccd438
      JrnlStart     : 00000000 00000000
      JrnlEnd       : 00000000 00c904b0
      LastUsn       : 00000000 00ccd438
      Replica Version Vector
         VvEntry: 8223643e-3a84-4b33-9cab0ab5960747a6 = 01c8cf3f 93353a4d
      Outlog Version Vector
         VvEntry: 8223643e-3a84-4b33-9cab0ab5960747a6 = 01c8cf3f 93353a4d

      Cxtion: {9FFA6AF3-7155-4D14-B4B9-417C88FA981C} (c17efd56-bc43-4aae-b43dd4f72c200acb)
         Partner      : FLTSERVER1POM (c630cf80-207e-4a76-8c5b5385ba91770f)
         PartDnsName  : fltserver1pom.FreightlinerSF.com
         PartSrvName  : FREIGHTLINERSF\FLTSERVER1POM$
         PartPrincName: FREIGHTLINERSF\FLTSERVER1POM$
         PartSid      : S-1-5-21-1275210071-527237240-682003330-1003
         OrigGuid     : 00000000-0000-0000-0000000000000000
         State        : 1
         Flags        : 00000002 Flags [SchedOff ]
         CxtionOptions: 70000000 Flags [0x70000000 ]
         Inbound      : TRUE
         JrnlCxtion   : FALSE
         PartnerAuth  : 0
         TermCoSn     : 0
         JoinCmd      : 0x00000000
         CoCount      : 0
         CommQueue    : 1
         CoPQ         : 00000000
         UnjoinTrigger: 0
         UnjoinReset  : 0
         Comm Packets : 0
         PartnerMajor : 0
         PartnerMinor : 0
         JoinGuid     : 00000000-0000-0000-0000000000000000
         LastJoinTime : Time???
         LastSndStatus: ERROR_SUCCESS
         NoFailedSnds : 0
         Schedule
            Day 1: 000fffffffffffffffffffff
            Day 2: ffffffff0000000000000000
            Day 3: 000fffff0000000000000000
            Day 4: 000fffff0000000000000000
            Day 5: 000fffff0000000000000000
            Day 6: 000fffff0000000000000000
            Day 7: 000fffff0000000000000000

      Cxtion: <Jrnl Cxtion> (86d7f9a2-c33a-4bad-b56985fd1bc4764d)
         Partner      : <Jrnl Cxtion> (86d7f9a2-c33a-4bad-b56985fd1bc4764d)
         PartDnsName  : <Jrnl Cxtion>
         PartSrvName  : <Jrnl Cxtion>
         PartPrincName: <Jrnl Cxtion>
         PartSid      : <Jrnl Cxtion>
         OrigGuid     : 00000000-0000-0000-0000000000000000
         State        : 7
         Flags        : 000000c0 Flags [JoinGuidValid UnJoinGuidValid ]
         CxtionOptions: 00000000 Flags [<Flags Clear>]
         Inbound      : TRUE
         JrnlCxtion   : TRUE
         PartnerAuth  : 1
         TermCoSn     : 0
         JoinCmd      : 0x00000000
         CoCount      : 0
         CommQueue    : 0
         CoPQ         : 00000000
         UnjoinTrigger: 0
         UnjoinReset  : 0
         Comm Packets : 0
         PartnerMajor : 0
         PartnerMinor : 0
         JoinGuid     : ef3e2b95-763f-33d9-1b3707416e5383ae
         LastJoinTime :

DELETED REPLICA SETS
0
 
LVL 38

Expert Comment

by:ChiefIT
ID: 21923454
I really never have been able to interpolate that.

Working with Journal Wrap Auto Restore resets the NTFRS shares. So you loose the data you saved.

Burflags is a less agressive approach to fixing this. If it's the only DC in the network then I would go ahead with Burflags set to D4. If there is more than one DC you may wnat to set Burflags do D2.

This article will guide you through it:
http://support.microsoft.com/kb/290762/en-us
0
 

Author Comment

by:fabiouness
ID: 21927581
The PDC (fltserver1pom) is the one holding the "master" directory that I want replicated to the other servers.  So you're saying to just set the two other DCs Burflags to D2 and not to mess with the PDC?  Or do I need to also set the PDC's Burflags to D4?  I don't want to mess up the replication of SYSVOL since that's working fine.
0
 
LVL 38

Expert Comment

by:ChiefIT
ID: 21933489
Set the two other DCs Burflags to D2 and not to mess with the PDC

D4 is primarily used for single DCs.

Using "Enable Journal Wrap Automatic Restore" will make NTFRS reinitialize all NTFRS shares and delete all contents in those shares (a very aggressive approach). This includes the Sysvol and Netlogon share. This is why we are choosing the Burflag method.

Regardless of the method, prior fixing your shares, you might want a True Image Backup to resort to in case of any issues. I don't anticipate any, but you never know. You know how Murphy does her Law.

0
 

Author Comment

by:fabiouness
ID: 21938705
Well, the Burflags approach didn't work either.  It reset the server's association to the replica sets, but later that night I got the same old 13508 error I was getting before.  I think the next step is to delete the replica sets altogether and start over.  Is this wise?  Will this affect SYSVOL?  I've read where you have to delete the items from both ADUC and the registry.  
0
 

Accepted Solution

by:
fabiouness earned 0 total points
ID: 21946748
Finally got it working!  Went ahead and deleted the root from the DFS console and the root folder under DFS Volumes under FRS in ADUC on all servers (with FRS service stopped).  Rebooted all servers and then deleted all subfolders under the root's corresponding folder in Explorer on all servers.  Recreated the DFS root on the PDC and the link to the one folder share I had been wanting to replicate among all servers.  This time, instead of replicating the root, I just set it to replicate the link under the root.  I also used a full mesh topology among the three servers where before I had set up a custom replication with the PDC "pushing" the content to the other two DCs only.  Lo and behold, I finally got a 13509 Event ID after the 13508 on all servers and the content is identical in the desired shared folder!  I'm thinking perhaps there were some "remnants" of the old replication information still in AD, or maybe it was merely the type of topology I was using for replication, but whatever the case, it's working!  Thanks to all for your help!
0

Featured Post

Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

Join & Write a Comment

Suggested Solutions

Introduction You may have a need to setup a group of users to allow local administrative access on workstations.  In a domain environment this can easily be achieved with Restricted Groups and Group Policies. This article will demonstrate how to…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now