Ошибка 1864 на контроллере домена

Здравствуйте. Имеется следующая проблема: на всех контроллерах домена возникает ошибка с кодом 1864. Ошибке подвержены следующие разделы:

DC=ForestDnsZones,DC=root,DC=tpkdom,DC=local

DC=DomainDnsZones,DC=main,DC=root,DC=tpkdom,DC=local

DC=main,DC=root,DC=tpkdom,DC=local

CN=Schema,CN=Configuration,DC=root,DC=tpkdom,DC=local

CN=Configuration,DC=root,DC=tpkdom,DC=local

Схема доменной структуры такая: Основной домен: ROOT.TPKDOM.LOCAL, в нём MAIN.ROOT.TPKDOM.LOCAL

DCDIAG выглядит следующим образом:

C:\Windows\system32>dcdiag
Диагностика сервера каталогов
Выполнение начальной настройки:
   Выполняется попытка поиска основного сервера...
   Основной сервер = DC03MAIN01
   * Идентифицирован лес AD.
   Сбор начальных данных завершен.

Выполнение обязательных начальных проверок
   Сервер проверки: TPKDOM-Tyumen01\DC03MAIN01
      Запуск проверки: Connectivity
         ......................... DC03MAIN01 - пройдена проверка Connectivity

Выполнение основных проверок
   Сервер проверки: TPKDOM-Tyumen01\DC03MAIN01
      Запуск проверки: Advertising
         ......................... DC03MAIN01 - пройдена проверка Advertising
      Запуск проверки: FrsEvent
         ......................... DC03MAIN01 - пройдена проверка FrsEvent
      Запуск проверки: DFSREvent
         ......................... DC03MAIN01 - пройдена проверка DFSREvent
      Запуск проверки: SysVolCheck
         ......................... DC03MAIN01 - пройдена проверка SysVolCheck
      Запуск проверки: KccEvent
         ......................... DC03MAIN01 - пройдена проверка KccEvent
      Запуск проверки: KnowsOfRoleHolders
         ......................... DC03MAIN01 - пройдена проверка
         KnowsOfRoleHolders
      Запуск проверки: MachineAccount
         * Текущий контроллер домена не принадлежит к подразделению контроллера
         домена
         ......................... DC03MAIN01 - не пройдена проверка
         MachineAccount
      Запуск проверки: NCSecDesc
         ......................... DC03MAIN01 - пройдена проверка NCSecDesc
      Запуск проверки: NetLogons
         ......................... DC03MAIN01 - пройдена проверка NetLogons
      Запуск проверки: ObjectsReplicated
         ......................... DC03MAIN01 - пройдена проверка
         ObjectsReplicated
      Запуск проверки: Replications
         ПРЕДУПРЕЖДЕНИЕ О ЗАДЕРЖКЕ ПОЛУЧЕННОЙ РЕПЛИКАЦИИ
         DC03MAIN01:  Текущее время - 2015-11-30 11:56:03.
            DC=ForestDnsZones,DC=root,DC=tpkdom,DC=local
               Последняя репликация получена из DC05MAIN04 в
          2015-09-18 15:19:13
               Последняя репликация получена из DC03MAIN02 в
          2015-05-29 17:03:24
               ВНИМАНИЕ!  Эта задержка превышает время жизни захоронения в 180
         дней.
            CN=Schema,CN=Configuration,DC=root,DC=tpkdom,DC=local
               Последняя репликация получена из DC05MAIN04 в
          2015-09-18 15:19:13
               Последняя репликация получена из DC03MAIN02 в
          2015-05-29 17:03:23
               ВНИМАНИЕ!  Эта задержка превышает время жизни захоронения в 180
         дней.
            CN=Configuration,DC=root,DC=tpkdom,DC=local
               Последняя репликация получена из DC05MAIN04 в
          2015-09-18 15:19:13
               Последняя репликация получена из DC03MAIN02 в
          2015-05-29 17:03:23
               ВНИМАНИЕ!  Эта задержка превышает время жизни захоронения в 180
         дней.
            DC=DomainDnsZones,DC=main,DC=root,DC=tpkdom,DC=local
               Последняя репликация получена из DC05MAIN04 в
          2015-09-18 15:19:13
               Последняя репликация получена из DC03MAIN02 в
          2015-05-29 17:03:24
               ВНИМАНИЕ!  Эта задержка превышает время жизни захоронения в 180
         дней.
            DC=main,DC=root,DC=tpkdom,DC=local
               Последняя репликация получена из DC05MAIN04 в
          2015-09-18 15:19:13
               Последняя репликация получена из DC03MAIN02 в
          2015-05-29 17:03:24
               ВНИМАНИЕ!  Эта задержка превышает время жизни захоронения в 180
         дней.
         ......................... DC03MAIN01 - пройдена проверка Replications
      Запуск проверки: RidManager
         ......................... DC03MAIN01 - пройдена проверка RidManager
      Запуск проверки: Services
         ......................... DC03MAIN01 - пройдена проверка Services
      Запуск проверки: SystemLog
         ......................... DC03MAIN01 - пройдена проверка SystemLog
      Запуск проверки: VerifyReferences
         Проблемы у некоторых объектов, относящихся к DC DC03MAIN01:
            [1] Проблема: Отсутствует ожидаемое значение
             Базовый объект:
            CN=DC03MAIN01,OU=Domain_Controllers,OU=Servers,OU=Tyumen,DC=main,DC=
root,DC=tpkdom,DC=local
             Описание базового объекта: "Объект учетной записи DC"
             Имя атрибута объекта значения: frsComputerReferenceBL
             Описание объекта значения: "Объект члена SYSVOL FRS"
             Рекомендуемое действие: См. статью базы знаний: Q312862
         ......................... DC03MAIN01 - не пройдена проверка
         VerifyReferences


   Выполнение проверок разделов на: ForestDnsZones
      Запуск проверки: CheckSDRefDom
         ......................... ForestDnsZones - пройдена проверка
         CheckSDRefDom
      Запуск проверки: CrossRefValidation
         ......................... ForestDnsZones - пройдена проверка
         CrossRefValidation

   Выполнение проверок разделов на: DomainDnsZones
      Запуск проверки: CheckSDRefDom
         ......................... DomainDnsZones - пройдена проверка
         CheckSDRefDom
      Запуск проверки: CrossRefValidation
         ......................... DomainDnsZones - пройдена проверка
         CrossRefValidation

   Выполнение проверок разделов на: main
      Запуск проверки: CheckSDRefDom
         ......................... main - пройдена проверка CheckSDRefDom
      Запуск проверки: CrossRefValidation
         ......................... main - пройдена проверка CrossRefValidation

   Выполнение проверок разделов на: Schema
      Запуск проверки: CheckSDRefDom
         ......................... Schema - пройдена проверка CheckSDRefDom
      Запуск проверки: CrossRefValidation
         ......................... Schema - пройдена проверка
         CrossRefValidation

   Выполнение проверок разделов на: Configuration
      Запуск проверки: CheckSDRefDom
         ......................... Configuration - пройдена проверка
         CheckSDRefDom
      Запуск проверки: CrossRefValidation
         ......................... Configuration - пройдена проверка
         CrossRefValidation

   Выполнение проверок предприятия на: root.tpkdom.local
      Запуск проверки: LocatorCheck
         ......................... root.tpkdom.local - пройдена проверка
         LocatorCheck
      Запуск проверки: Intersite
         ......................... root.tpkdom.local - пройдена проверка
         Intersite

DC03MAIN01, DC01MAIN01, DC02MAIN01-R2 — контроллеры домена MAIN

DC01ROOT01, DC03ROOT01 — контроллеры домена ROOT

В логах присутствуют другие контроллеры домена, но с большинством из них связи уже не будет — они выведены из работы, но домен ещё не почищен.

Проблема в том, что скоро будет превышен срок захоронения в 180 дней.

Уточню также, что никаких проблем в работе домена не замечено — синхронизация с живыми контроллерами домена проходит замечательно. Других ошибок не обнарудено.

Источник
  • Remove From My Forums

  • Question

  • Dear All,

    i got error NTDS Replication event id 1864, this error appear on all DC every 24 hours.
    If i test replication using repadmin, the result was successfull. No replication issue..

    how to fix that error?

    Thank you

    Regards,

    Endrik

Answers

  • Dear All, 

    Microsoft Service already solve this case.

    This is step by step:
    1. Verify that replication to all DC servers are succesffully, and I get 1 replication failed to 1 DC on the branch site because there are outage electricity and connection problem. However, the error NTDS Replication event id 1864 still appear even the replication to all DCs are successfull.

    2. Run command repadmin /showvec /latency and there a record say like that:
        domain\lostandfound    @USN    <<DATE>>,

    This is happen because there are object NTDS on that lostandfound container which is still using on the replication progress. We delete the NTDS Object and After that, the Error gone on the Event Viewer.

    Thank you for all.

    Regards,

    Endrik

    • Marked as answer by

      Friday, February 19, 2010 8:56 AM

