5002 ошибка dfsr репликация dfs

Table of Contents

  • Event Details
  • Summary
  • Causes
  • Resolutions
    • Test basic network connectivity
    • Check Firewall settings
    • Install the latest updates
  • Verification
    • See Also

Event Details

Product: Windows Operating System
Event ID: 5002
Source: DFSR
Version: Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 R2
Message: Service encountered an error communicating with partner for Replication Group

Summary

DFS Replication encountered an error while communicating with a replication partner during replication. DFS Replication will retry replication.

Causes

An unhealthy state of this monitor is caused by communication errors during replication. Communication errors can occur for the following reasons:

  • General network connectivity issues
  • DNS errors
  • Firewall settings
  • Lack of software updates on replication partners

Resolutions

Test basic network connectivity

To test network connectivity with the affected server, use the following procedure:

  1. Open a command prompt window and then use the ping command to check basic network connectivity.

    If the ping command fails, it is likely that the server is not running, or has network problems that require local access to resolve. If ping is blocked in your network environment, skip this step.
  2. If the ping command is successful, test the server’s registration in DNS by using the
    nslookup command.
    If the nslookup command fails, there is a problem with DNS. Check the DNS server health or contact the DNS server administrator.
  3. If the nslookup command succeeds, DNS is working properly.

Note: For more information about troubleshooting network issues, see
article 325487 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?linkid=46059).

Check Firewall settings

If a firewall has been configured between replication partners, ensure that it is not blocking RPC communication. DFS Replication depends on RPC for communication. DFS Replication uses the RPC Endpoint Mapper (port 135) and a randomly assigned dynamic port
in the range of 49152 through 65535 for Windows Server 2008 R2 and Windows Server 2008, or in the range of 1025 through 5000 for Windows Server 2003 R2.

You can use the Dfsrdiag command-line tool to specify a static port instead of the dynamic port. For more information about how to specify the RPC Endpoint Mapper, see
article 154596 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=73991). For more information about dynamic port usage in Windows Server 2008, see
article 929851 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=187092).

Install the latest updates

Install the latest service pack and updates on all members of the replication group.

Verification

To manually confirm that replication is healthy, run a propagation test on the affected folder by using DFS Management or the following commands where <ReplicationGroup>
is the name of the replication group and <ReplicatedFolder>
is the name of the replicated folder:

dfsrdiag propagationtest /rgname:»<ReplicationGroup>» /rfname:»<ReplicatedFolder>» /testfilename:DFS-RTestFile.xml

dfsrdiag propagationreport /rgname:»<ReplicationGroup>» /rfname:»<ReplicatedFolder>» /testfilename:DFS-RTestFile.xml /reportfilename:c:\DFS-R_Report.xml

