none
Don't know how to fix replication issue!

    Question

  • Dear all,

    Current I have two DCs, one PDC (ssv01) and another BDC (ssv03). Both of them are Windows 2000 server SP4.
    I check and see have problem with BDC.
    - It is not able to share SYSVOL as long as NETLOGON

    Event log showed as the following:

    ------------------------------------------
    Event Type: Warning
    Event Source: NtFrs
    Event Category: None
    Event ID: 13565
    Date:  11/18/2009
    Time:  9:19:51 AM
    User:  N/A
    Computer: SSV03
    Description:
    File Replication Service is initializing the system volume with data from another domain controller. Computer SSV03 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
     
    To check for the SYSVOL share, at the command prompt, type:
    net share
     
    When File Replication Service completes the initialization process, the SYSVOL share will appear.
     
    The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.
    ------------------------------------------

    Event Type: Warning
    Event Source: NtFrs
    Event Category: None
    Event ID: 13508
    Date:  11/18/2009
    Time:  9:21:55 AM
    User:  N/A
    Computer: SSV03
    Description:
    The File Replication Service is having trouble enabling replication from \\ssv01.mydomain.com.vn to SSV03 for c:\winnt\sysvol\domain using the DNS name \\ssv01.mydomain.com.vn. FRS will keep retrying.
     Following are some of the reasons you would see this warning.
     
     [1] FRS can not correctly resolve the DNS name \\ssv01.mydomain.com.vn from this computer.
     [2] FRS is not running on \\ssv01.mydomain.com.vn.
     [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.
    Data:
    0000: d5 04 00 00               Õ...   


    ------------------------------------------

    I checked DNS, replication service are fine.
    Topology I use replicaiton monitor tool I also see that it is fine (and replicated successful between DCs).
    Could you please help me to fix the issue?

    Thanks,
    -Binh.


     
    Wednesday, November 18, 2009 9:02 AM

All replies

  • 1) On all Active Directory Servers
    1. Stop NETLOGON Service
    2. Stop File Replication Service (NTFRS)

    2)http://technet.microsoft.com/en-us/library/bb727056.aspx


    http://technetfaqs.wordpress.com
    Wednesday, November 18, 2009 9:20 AM
  • Hello Syed,

    Thank you for your info.
    I followed the document and checked.

    Big problem at here.

    There are no both accounts on my PDC (as the following log) while there are two account IWAM_SSV01B, IUSR_SSV01B (I think these accounts are on old DC) Maybe member has deleted confusionally.
    Maybe that is root cause of the issue.
    Now how I can fix it properly? Please help.

    ------------------from winlogon.log---------------
    Error 1332: No mapping between account names and security IDs was done.
      Cannot find IWAM_SSV01.
     Configure IUSR_SSV01.
    -----------------

    by the way, the following is log that I run the command on my workstation for checking....

    C:\Program Files\Support Tools>ntfrsutl version ssv01.mydomain.com.vn
    NtFrsApi Version Information
       NtFrsApi Major      : 0
       NtFrsApi Minor      : 0
       NtFrsApi Compiled on: Aug 17 2001 13:08:41
       NTFRS_TEST Disabled
    NtFrs Version Information
       NtFrs Major        : 0
       NtFrs Minor        : 0
       NtFrs Compiled on  : May  6 2003 14:15:26
       Latest changes:
       WIN2K-SP4
        + QFE #2 - force replication
    OS Version 5.0 (2195) -
    SP (4.0) SM: 0x0000  PT: 0x02
    Processor:  INTEL Level: 0x000f  Revision: 0x0403  Processor num/mask: 2/0000000
    3

    C:\Program Files\Support Tools>ntfrsutl version ssv03.mydomain.com.vn
    NtFrsApi Version Information
       NtFrsApi Major      : 0
       NtFrsApi Minor      : 0
       NtFrsApi Compiled on: Aug 17 2001 13:08:41
       NTFRS_TEST Disabled
    NtFrs Version Information
       NtFrs Major        : 0
       NtFrs Minor        : 0
       NtFrs Compiled on  : May  6 2003 14:15:26
       Latest changes:
       WIN2K-SP4
        + QFE #2 - force replication
    OS Version 5.0 (2195) -
    SP (4.0) SM: 0x0110  PT: 0x02
    Processor:  INTEL Level: 0x0006  Revision: 0x0b01  Processor num/mask: 1/0000000
    1

    C:\Program Files\Support Tools>



    Thanks,
    -Peace.

    Thursday, November 19, 2009 9:00 AM
  •  

    Hello,

     

    Thank you for your post here.

     

    Moreover, if the issue persists I'd like to know whether there is any router/firewall that may block the traffic for file sharing. There is known issue that a firewall that blocked higher level ports will break the FRS file replication.

     

    To narrow down the issue, you may take a network trace on the problematic DC to verify whether the traffic gets blocked by any firewall or devices. You can get the network monitor from the following link and install it on both servers.

     

    Download the NetMon3.3 from the following link:

    http://www.microsoft.com/downloads/details.aspx?FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en

     

    1) Install the network monitor on the server.

     

    2) Start the capture and try to reproduce the issue.

     

    2) Once the issue is reproduced, stop the captures and save the network trace files to verify whether the traffic gets blocked. You can also send the trace log to me at v-mileli@microsoft.com for further investigation.

     

    If you have any questions or concerns, please do not hesitate to let me know.

     

     

     

    Thursday, November 19, 2009 11:29 AM
    Moderator
  • Dear Miles,

    I've sent email to your email adress v-mileli@microsoft.com 
    My email address's  peacelo@live.com
    I don't know if my email reach you.
    You please check and get back to me. Thank you for your support.
    I look forward to hearing from you.

    Thanks,
    -Peace. 
    Monday, November 23, 2009 1:42 AM
  • Hi Peace,

    Lets first try to get the Ntfrs issue fixed. Since you mentioned that Sysvol and Netlogon are not shared on one of the DC, we can fix that easily provided AD Replication is working fine. Since Ntfrs Replication depends upon AD Replication and uses the same connection objects, it plays a vital role.

    You can check the AD Replication status from the PDC by running ''Repadmin /syncall /e /P". If it completes without errors then we can proceed further else would require to fix the AD Replication first.

    If AD Replication is fine then in order to fix the Ntfrs Replication we can change the Bur Flag Values to reinitiate the replication. To proceed with you need to first check the Policies under Sysvol. Check the Sysvol Folder on both the Domain Controllers and find out which Server is having all the Policies. Make sure to back them up to be on safer side. Once you have all Scripts and Policies at one place, you can proceed further.

    > Stop File Replication Service on both the Domain Controllers.
    > Go to PDC and make sure to put the Latest set of Policies and Scripts under Sysvol on it. All Policies and Scripts should be first copied to this Server under Sysvol because these will be replicated to the other Server.
    > Once done Traverse to Registry Location -- HKLM\System\CurrentControlSet\Services\Ntfrs\Parameters\Replica Set
          (There may be many GUIDs present in this location and you need to find the one for c:\windows\sysvol\domain. You can check the path on the right hand pane.)

    > The same GUID will also reflect under Cumulative Replica Set.
    > Open that GUID and you will find a Key called 'Bur Flag'.
    > Edit it and set the Value to 'D4' (hex)
    > Close the Registry Editor and Restart the File Replication Service on this Server
    > Once done, open Event Viewer and you would see an Event 13516 which indicates FRS is fine and both Netlogon and Sysvol are shared.

    Now lets move to other Domain Controller. Procedure would pretty much be the same. First of all empty the Policies and Scripts folder located under c:\windows\Sysvol\sysvol\domain name. This is because we have the Policies on other Server and they would be replicated to this Server.

    > File Replication Service is already stopped.
    > Traverse to the same Registry Location.
    > Match the GUIDs and make sure to edit the one for c:\windows\sysvol\domain
    this time under Bur Flags you need to put 'D2'
    > Close registry location
    > Restart the File Replication Service
    > Check Event Viewer and it will show you Event 13516 soon.
    > If it comes up then you can check the status of Sysvol and Netlogon. They would be shared and all the Policies and Scripts would come on this Server too.

    You can also refer to this Article for the same -- http://support.microsoft.com/kb/290762

    The above mentioned procedure is to be followed only if the AD Replication is working fine. If not revert back with the errors you get while running 'Repadmin /syncall /e /P'.

    Thanks,
    Nitin
    Monday, November 23, 2009 2:18 AM
  • Thank you for your info, Nitin.
    I have a question.
    When I run command on PDC >Repadmin /syncall /e: /P:

    It required username/password. Any problem? or how can I supply user/password?
    It alert "Password must be accompanied by user name."

    Thanks,
    -Peace.
    Monday, November 23, 2009 4:28 AM
  • Hi Peace,

    Are you logged in with Enterprise Admin ? Ideally it should not ask you for the Password.
    Are you getting any issues while manually forcing the Replication from Sites and Services ?
    Also try Replmon.

    Thanks,
    Nitin

    Monday, November 23, 2009 5:07 AM
  • Sure I used administrator account with Enterprise Admin right.
    It still show "Password must be accompanied by user name."

    I use Replmon for checking, everything look well. Replicated Schema, Configuration, and Domain successfully.

    Additional info.

    SSV01B is old DCs which is installed by previous admin person.
    This old DCs also installed exchange server. It is not demote correctly.
    So I also follow the guide at here to remove.
    http://support.microsoft.com/kb/216498

    I did all the steps carefully. Beside I also use ASDIEDIT to check and see some old objects are still available as below.

    Expand CN=System

    Expand CN=RpcServices =>CN=BrightStorEB@SSV01B

     

    Expand CN=System

    Expand CN=WinsockServices  => CN=ssv01b.mydomain.com.vn

    I don't know if I should remove them.
    Please help!


    Thanks,
    -Peace.

    Monday, November 23, 2009 6:33 AM
  • Hi Peace,

    Yes you can remove the Stale records of the Old Domain Controller and it wont harm anything. Make sure to manually force the Replication to other Servers.

    Are you getting the prompt for the Password from the other Server as well. Try downloading and installing the Repadmin Tool again an check from both the Servers. Else use Replmon to force the Replication and see if it shows some Errors.

    If the AD Replication is working fine, proceed with the steps i mentioned in previous post to fix the File Replication Issues.

    Thanks,
    Nitin

    Monday, November 23, 2009 6:41 AM
  • Hi Nitin,

    Yes, I will try to remove these old objects (CN=BrightStorEB@SSV01B and CN=ssv01b.mydomain.com.vn)

    any problems? if I also remove user and groups as the following (they are still available there):
    Group: Exchange Domain Servers and Exchange Enterprise Servers group.
    User: IUSR_SSV01B
    Current my system doesn't use Exchange Server.
    My DC is just Active Directory.

    Thank you for your support, Nitin.
    -Peace.
    Monday, November 23, 2009 7:00 AM
  • Hi Peace,

    Yes if you are no longer using Exchange Server then you should remove all such objects else you ay get issues later on when you will try to install Exchange again.

    Regarding the Replication issue as soon as you verify that it's fine, proceed with the FRS Troubleshooting.

    Thanks,
    Nitin

    Monday, November 23, 2009 7:38 AM
  • Hi,

     

    Thanks for the update.

     

    I have received the network trace and found some issue in it:

     

    You have the PDC: XX.XX.65.30 and BDC: XX.XX.65.9. In the network trace captured from BDC: XX.XX.65.9, the traffic between XX.XX.65.30 and XX.XX.65.9 is logged properly. However, on the PDC: XX.XX.65.30 there is not any traffic between itself and XX.XX.65.9 logged. I suspect that there is incorrect DNS records in the domain DNS zone for those DCs. For further investigation, please help to answer/collect the following questions/information:

     

    1.       On the both DC, can you PING the domain name and the hostname of both DCs? Does PING return the correct IP addresses?

    2.       To find out any potential issues on the DC, please help to collect the MPS report on the DC and send to me at v-mileli@microsoft.com (you can upload the report to Skydrive) for further investigation:

     

    Overview of the Microsoft Configuration Capture Utility (MPS_REPORTS)

    http://support.microsoft.com/kb/818742

     

    If you have any questions or concerns, please do not hesitate to let me know.

     

    Monday, November 23, 2009 10:18 AM
    Moderator

  • Dear Miles,

    Thank you very much for your support.

    Yes, you're right. My PDC is xx.xx.65.30 and BDC is xx.xx.65.9

    #2. I am sorry, I don't get report. Because My DCs are running on OS Windows 2000 server. So there is no PowerShell for it.

    #1. I am sure it is fine. DNS is fine.

    ----------Ping on SSV01:-------------------

    Microsoft Windows 2000 [Version 5.00.2195]
    (C) Copyright 1985-2000 Microsoft Corp.

    C:\Documents and Settings\Administrator.mydomainVN>ping mydomain.com.vn

    Pinging mydomain.com.vn [xx.xxx.65.30] with 32 bytes of data:

    Reply from xx.xxx.65.30: bytes=32 time<10ms TTL=128
    Reply from xx.xxx.65.30: bytes=32 time<10ms TTL=128
    Reply from xx.xxx.65.30: bytes=32 time<10ms TTL=128
    Reply from xx.xxx.65.30: bytes=32 time<10ms TTL=128

    Ping statistics for xx.xxx.65.30:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum =  0ms, Average =  0ms

    C:\Documents and Settings\Administrator.mydomainVN>ping ssv03.mydomain.com.vn

    Pinging ssv03.mydomain.com.vn [xx.xxx.65.9] with 32 bytes of data:

    Reply from xx.xxx.65.9: bytes=32 time<10ms TTL=128
    Reply from xx.xxx.65.9: bytes=32 time<10ms TTL=128
    Reply from xx.xxx.65.9: bytes=32 time<10ms TTL=128
    Reply from xx.xxx.65.9: bytes=32 time<10ms TTL=128

    Ping statistics for xx.xxx.65.9:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum =  0ms, Average =  0ms

    C:\Documents and Settings\Administrator.mydomainVN>ping ssv03

    Pinging ssv03.mydomain.com.vn [xx.xxx.65.9] with 32 bytes of data:

    Reply from xx.xxx.65.9: bytes=32 time<10ms TTL=128
    Reply from xx.xxx.65.9: bytes=32 time<10ms TTL=128
    Reply from xx.xxx.65.9: bytes=32 time<10ms TTL=128
    Reply from xx.xxx.65.9: bytes=32 time<10ms TTL=128

    Ping statistics for xx.xxx.65.9:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum =  0ms, Average =  0ms

    C:\Documents and Settings\Administrator.mydomainVN>

    ------------------Ping on SSV03---------------
    Microsoft Windows 2000 [Version 5.00.2195]
    (C) Copyright 1985-2000 Microsoft Corp.

    C:\Documents and Settings\Administrator.mydomainVN>ping mydomain.com.vn

    Pinging mydomain.com.vn [xx.xxx.65.30] with 32 bytes of data:

    Reply from xx.xxx.65.30: bytes=32 time=9ms TTL=128
    Reply from xx.xxx.65.30: bytes=32 time<10ms TTL=128
    Reply from xx.xxx.65.30: bytes=32 time<10ms TTL=128
    Reply from xx.xxx.65.30: bytes=32 time<10ms TTL=128

    Ping statistics for xx.xxx.65.30:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum =  9ms, Average =  2ms

    C:\Documents and Settings\Administrator.mydomainVN>ping ssv01.mydomain.com.vn

    Pinging ssv01.mydomain.com.vn [xx.xxx.65.30] with 32 bytes of data:

    Reply from xx.xxx.65.30: bytes=32 time=10ms TTL=128
    Reply from xx.xxx.65.30: bytes=32 time<10ms TTL=128
    Reply from xx.xxx.65.30: bytes=32 time<10ms TTL=128
    Reply from xx.xxx.65.30: bytes=32 time<10ms TTL=128

    Ping statistics for xx.xxx.65.30:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum =  10ms, Average =  2ms

    C:\Documents and Settings\Administrator.mydomainVN>ping ssv01

    Pinging ssv01.mydomain.com.vn [xx.xxx.65.30] with 32 bytes of data:

    Reply from xx.xxx.65.30: bytes=32 time=9ms TTL=128
    Reply from xx.xxx.65.30: bytes=32 time<10ms TTL=128
    Reply from xx.xxx.65.30: bytes=32 time<10ms TTL=128
    Reply from xx.xxx.65.30: bytes=32 time<10ms TTL=128

    Ping statistics for xx.xxx.65.30:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum =  9ms, Average =  2ms

    C:\Documents and Settings\Administrator.mydomainVN>

    ----------------------------------

    Beside I check some commands. You can refer it as the following.


    =================on SSV01===============================

    Microsoft Windows 2000 [Version 5.00.2195]
    (C) Copyright 1985-2000 Microsoft Corp.

    C:\Documents and Settings\Administrator.mydomainVN>repadmin /syncall ssv01.mydomain.com.vn dc=mydomain,dc=com,dc=vn
    CALLBACK MESSAGE: The following replication is in progress:
        From: 9d19b2c8-220b-47e6-846e-3e5d6b3311dc._msdcs.mydomain.com.vn
        To  : 2534442d-e3c4-49f9-9512-6b5e6ec5cc08._msdcs.mydomain.com.vn
    CALLBACK MESSAGE: The following replication completed successfully:
        From: 9d19b2c8-220b-47e6-846e-3e5d6b3311dc._msdcs.mydomain.com.vn
        To  : 2534442d-e3c4-49f9-9512-6b5e6ec5cc08._msdcs.mydomain.com.vn
    CALLBACK MESSAGE: SyncAll Finished.

    SyncAll terminated with no errors.

    C:\Documents and Settings\Administrator.mydomainVN>repadmin /syncall ssv03.ajin
    omoto.com.vn dc=mydomain,dc=com,dc=vn
    CALLBACK MESSAGE: The following replication is in progress:
        From: 2534442d-e3c4-49f9-9512-6b5e6ec5cc08._msdcs.mydomain.com.vn
        To  : 9d19b2c8-220b-47e6-846e-3e5d6b3311dc._msdcs.mydomain.com.vn
    CALLBACK MESSAGE: The following replication completed successfully:
        From: 2534442d-e3c4-49f9-9512-6b5e6ec5cc08._msdcs.mydomain.com.vn
        To  : 9d19b2c8-220b-47e6-846e-3e5d6b3311dc._msdcs.mydomain.com.vn
    CALLBACK MESSAGE: SyncAll Finished.

    SyncAll terminated with no errors.

    C:\Documents and Settings\Administrator.mydomainVN>


    =================on SSV03===============================

    Microsoft Windows 2000 [Version 5.00.2195]
    (C) Copyright 1985-2000 Microsoft Corp.

    C:\Documents and Settings\Administrator.mydomainVN>repadmin /syncall ssv01.mydomain.com.vn dc=mydomain,dc=com,dc=vn

    CALLBACK MESSAGE: The following replication is in progress:
        From: 9d19b2c8-220b-47e6-846e-3e5d6b3311dc._msdcs.mydomain.com.vn
        To  : 2534442d-e3c4-49f9-9512-6b5e6ec5cc08._msdcs.mydomain.com.vn
    CALLBACK MESSAGE: The following replication completed successfully:
        From: 9d19b2c8-220b-47e6-846e-3e5d6b3311dc._msdcs.mydomain.com.vn
        To  : 2534442d-e3c4-49f9-9512-6b5e6ec5cc08._msdcs.mydomain.com.vn
    CALLBACK MESSAGE: SyncAll Finished.

    SyncAll terminated with no errors.

    C:\Documents and Settings\Administrator.mydomainVN>

    =============================================================



    Microsoft Windows 2000 [Version 5.00.2195]
    (C) Copyright 1985-2000 Microsoft Corp.

    C:\Documents and Settings\Administrator.mydomainVN>repadmin /showreps ssv01.mydomain.com.vn
    Default-First-Site-Name\SSV01
    DSA Options : IS_GC
    objectGuid  : 2534442d-e3c4-49f9-9512-6b5e6ec5cc08
    invocationID: d017b738-f7bd-49dd-ae18-c72b2caa7914

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

    CN=Schema,CN=Configuration,DC=mydomain,DC=com,DC=vn
        Default-First-Site-Name\SSV03 via RPC
            objectGuid: 9d19b2c8-220b-47e6-846e-3e5d6b3311dc
            Last attempt @ 2009-11-23 14:58.28 was successful.

    CN=Configuration,DC=mydomain,DC=com,DC=vn
        Default-First-Site-Name\SSV03 via RPC
            objectGuid: 9d19b2c8-220b-47e6-846e-3e5d6b3311dc
            Last attempt @ 2009-11-23 14:58.28 was successful.

    DC=mydomain,DC=com,DC=vn
        Default-First-Site-Name\SSV03 via RPC
            objectGuid: 9d19b2c8-220b-47e6-846e-3e5d6b3311dc
            Last attempt @ 2009-11-23 15:06.08 was successful.

    ==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

    CN=Schema,CN=Configuration,DC=mydomain,DC=com,DC=vn
        Default-First-Site-Name\SSV03 via RPC
            objectGuid: 9d19b2c8-220b-47e6-846e-3e5d6b3311dc

    CN=Configuration,DC=mydomain,DC=com,DC=vn
        Default-First-Site-Name\SSV03 via RPC
            objectGuid: 9d19b2c8-220b-47e6-846e-3e5d6b3311dc

    DC=mydomain,DC=com,DC=vn
        Default-First-Site-Name\SSV03 via RPC
            objectGuid: 9d19b2c8-220b-47e6-846e-3e5d6b3311dc

    C:\Documents and Settings\Administrator.mydomainVN>

     

    ==================================================

    Microsoft Windows 2000 [Version 5.00.2195]
    (C) Copyright 1985-2000 Microsoft Corp.


    C:\Documents and Settings\Administrator.mydomainVN>repadmin /showreps ssv03.mydomain.com.vn
    Default-First-Site-Name\SSV03
    DSA Options : IS_GC
    objectGuid  : 9d19b2c8-220b-47e6-846e-3e5d6b3311dc
    invocationID: f9fb6752-e39c-477b-a655-655381a075c0

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

    CN=Schema,CN=Configuration,DC=mydomain,DC=com,DC=vn
        Default-First-Site-Name\SSV01 via RPC
            objectGuid: 2534442d-e3c4-49f9-9512-6b5e6ec5cc08
            Last attempt @ 2009-11-23 14:47.10 was successful.

    CN=Configuration,DC=mydomain,DC=com,DC=vn
        Default-First-Site-Name\SSV01 via RPC
            objectGuid: 2534442d-e3c4-49f9-9512-6b5e6ec5cc08
            Last attempt @ 2009-11-23 15:08.55 was successful.

    DC=mydomain,DC=com,DC=vn
        Default-First-Site-Name\SSV01 via RPC
            objectGuid: 2534442d-e3c4-49f9-9512-6b5e6ec5cc08
            Last attempt @ 2009-11-23 15:11.26 was successful.

    ==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

    CN=Schema,CN=Configuration,DC=mydomain,DC=com,DC=vn
        Default-First-Site-Name\SSV01 via RPC
            objectGuid: 2534442d-e3c4-49f9-9512-6b5e6ec5cc08

    CN=Configuration,DC=mydomain,DC=com,DC=vn
        Default-First-Site-Name\SSV01 via RPC
            objectGuid: 2534442d-e3c4-49f9-9512-6b5e6ec5cc08

    DC=mydomain,DC=com,DC=vn
        Default-First-Site-Name\SSV01 via RPC
            objectGuid: 2534442d-e3c4-49f9-9512-6b5e6ec5cc08

    C:\Documents and Settings\Administrator.mydomainVN>

     

     

     

    Tuesday, November 24, 2009 10:33 AM
  • Hi Peace,

    Looking at the results that you posted recently, Replication seems to be working fine. Did you get chance to implement the steps for FRS Troubleshooting yet ?

    Thanks,
    Nitin
    Wednesday, November 25, 2009 1:38 AM
  • Hi Nitin,

    Not yet. In order to fix the following issues I need to edit registry so I am going to perform it at weekend.

    Thank you for your support.

    - Peace.
    ---------------------------------
    Event Type: Warning
    Event Source: NtFrs
    Event Category: None
    Event ID: 13565
    Date:  11/18/2009
    Time:  9:19:51 AM
    User:  N/A
    Computer: SSV03
    Description:
    File Replication Service is initializing the system volume with data from another domain controller. Computer SSV03 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
     
    To check for the SYSVOL share, at the command prompt, type:
    net share
     
    When File Replication Service completes the initialization process, the SYSVOL share will appear.
     
    The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.
    ------------------------------------------

    Event Type: Warning
    Event Source: NtFrs
    Event Category: None
    Event ID: 13508
    Date:  11/18/2009
    Time:  9:21:55 AM
    User:  N/A
    Computer: SSV03
    Description:
    The File Replication Service is having trouble enabling replication from \\ssv01.mydomain.com.vn to SSV03 for c:\winnt\sysvol\domain using the DNS name \\ssv01.mydomain.com.vn. FRS will keep retrying.
     Following are some of the reasons you would see this warning.
     
     [1] FRS can not correctly resolve the DNS name \\ssv01.mydomain.com.vn from this computer.
     [2] FRS is not running on \\ssv01.mydomain.com.vn.
     [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.
    Data:
    0000: d5 04 00 00               Õ...   

    Wednesday, November 25, 2009 2:47 AM
  • Hi Peace,

    If you are getting Even 13508 on SSV03 than problem is with the Server it is trying to take Replication from. In your case it would be SSV01. That Server might be in a Journal Wrap Error or some other Database Coruption.
    Please make sure to follow the steps deligiently and don't forget to backup all the Policies and Scripts.

    Awaiting Results.

    Thanks,
    Nitin
    Wednesday, November 25, 2009 2:54 AM
  • Hi Nitin,

    Yes, you're right absolutely. On PDC (ssv01) get error Event ID: 13568 as the following.
    Thank you very much for your support.

    -Peace.


    Event Type: Error
    Event Source: NtFrs
    Event Category: None
    Event ID: 13568
    Date:  24/11/2009
    Time:  4:41:01 PM
    User:  N/A
    Computer: SSV01
    Description:
    The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
     
     Replica set name is    : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
     Replica root path is   : "c:\winnt\sysvol\domain"
     Replica root volume is : "\\.\C:"
     A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found.  This can occur because of one of the following reasons.
     
     [1] Volume "\\.\C:" has been formatted.
     [2] The NTFS USN journal on volume "\\.\C:" has been deleted.
     [3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
     [4] File Replication Service was not running on this computer for a long time.
     [5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
     Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
     [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
     [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
     
    WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
     
    To change this registry parameter, run regedit.
     
    Click on Start, Run and type regedit.
     
    Expand HKEY_LOCAL_MACHINE.
    Click down the key path:
       "System\CurrentControlSet\Services\NtFrs\Parameters"
    Double click on the value name
       "Enable Journal Wrap Automatic Restore"
    and update the value.
     
    If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.

    Wednesday, November 25, 2009 3:24 AM
  • Hi Peace,

    Allright so now when we are sure of this issue lets go ahead with the troubleshooting. Be extremely carefull with the Registry Entries. You have to edit the BurFlag under the GUID thato corrosponds to the c:\windows\sysvol\domain. This is because if we use DFS we see a lot other GUID's at the same location. However if you are not using DFS then you will see only one GUID both under 'Cumulative Replica Set' and 'Replica Set'.

    And regarding the Journal Wrap Error that you are getting, we can increase the Journal Size from the Registry so that he issue dosen't comes up again in future. Although there are a lot of reasons why this Error comes up but atleast we can eradicate the possiblity on one of them :)

    Revert back if you have any questions in any step.

    Thanks,
    Nitin

    Wednesday, November 25, 2009 4:23 AM
  • Hi Nitin,

    Thank you very much for your support.
    Currently the repliation is fixed. It's fine. BDC can authenticate well.
    What I do to be as the following.

    on both DCs > net stop ntfrs
    And then adjust Burflag to D4 on PDC and Burflag on BDC to D2 as the following path.


    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Replica Sets\GUID

    Right-click BurFlags, and then click Modify.

    Type D4 in the Value Data field (HexaDecimal), and then click OK

    after that on both DCs > net start ntfrs

    -------------
    Beside I get error at the following currently.

    Becuase I plan to migrate my DCs (Win2k) to Windows 2008.
    So I also run commadn adprep /forestprep on PDC but it still show error as below.

    I appreciate your help.


    Adprep was unable to extend the schema.

    [Status/Consequence]

    There is a schema conflict with Exchange 2000. The schema is not upgraded.

    [User Action]

    The schema conflict must be resolved before running adprep. Resolve the schema c

    onflict, allow the change to replicate between all replication partners, and the

    n run Adprep. For information on resolving the conflict, see Microsoft Knowledge

     Base article Q325379.

     

    Saturday, November 28, 2009 8:43 AM
  • Hi Peace,

    Sory for the delay in reply. I had a word with a Exchange guy regarding this. If i am not wron you only have 2 DC's witn Windows 2000 installed on them. Where is the Exchange Server, is it also on the DC ?

    I came across this Microsoft Article which says --

    Scenario 1: Exchange 2000 schema changes are added after you run the Windows Server 2003 adprep /forestprep command

    If Exchange 2000 schema changes will be introduced to your Windows 2000 forest after the Windows Server 2003 adprep /forestprep command is run, no cleanup is required. Go to the "Overview: Upgrading Windows 2000 domain controllers to Windows Server 2003" section.

    Scenario 2: Exchange 2000 schema changes will be installed before the Windows Server 2003 adprep /forestprep command

    If Exchange 2000 schema changes have already been installed but you have NOT run the Windows Server 2003 adprep /forestprep command.

    You can go through these Articles as well, hope these helps you --

    http://support.microsoft.com/default.aspx/kb/325379
    http://support.microsoft.com/kb/324392

    Revert back if you have any queries.

    Thanks,
    Nitin
    Monday, November 30, 2009 1:49 AM
  • Hi Nitin,

    I was facing the same kind issue which peace was facing .. .

    I tried to look into my PDC for the BUR Flag Settings .. but to my amazement there was no such Registry key in PDC but in ADC it existed wat cud be the issue.

    Rgds

    Anuragg
    Cheers Anuragg
    Wednesday, February 17, 2010 7:06 AM
  • Hello Anurag,

                  Can you please open the new thread and let us know your problem and Please donot forget to put the logs

    Repadmin /showreps and Repadmin /syncall /e /P



    Thanks
    Syed
    http://technetfaqs.wordpress.com
    Wednesday, February 17, 2010 8:03 AM