Источник

Hello,

We have multiple DCs in different sites, and all five servers but one are showing Event ID 1864 in the log:

——————

This is the replication status for the following directory partition on this directory server.

Directory partition:
DC=ForestDnsZones,DC=domain,DC=domain,DC=org

This directory server has not recently received replication information from a number of directory servers.  The count of directory servers is shown, divided into the following intervals.

More than 24 hours:
1
More than a week:
1
More than one month:
0
More than two months:
0
More than a tombstone lifetime:
0
Tombstone lifetime (days):
60

————

I ran dcdiag and all the tests are passing except the NCSecDesc test.  Which also seems to indicate problems with replication.  I did some research and read many blogs and articles.  Microsoft says that this has to do with RODCs but we don’t have any RODCs in this forest.  Any ideas or suggestions? 

Источник

Problem: NTDS Replication Errors, Due to missing Domain Controller “Event ID: 1864”

Running Windows Server 2003 running as Primary Domain Controller.  I have another Windows 2003 server running Exchange 2003 and also a Secondary Domain Controller.  Also have a third server which is also Windows 2003 which is a Secondary Domain and Secondary DNS Server.

The following errors occur for SERVER12.  SERVER12 is a server I built and then scrapped.  I install the domain controller role on the server, but never demoted or removed the role before wiping out the server.

Below is the error I am receiving.  I also posted a copy of the results from a DCDIAG on the primary Domain Controller.

What are the best practices for removing SERVER12 from my network so I do not receive these messages again?

————————————-
Event Type:      Error
Event Source:      NTDS Replication
Event Category:      Replication
Event ID:      1864
Date:            12/4/2005
Time:            6:01:27 PM
User:            NT AUTHORITYANONYMOUS LOGON
Computer:      SERVER0
Description:
This is the replication status for the following directory partition on the local domain controller.

Directory partition:
CN=Schema,CN=Configuration,DC=DOMAIN,DC=local

The local domain controller has not recently received replication information from a number of domain controllers.   The count of domain controllers is shown, divided into the following intervals.

More than 24 hours:
1
More than a week:
1
More than one month:
1
More than two months:
0
More than a tombstone lifetime:
0
Tombstone lifetime (days):
60
Domain controllers that do not replicate in a timely manner may encounter errors. It may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled.

To identify the domain controllers by name, install the support tools included on the installation  CD and run dcdiag.exe.
You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest.   The command is “repadmin /showvector /latency “.

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

————————————-
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

P:>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-SiteSERVER0
Starting test: Connectivity
……………………. SERVER0 passed test Connectivity

Doing primary tests

Testing server: Default-First-SiteSERVER0
Starting test: Replications
[Replications Check,SERVER0] A recent replication attempt failed:
From SERVER12 to SERVER0
Naming Context: CN=Schema,CN=Configuration,DC=DOMAIN,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2005-12-05 09:46:37.
The last success occurred at 2005-11-02 15:48:28.
788 failures have occurred since the last success.
[SERVER12] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
The source remains down. Please check the machine.
[Replications Check,SERVER0] A recent replication attempt failed:
From SERVER12 to SERVER0
Naming Context: CN=Configuration,DC=DOMAIN,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2005-12-05 09:46:16.
The last success occurred at 2005-11-02 15:49:17.
788 failures have occurred since the last success.
The source remains down. Please check the machine.
[Replications Check,SERVER0] A recent replication attempt failed:
From SERVER12 to SERVER0
Naming Context: DC=DOMAIN,DC=local
The replication generated an error (1722):
The RPC server is unavailable.
The failure occurred at 2005-12-05 09:45:55.
The last success occurred at 2005-11-02 16:08:40.
788 failures have occurred since the last success.
The source remains down. Please check the machine.
REPLICATION-RECEIVED LATENCY WARNING
SERVER0:  Current time is 2005-12-05 09:47:37.
CN=Schema,CN=Configuration,DC=DOMAIN,DC=local
Last replication recieved from SERVER12 at 2005-11-02 15:58:42.
CN=Configuration,DC=DOMAIN,DC=local
Last replication recieved from SERVER12 at 2005-11-02 15:58:42.
DC=DOMAIN,DC=local
Last replication recieved from SERVER12 at 2005-11-02 16:08:43.
……………………. SERVER0 passed test Replications
Starting test: NCSecDesc
……………………. SERVER0 passed test NCSecDesc
Starting test: NetLogons
……………………. SERVER0 passed test NetLogons
Starting test: Advertising
……………………. SERVER0 passed test Advertising
Starting test: KnowsOfRoleHolders
……………………. SERVER0 passed test KnowsOfRoleHolders
Starting test: RidManager
……………………. SERVER0 passed test RidManager
Starting test: MachineAccount
……………………. SERVER0 passed test MachineAccount
Starting test: Services
……………………. SERVER0 passed test Services
Starting test: ObjectsReplicated
……………………. SERVER0 passed test ObjectsReplicated
Starting test: frssysvol
……………………. SERVER0 passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared.  Failing SYSVOL replication problems may cause
Group Policy problems.
……………………. SERVER0 failed test frsevent
Starting test: kccevent
……………………. SERVER0 passed test kccevent
Starting test: systemlog
……………………. SERVER0 passed test systemlog
Starting test: VerifyReferences
……………………. SERVER0 passed test VerifyReferences

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
……………………. ForestDnsZones passed test CrossRefValidation