See Also

  • Knowledge Base article 832017, «Service overview and network port requirements for the Windows Server system» (http://go.microsoft.com/fwlink/?LinkId=65336)
  • Current Hotfixes for Distributed File System (DFS) technologies in Windows Server 2008 and Windows Server 2008 R2 (http://go.microsoft.com/fwlink/?LinkId=140177)

Good Morning Windows Gurus,

I am running into a challenge with our DFS Replication where I am daily getting multiple alerts about the service stopping communication with the partner controller because the replication is being Paused for backup or restore.  We are running Server 2012 R2 in a vmware vsphere installation. Messages below.

Text

The DFS Replication service is stopping communication with partner BV-DC1 for replication group Domain System Volume due to an error. The service will retry the connection periodically. 
 
Additional Information: 
Error: 9036 (Paused for backup or restore) 
Connection ID: E14D9BA1-6EBD-43BF-95B4-591C1773EA6D 
Replication Group ID: 7C857D6F-15C8-4C74-BDC6-1A49065B34B0

Text

The DFS Replication service encountered an error communicating with partner BV-DC1 for replication group Domain System Volume. 
 
Partner DNS address: BV-DC1.busd.loc 
 
Optional data if available: 
Partner WINS Address: BV-DC1 
Partner IP Address: 10.2.16.202 
 
The service will retry the connection periodically. 
 
Additional Information: 
Error: 9036 (Paused for backup or restore) 
Connection ID: E14D9BA1-6EBD-43BF-95B4-591C1773EA6D 
Replication Group ID: 7C857D6F-15C8-4C74-BDC6-1A49065B34B0

I have temporarily paused Veeam backups of the FSMO server to rule out the service causing the interruption. I have also ran the AD Replication Status tool and everything comes back clean. AD is replicating. Do I need to stress over these errors? They seem pretty numerous given my past experience with Windows Server.

Thank you very much for your time. Happy Wednesday.

If you have ever had issues with NETLOGON or SYSVOL folders not replicating across domain controllers you know that it can be a huge pain in the butt. Whether it be your policy definitions folder not replicating or group policy is just out of sync with the rest of your DCs. It’s an issue that many sysadmins over time have had to overcome however, luckily for me, I was fortunate enough to have had it happen in my lab. My issue was sysvol was not replicating on my 2019 domain controllers so not only did I need to be able to force sysvol replication, I needed to get to the root of the issue to figure out why. Today we’re going to fix sysvol folders not replicating across domain controllers.

I have also posted a video of how to fix domain controller replication at the end of this post for those who prefer to watch the demo 🙂

After checking the event viewer I am across several logs that seemed a bit concerning to me.

Log Name: DFS Replication
Source: DFSR
Date: 3/25/2020 1:04:30 PM
Event ID: 4612
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: PAC-DC02.ad.thesysadminchannel.com

Description:
The DFS Replication service initialized SYSVOL at local path C:\Windows\SYSVOL\domain and is waiting to perform initial replication. 
The replicated folder will remain in the initial synchronization state until it has replicated with its partner PAC-DC01.ad.thesysadminchannel.com. 
If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. 
This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. 
If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. 
This can cause the SYSVOL folder on this server to become out of sync with other domain controllers. 
 
Additional Information: 
Replicated Folder Name: SYSVOL Share 
Replicated Folder ID: 33B02C74-D5A3-41A7-A1EB-7D526AA4A243 
Replication Group Name: Domain System Volume 
Replication Group ID: 3CA9F092-C1B4-4F46-B276-7FD034A8E03C 
Member ID: 2AED3E8C-B864-4939-8969-BC747CD672C5 
Read-Only: 0



Log Name: DFS Replication
Source: DFSR
Date: 3/25/2020 1:04:30 PM
Event ID: 5002
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: PAC-DC02.ad.thesysadminchannel.com
Description:
The DFS Replication service encountered an error communicating with partner PAC-DC01 for replication group Domain System Volume. 
 
Partner DNS address: PAC-DC01.ad.thesysadminchannel.com 
 
Optional data if available: 
Partner WINS Address: PAC-DC01 
Partner IP Address: 172.16.10.101 
 
The service will retry the connection periodically. 
 
Additional Information: 
Error: 1753 (There are no more endpoints available from the endpoint mapper.) 
Connection ID: 3CA9F092-C1B4-4F46-B276-7FD034A8E03C 
Replication Group ID: FD8F1538-9B92-4EF9-9E8E-E74512BC2149

EventID-4612-DFSR-Failure

EventID-5002-DFSR-Failure

First things first, we need to determine which domain controller is going to act as the master server. This needs to be the most updated DC in terms of policies because this will overwrite anything and everything that doesn’t match.

An example of this is if you create the policies on DC01, and those policies never replicate to DC02. DC01 is more up to date than DC02 so DC01 should be your master.

Once you have that all set, you can follow the steps in the video.

Hopefully you found that very useful and now your sysvol replication is working as expected. If you still have doubts, you can check out Microsoft’s Documentation for the official page.

Paul Contreras

Hi, my name is Paul and I am a Sysadmin who enjoys working on various technologies from Microsoft, VMWare, Cisco and many others. Join me as I document my trials and tribulations of the daily grind of System Administration.

  • Remove From My Forums
  • Question

  • I am getting the following error:

    The DFS Replication service encountered an error communicating with partner «computerX» for replication group Domain System Volume. 

     
    Partner DNS address: computerX.mydomain.local 

     
    Optional data if available: 
    Partner WINS Address: computerX
    Partner IP Address:  

     
    The service will retry the connection periodically. 

     
    Additional Information: 
    Error: 1753 (There are no more endpoints available from the endpoint mapper.) 
    Connection ID: 1AF76904-674E-4276-9360-256115BE3BBA 
    Replication Group ID: 8573BF33-9A6A-4890-BB2A-E6DCCBD686CA

    ComputerX is a server that was previously running as a domain server on our domain.  It was demoted using DCPromo and then removed from the domain.  When I take a look in the DFS Management MMC the Domain System Volume replication object does not
    contain a folder for this server any longer, it only lists our currently active servers.  Does anyone know how to fix this issue?

Имеется контроллер домена DC01 на Windows Server 2012 R2 (уровень домена\леса 2012 R2) со всеми ролями FSMO, DNS, а также он DHCP.

PS C:\Windows\system32> netdom /query fsmo
Хозяин схемы                DC01.*.*.*
Хозяин именования доменов   DC01.*.*.*
PDC                         DC01.*.*.*
Диспетчер пула RID          DC01.*.*.*
Хозяин инфраструктуры       DC01.*.*.*
Команда выполнена успешно.

В журнале DFS появляется ошибка —

Имя журнала:   DFS Replication
Источник:      DFSR
Дата:          07.04.2014 11:35:47
Код события:   6002
Категория задачи:Отсутствует
Уровень:       Ошибка
Ключевые слова:Классический
Пользователь:  Н/Д
Компьютер:     DC01.*.*.*
Описание:
Служба репликации DFS обнаружила недопустимые данные объекта 
msDFSR-Subscriber при запросе  сведений о конфигурации. 
 
Дополнительные сведения: 
DN объекта: CN=Domain System Volume,CN=DFSR-LocalSettings,CN=DC01,
OU=Domain Controllers,DC=*,DC=*,DC=* 
Имя атрибута: msDFSR-MemberReference 
Контроллер домена: DC01.*.*.*
Цикл запроса: 60 мин
Xml события:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="DFSR" />
    <EventID Qualifiers="49152">6002</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-07T08:35:47.000000000Z" />
    <EventRecordID>276</EventRecordID>
    <Channel>DFS Replication</Channel>
    <Computer>DC01.*.*.*</Computer>
    <Security />
  </System>
  <EventData>
    <Data>msDFSR-Subscriber</Data>
    <Data>CN=Domain System Volume,CN=DFSR-LocalSettings,CN=DC01,
OU=Domain Controllers,DC=*,DC=*,DC=*</Data>
    <Data>msDFSR-MemberReference</Data>
    <Data>DC01.*.*.*</Data>
    <Data>60</Data>
  </EventData>
</Event>

Также имеется второй контроллер домена DC00, также Windows Server 2012 R2, на нем не появились шары SYSVOL и NETLOGON, в журнале следующее

Имя журнала:   DFS Replication
Источник:      DFSR
Дата:          07.04.2014 17:01:43
Код события:   4612
Категория задачи:Отсутствует
Уровень:       Ошибка
Ключевые слова:Классический
Пользователь:  Н/Д
Компьютер:     DC00.*.*.*
Описание:
Служба репликации DFS инициализировала SYSVOL по локальному 
пути C:\Windows\SYSVOL\domain и готова к начальной репликации. 
Реплицированная папка останется в состоянии начальной синхронизации 
до выполнения репликации со своим партнером DC01.*.*.*. 
Если в это время выполнялось назначение сервера контроллером домена, 
контроллер домена не будет делать объявления и функционировать как 
контроллер домена, пока данная проблема не будет решена. Это могло 
произойти, если указанный партнер также находится в состоянии начальной 
синхронизации или обнаружены нарушения общего доступа на этом сервере 
или партнере синхронизации. Если данное событие произошло в результате 
миграции SYSVOL от службы репликации файлов (FRS) к репликации DFS, изменения 
не будут реплицироваться до тех пор, пока эта проблема не будет решена. 
В результате этого папка SYSVOL на данном сервере может стать не 
синхронизированной с другими контроллерами домена. 
  
Дополнительные сведения:  
Имя реплицированной папки: SYSVOL Share 
Идентификатор реплицированной папки: C0D02335-2516-4027-A9CA-0B86A386E210 
Имя группы репликации: Domain System Volume 
Идентификатор группы репликации: 5F0F06CC-E904-4E94-9ED2-9C70D442AD3B 
Код участника: 22614947-BBFD-4BE5-BBE0-20E99675B0B1 
Только для чтения: 0
Xml события:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="DFSR" />
    <EventID Qualifiers="49152">4612</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-07T14:01:43.000000000Z" />
    <EventRecordID>88</EventRecordID>
    <Channel>DFS Replication</Channel>
    <Computer>DC00.*.*.*</Computer>
    <Security />
  </System>
  <EventData>
    <Data>C0D02335-2516-4027-A9CA-0B86A386E210</Data>
    <Data>C:\Windows\SYSVOL\domain</Data>
    <Data>SYSVOL Share</Data>
    <Data>Domain System Volume</Data>
    <Data>5F0F06CC-E904-4E94-9ED2-9C70D442AD3B</Data>
    <Data>22614947-BBFD-4BE5-BBE0-20E99675B0B1</Data>
    <Data>DC01.*.*.*y</Data>
    <Data>0</Data>
  </EventData>
</Event>

и

Имя журнала:   DFS Replication
Источник:      DFSR
Дата:          07.04.2014 17:01:43
Код события:   5002
Категория задачи:Отсутствует
Уровень:       Ошибка
Ключевые слова:Классический
Пользователь:  Н/Д
Компьютер:     DC00.*.*.*
Описание:
Служба репликации DFS обнаружила ошибку в подключении к 
партнеру DC01 для группы репликации Domain System Volume. 
 
DNS-адрес партнера: DC01.*.*.*
 
Доступные дополнительные сведения: 
WINS-адрес партнера: DC01 
IP-адрес партнера: 192.168.50.53 
  
Служба периодически будет пытаться установить подключение. 
 
Дополнительные сведения: 
Ошибка: 1753 (В системе отображения конечных точек не 
осталось доступных конечных точек.) 
Идентификатор подключения: 5F0F06CC-E904-4E94-9ED2-9C70D442AD3B 
Идентификатор группы репликации: D687A311-7DA0-48CC-8176-859049523817
Xml события:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="DFSR" />
    <EventID Qualifiers="49152">5002</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-07T14:01:43.000000000Z" />
    <EventRecordID>87</EventRecordID>
    <Channel>DFS Replication</Channel>
    <Computer>DC00.*.*.*</Computer>
    <Security />
  </System>
  <EventData>
    <Data>5F0F06CC-E904-4E94-9ED2-9C70D442AD3B</Data>
    <Data>DC01</Data>
    <Data>Domain System Volume</Data>
    <Data>DC01.*.*.*</Data>
    <Data>DC01</Data>
    <Data>192.168.50.53</Data>
    <Data>1753</Data>
    <Data>В системе отображения конечных точек не осталось 
доступных конечных точек.</Data>
    <Data>D687A311-7DA0-48CC-8176-859049523817</Data>
  </EventData>
</Event>

Решения из гугла не помогли. Если нужна еще какая-то информация — предоставлю.

Понравилась статья? Поделить с друзьями:

Интересное по теме:

  • 500 ошибка сервера beget
  • 5001 ошибка мерседес 204
  • 500 ошибка примеры
  • 5001 код ошибки стандофф
  • 50003 ошибка зум

  • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии