Jump to content


Directory service Error 1863

event id 1863

  • Please log in to reply
1 reply to this topic

#1 sikandarht

sikandarht

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 13 April 2012 - 05:20 PM

we have at office one win 2k3 DC, & ADC each; DC is crashed and ADC is promoted with seizer command DC.....all work fine.....DC is never back online.....now we have another machine and becoming ADC; all replication occur

but event id some errors occur again and again with even id 1863. can anybody help how to solve this.......

the ADC which now act as DC.....name allied-bdc.hg.com
the new ADC name is : NSS.hg.com
===========
Directory Service Error: EVENT ID: 1863
==========
This is the replication status for the following directory partition on the local domain controller.

Directory partition:
DC=ForestDnsZones,DC=hg,DC=com

The local domain controller has not received replication information from a number of domain controllers within the configured latency interval.

Latency Interval (Hours):
24
Number of domain controllers in all sites:
1
Number of domain controllers in this site:
1

The latency interval can be modified with the following registry key.

Registry Key:
HKLM\System\CurrentControlSet\Services\NTDS\Parame ters\Replicator latency error interval (hours)

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 <partition-dn>".

For more information, see Help and Support Center

============================================
using dcdiag at cmd
============================================

Microsoft Windows [Version 5.2.3790]
© Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.HG>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: HimontGroup\ALLIED-BDC
Starting test: Connectivity
......................... ALLIED-BDC passed test Connectivity

Doing primary tests

Testing server: HimontGroup\ALLIED-BDC
Starting test: Replications
[Replications Check,ALLIED-BDC] Inbound replication is disabled.
To correct, run "repadmin /options ALLIED-BDC -DISABLE_INBOUND_REPL"
[Replications Check,ALLIED-BDC] Outbound replication is disabled.
To correct, run "repadmin /options ALLIED-BDC -DISABLE_OUTBOUND_REPL"
......................... ALLIED-BDC failed test Replications
Starting test: NCSecDesc
......................... ALLIED-BDC passed test NCSecDesc
Starting test: NetLogons
......................... ALLIED-BDC passed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for \\nss.hg.com, when we wer
e trying to reach ALLIED-BDC.
Server is not responding or is not considered suitable.
Warning: ALLIED-BDC is not advertising as a time server.
......................... ALLIED-BDC failed test Advertising
Starting test: KnowsOfRoleHolders
......................... ALLIED-BDC passed test KnowsOfRoleHolders
Starting test: RidManager
......................... ALLIED-BDC passed test RidManager
Starting test: MachineAccount
......................... ALLIED-BDC passed test MachineAccount
Starting test: Services
w32time Service is stopped on [ALLIED-BDC]
NETLOGON Service is paused on [ALLIED-BDC]
......................... ALLIED-BDC failed test Services
Starting test: ObjectsReplicated
......................... ALLIED-BDC passed test ObjectsReplicated
Starting test: frssysvol
......................... ALLIED-BDC 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.
......................... ALLIED-BDC failed test frsevent
Starting test: kccevent
......................... ALLIED-BDC passed test kccevent
Starting test: systemlog
......................... ALLIED-BDC passed test systemlog
Starting test: VerifyReferences
......................... ALLIED-BDC 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 : hg
Starting test: CrossRefValidation
......................... hg passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... hg passed test CheckSDRefDom

Running enterprise tests on : hg.com
Starting test: Intersite
......................... hg.com passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 135
5
A Good Time Server could not be located.
......................... hg.com failed test FsmoCheck

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

metadata cleanup runs.....and clean domain that have pointed ......which is now offline.!!!!
plz plz help.....

Posted Image


  • 0

#2 kamtec1

kamtec1

    Microsoft Servers Expert

  • Technical Experts
  • PipPipPipPip
  • 882 posts
  • Gender:Male
  • Location:Israel
  • Interests:MCSE/MCSA/A+/MCTS
    Microsoft Servers
    Microsoft Products
    IPTell
    CEH
    CISCO
    Microsoft® Certified IT Professional ﴾MCITP﴿

Posted 08 June 2012 - 08:00 AM

Hi .

This event may be an indication that the Active Directory may contain lingering objects (objects that are deleted from the Active Directory directory service when the domain controller is offline). These can occur if a domain controller does not replicate for an interval of time that is longer than the tombstone lifetime (TSL).

You can see the fix in MS site :)
gfp://technet.microsoft.com/en-us/library/cc738018(v=ws.10).aspx

g//technet.microsoft.com/en-us/library/cc738415(v=ws.10).aspx


Good luck.
  • 0





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users