Starting test: CheckSDRefDom
……………………. ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
……………………. DomainDnsZones passed test CrossRefValidation

Starting test: CheckSDRefDom
……………………. DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
……………………. Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
……………………. Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
……………………. Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
……………………. Configuration passed test CheckSDRefDom

Running partition tests on : SERVER
Starting test: CrossRefValidation
……………………. DOMAIN passed test CrossRefValidation
Starting test: CheckSDRefDom
……………………. DOMAIN passed test CheckSDRefDom

Running enterprise tests on : SERVER.local
Starting test: Intersite
……………………. DOMAIN.local passed test Intersite
Starting test: FsmoCheck
……………………. DOMAIN.local passed test FsmoCheck

P:>
————————————-

Solution : NTDS Replication Errors, Due to missing Domain Controller “Event ID: 1864”

First, clean out your AD:
How to remove data in Active Directory after an unsuccessful domain controller demotion
http://support.microsoft.com/?kbid=216498

Then check AD Sites and Services, if the old server still shows up.

Источник

Step 1 – Solve Ntds Replication Error 1864 Fix

Is Ntds Replication Error 1864 Fix appearing? Would you like to safely and quickly eliminate event id 1864 which additionally can lead to a blue screen of death?

When you manually edit your Windows Registry trying to take away the invalid event id 1864 windows 2008 r2 keys you’re taking a authentic chance. Unless you’ve got been adequately trained and experienced you’re in danger of disabling your computer system from working at all. You could bring about irreversible injury to your whole operating system. As very little as just 1 misplaced comma can preserve your Pc from even booting every one of the way by!

Troubleshooting event id 1864 activedirectory_domainservice Windows XP, Vista, 7, 8 & 10

Simply because this chance is so higher, we hugely suggest that you make use of a trusted registry cleaner plan like CCleaner (Microsoft Gold Partner Licensed). This system will scan and then fix any Ntds Replication Error 1864 Fix complications.

Registry cleaners automate the entire procedure of finding invalid registry entries and missing file references (including the Fix error) likewise as any broken hyperlinks inside of your registry.

Issue with repadmin /showvector /latency

Backups are made immediately prior to each and every scan providing you with the choice of undoing any changes with just one click. This protects you against doable damaging your pc. Another advantage to these registry cleaners is that repaired registry errors will strengthen the speed and performance of one’s procedure drastically.

  • http://www.experts-exchange.com/questions/21301536/Event-Id-1864-NTDS-replication-error.html
  • https://community.spiceworks.com/topic/146233-event-id-1864-windows-server-2008-ad-error
  • https://community.spiceworks.com/windows_event/show/413-ntds-replication-1864
  • http://serverfault.com/questions/696627/windows-server-2003-ad-replication-error-1864

Cautionary Note: Yet again, for those who are not an state-of-the-art consumer it’s very encouraged that you simply refrain from editing your Windows Registry manually. If you make even the smallest error within the Registry Editor it can result in you some serious issues that may even call for a brand new set up of Windows. Not all difficulties attributable to incorrect Registry Editor use are solvable.

Fixed: repadmin /showvector /latency partition-dn

Symptoms of Ntds Replication Error 1864 Fix
“Ntds Replication Error 1864 Fix” appears and crashes the energetic method window.
Your Personal computer routinely crashes with Ntds Replication Error 1864 Fix when running the exact same system.
“Ntds Replication Error 1864 Fix” is shown.
Windows operates sluggishly and responds little by little to mouse or keyboard input.
Your computer periodically “freezes” for the number of seconds in a time.

Will cause of Ntds Replication Error 1864 Fix

Corrupt obtain or incomplete set up of Windows Operating System software program.

Corruption in Windows registry from a new Windows Operating System-related application adjust (install or uninstall).

Virus or malware infection which has corrupted Windows method documents or Windows Operating System-related application data files.

Another method maliciously or mistakenly deleted Windows Operating System-related files.

Mistakes this sort of as “Ntds Replication Error 1864 Fix” can be brought about by several different elements, so it really is important that you troubleshoot every of the achievable brings about to forestall it from recurring.

Simply click the beginning button.
Variety “command” inside the lookup box… Will not hit ENTER nonetheless!
Although keeping CTRL-Shift in your keyboard, hit ENTER.
You’re going to be prompted that has a authorization dialog box.
Click on Of course.
A black box will open having a blinking cursor.
Variety “regedit” and hit ENTER.
Within the Registry Editor, choose the event id 1864 windows 2008 r2 connected key (eg. Windows Operating System) you wish to back again up.
Within the File menu, choose Export.
Inside the Preserve In list, pick out the folder in which you wish to save the Windows Operating System backup key.
Inside the File Title box, sort a reputation for the backup file, these types of as “Windows Operating System Backup”.
From the Export Vary box, ensure that “Selected branch” is selected.
Click on Help you save.
The file is then saved by using a .reg file extension.
You now use a backup within your event id 1864 activedirectory_domainservice related registry entry.

Solution to your repadmin /test:replication problem

There are actually some manual registry editing measures that can not be talked about in this article due to the high chance involved for your laptop or computer method. If you want to understand more then check out the links below.

Additional Measures:

One. Conduct a Thorough Malware Scan

There’s a probability the Error Replication 1864 Fix Ntds error is relevant to some variety of walware infection. These infections are malicious and ready to corrupt or damage and possibly even delete your ActiveX Control Error files. Also, it’s attainable that your Ntds Replication Error 1864 Fix is actually connected to some element of that malicious plan itself.

2. Clean dsreplicagetinfo() failed with status 8453 (0x2105): replication access was denied. Disk Cleanup

The a lot more you employ your computer the extra it accumulates junk files. This comes from surfing, downloading packages, and any sort of usual computer system use. When you don’t clean the junk out occasionally and keep your program clean, it could turn into clogged and respond slowly. That is when you can encounter an Replication error because of possible conflicts or from overloading your hard drive.

Once you clean up these types of files using Disk Cleanup it could not just remedy Ntds Replication Error 1864 Fix, but could also create a dramatic change in the computer’s efficiency.

Tip: While ‘Disk Cleanup’ is definitely an excellent built-in tool, it even now will not completely clean up event id discovered on your PC. There are numerous programs like Chrome, Firefox, Microsoft Office and more, that cannot be cleaned with ‘Disk Cleanup’.

Since the Disk Cleanup on Windows has its shortcomings it is extremely encouraged that you use a specialized sort of challenging drive cleanup and privacy safety application like CCleaner. This system can clean up your full pc. If you run this plan after each day (it could be set up to run instantly) you are able to be assured that your Pc is generally clean, often operating speedy, and always absolutely free of any Replication error associated with your temporary files.

How Disk Cleanup can help dcdiag

1. Click your ‘Start’ Button.
2. Style ‘Command’ into your search box. (no ‘enter’ yet)
3. When holding down in your ‘CTRL-SHIFT’ important go ahead and hit ‘Enter’.
4. You will see a ‘permission dialogue’ box.
5. Click ‘Yes’
6. You will see a black box open up plus a blinking cursor.
7. Variety in ‘cleanmgr’. Hit ‘Enter’.
8. Now Disk Cleanup will start calculating the amount of occupied disk space you will be able to reclaim.
9. Now a ‘Disk Cleanup dialogue box’ seems. There will be a series of checkboxes for you personally to pick. Generally it will likely be the ‘Temporary Files’ that consider up the vast majority of your disk area.
10. Verify the boxes that you want cleaned. Click ‘OK’.

How to repair

3. System Restore can also be a worthwhile device if you ever get stuck and just desire to get back to a time when your computer system was working ideal. It will work without affecting your pics, paperwork, or other crucial information. You can discover this option with your User interface.

event id

Manufacturer

Device

Operating System


Ntds Replication Error 1864 Fix


4 out of
5

based on
31 ratings.

 

Источник

Понравилась статья? Поделить с друзьями:
  • Ошибка 1861 приора
  • Ошибка 1861 крайслер пацифика
  • Ошибка 180001 bmw f30
  • Ошибка 1861 калина
  • Ошибка 1800 ниссан теана j32