Re: DCDiag.exe errors

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Kevin D. Goodknecht Sr. [MVP] (admin_at_nospam.WFTX.US)
Date: 08/17/04


Date: Tue, 17 Aug 2004 17:38:41 -0500

In news:uTUprOKhEHA.1652@TK2MSFTNGP09.phx.gbl,
Scott Micale <hrm_admin@news.postalalias> wrote their comments
Then Kevin replied below:
> Here are my results on 3 of my DC's in my environment. I
> need help with these and am not sure where else to go
> from here. I have one forest with 2 child domains. Any
> help is greatly appreciated

One of your servers, NT_SERVER has an underscore in its name, underscores
are only an allow DNS character if at the beginning of the name, you will
have to configure your DNS server to accept all names. Right click on the
server name in the DNS console choose properties. On the advanced tab, next
to name checking select all names from the drop down list.

Run netdiag /fix from all servers and rerun dcdiag /e /v

-- 
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
================================================
-- 
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
================================================
http://www.lonestaramerica.com/
================================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
================================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
================================================
>
>
>
> DC Diagnosis
>
>
>
> Performing initial setup:
>
>    Done gathering initial info.
>
>
>
> Doing initial non skippeable tests
>
>
>
>    Testing server: Default-First-Site-Name\HARTTOOL
>
>       Starting test: Connectivity
>
>          ......................... HARTTOOL passed test
> Connectivity
>
>
>
> Doing primary tests
>
>
>
>    Testing server: Default-First-Site-Name\HARTTOOL
>
>       Starting test: Replications
>
>          [Replications Check,HARTTOOL] A recent
> replication attempt failed:
>
>             From NT_SERVER to HARTTOOL
>
>             Naming Context:
> CN=Schema,CN=Configuration,DC=hrm,DC=lan
>
>             The replication generated an error (8524):
>
>             The DSA operation is unable to proceed
> because of a DNS lookup failu
>
> re.
>
>             The failure occurred at 2004-08-17 15:59.55.
>
>             The last success occurred at 2004-07-20
> 14:59.08.
>
>             678 failures have occurred since the last
> success.
>
>             The guid-based DNS name
> 1eecced9-7b86-4b50-a815-5c26414f350c._msdcs.
>
> hrm.lan
>
>             is not registered on one or more DNS servers.
>
>          [NT_SERVER] DsBind() failed with error 1722,
>
>          The RPC server is unavailable..
>
>          [Replications Check,HARTTOOL] A recent
> replication attempt failed:
>
>             From BRAIN to HARTTOOL
>
>             Naming Context:
> CN=Schema,CN=Configuration,DC=hrm,DC=lan
>
>             The replication generated an error (8524):
>
>             The DSA operation is unable to proceed
> because of a DNS lookup failu
>
> re.
>
>             The failure occurred at 2004-08-17 15:59.55.
>
>             The last success occurred at 2004-07-20
> 12:59.08.
>
>             680 failures have occurred since the last
> success.
>
>             The guid-based DNS name
> 0b692c1e-6566-436a-be49-0d02669e5135._msdcs.
>
> hrm.lan
>
>             is not registered on one or more DNS servers.
>
>          [BRAIN] DsBind() failed with error 1722,
>
>          The RPC server is unavailable..
>
>          [Replications Check,HARTTOOL] A recent
> replication attempt failed:
>
>             From NT_SERVER to HARTTOOL
>
>             Naming Context: CN=Configuration,DC=hrm,DC=lan
>
>             The replication generated an error (8524):
>
>             The DSA operation is unable to proceed
> because of a DNS lookup failu
>
> re.
>
>             The failure occurred at 2004-08-17 16:01.00.
>
>             The last success occurred at 2004-07-20
> 14:59.08.
>
>             3432 failures have occurred since the last
> success.
>
>             The guid-based DNS name
> 1eecced9-7b86-4b50-a815-5c26414f350c._msdcs.
>
> hrm.lan
>
>             is not registered on one or more DNS servers.
>
>          [Replications Check,HARTTOOL] A recent
> replication attempt failed:
>
>             From BRAIN to HARTTOOL
>
>             Naming Context: CN=Configuration,DC=hrm,DC=lan
>
>             The replication generated an error (8524):
>
>             The DSA operation is unable to proceed
> because of a DNS lookup failu
>
> re.
>
>             The failure occurred at 2004-08-17 16:14.46.
>
>             The last success occurred at 2004-07-20
> 13:35.51.
>
>             6922 failures have occurred since the last
> success.
>
>             The guid-based DNS name
> 0b692c1e-6566-436a-be49-0d02669e5135._msdcs.
>
> hrm.lan
>
>             is not registered on one or more DNS servers.
>
>          ......................... HARTTOOL passed test
> Replications
>
>       Starting test: NCSecDesc
>
>          ......................... HARTTOOL passed test
> NCSecDesc
>
>       Starting test: NetLogons
>
>          ......................... HARTTOOL passed test
> NetLogons
>
>       Starting test: Advertising
>
>          ......................... HARTTOOL passed test
> Advertising
>
>       Starting test: KnowsOfRoleHolders
>
>          Warning: NT_SERVER is the Schema Owner, but is
> not responding to DS RPC
>
>  Bind.
>
>          [NT_SERVER] LDAP connection failed with error 58,
>
>          The specified server cannot perform the
> requested operation..
>
>          Warning: NT_SERVER is the Schema Owner, but is
> not responding to LDAP B
>
> ind.
>
>          Warning: NT_SERVER is the Domain Owner, but is
> not responding to DS RPC
>
>  Bind.
>
>          Warning: NT_SERVER is the Domain Owner, but is
> not responding to LDAP B
>
> ind.
>
>          ......................... HARTTOOL failed test
> KnowsOfRoleHolders
>
>       Starting test: RidManager
>
>          ......................... HARTTOOL passed test
> RidManager
>
>       Starting test: MachineAccount
>
>          ......................... HARTTOOL passed test
> MachineAccount
>
>       Starting test: Services
>
>          ......................... HARTTOOL passed test
> Services
>
>       Starting test: ObjectsReplicated
>
>          ......................... HARTTOOL passed test
> ObjectsReplicated
>
>       Starting test: frssysvol
>
>          ......................... HARTTOOL passed test
> frssysvol
>
>       Starting test: kccevent
>
>          An Warning Event occured.  EventID: 0x800004F1
>
>             Time Generated: 08/17/2004   16:05:15
>
>             (Event String could not be retrieved)
>
>          An Warning Event occured.  EventID: 0x800004F1
>
>             Time Generated: 08/17/2004   16:05:15
>
>             (Event String could not be retrieved)
>
>          An Warning Event occured.  EventID: 0x800004F1
>
>             Time Generated: 08/17/2004   16:05:15
>
>             (Event String could not be retrieved)
>
>          An Warning Event occured.  EventID: 0x800004F1
>
>             Time Generated: 08/17/2004   16:05:15
>
>             (Event String could not be retrieved)
>
>          An Error Event occured.  EventID: 0xC0000466
>
>             Time Generated: 08/17/2004   16:14:29
>
>             (Event String could not be retrieved)
>
>          ......................... HARTTOOL failed test
> kccevent
>
>       Starting test: systemlog
>
>          An Error Event occured.  EventID: 0x0000165B
>
>             Time Generated: 08/17/2004   15:55:05
>
>             Event String: The session setup from the
> computer SKYNET failed
>
>          An Error Event occured.  EventID: 0x0000169E
>
>             Time Generated: 08/17/2004   16:00:19
>
>             (Event String could not be retrieved)
>
>          ......................... HARTTOOL failed test
> systemlog
>
>
>
>    Running enterprise tests on : hrm.lan
>
>       Starting test: Intersite
>
>          ......................... hrm.lan passed test
> Intersite
>
>       Starting test: FsmoCheck
>
>          Warning: DcGetDcName(GC_SERVER_REQUIRED) call
> failed, error 1355
>
>          A Global Catalog Server could not be located -
> All GC's are down.
>
>          ......................... hrm.lan failed test
> FsmoCheck
>
>
>
> This is on skynet the win2k3 DC in hh.hrm.lan
>
>
>
> C:\WINDOWS\Profiles\Administrator>dcdiag
>
>
>
> Domain Controller Diagnosis
>
>
>
> Performing initial setup:
>
>    Done gathering initial info.
>
>
>
> Doing initial required tests
>
>
>
>    Testing server: Default-First-Site-Name\SKYNET
>
>       Starting test: Connectivity
>
>          ......................... SKYNET passed test
> Connectivity
>
>
>
> Doing primary tests
>
>
>
>    Testing server: Default-First-Site-Name\SKYNET
>
>       Starting test: Replications
>
>          REPLICATION LATENCY WARNING
>
>          ERROR: Expected notification link is missing.
>
>          Source NT_SERVER
>
>          Replication of new changes along this path will
> be delayed.
>
>          This problem should self-correct on the next
> periodic sync.
>
>          ......................... SKYNET passed test
> Replications
>
>       Starting test: NCSecDesc
>
>          ......................... SKYNET passed test
> NCSecDesc
>
>       Starting test: NetLogons
>
>          ......................... SKYNET passed test
> NetLogons
>
>       Starting test: Advertising
>
>          ......................... SKYNET passed test
> Advertising
>
>       Starting test: KnowsOfRoleHolders
>
>          ......................... SKYNET passed test
> KnowsOfRoleHolders
>
>       Starting test: RidManager
>
>          ......................... SKYNET passed test
> RidManager
>
>       Starting test: MachineAccount
>
>          ......................... SKYNET passed test
> MachineAccount
>
>       Starting test: Services
>
>          ......................... SKYNET passed test
> Services
>
>       Starting test: ObjectsReplicated
>
>          ......................... SKYNET passed test
> ObjectsReplicated
>
>       Starting test: frssysvol
>
>          ......................... SKYNET passed test
> frssysvol
>
>       Starting test: frsevent
>
>          ......................... SKYNET passed test
> frsevent
>
>       Starting test: kccevent
>
>          ......................... SKYNET passed test
> kccevent
>
>       Starting test: systemlog
>
>          ......................... SKYNET passed test
> systemlog
>
>       Starting test: VerifyReferences
>
>          ......................... SKYNET passed test
> VerifyReferences
>
>
>
>    Running partition tests on : DomainDnsZones
>
>       Starting test: CrossRefValidation
>
>          ......................... DomainDnsZones passed
> test CrossRefValidation
>
>
>
>       Starting test: CheckSDRefDom
>
>          ......................... DomainDnsZones passed
> test CheckSDRefDom
>
>
>
>    Running partition tests on : hh
>
>       Starting test: CrossRefValidation
>
>          ......................... hh passed test
> CrossRefValidation
>
>       Starting test: CheckSDRefDom
>
>          ......................... hh passed test
> CheckSDRefDom
>
>
>
>    Running partition tests on : ForestDnsZones
>
>       Starting test: CrossRefValidation
>
>          ......................... ForestDnsZones passed
> test CrossRefValidation
>
>
>
>       Starting test: CheckSDRefDom
>
>          ......................... ForestDnsZones 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 enterprise tests on : hrm.lan
>
>       Starting test: Intersite
>
>          ......................... hrm.lan passed test
> Intersite
>
>       Starting test: FsmoCheck
>
>          ......................... hrm.lan passed test
> FsmoCheck
>
>
>
> And on the root win2k3 server Nt_server in hrm.lan
>
>
>
> C:\WINDOWS\Profiles\Administrator>dcdiag
>
>
>
> Domain Controller Diagnosis
>
>
>
> Performing initial setup:
>
>    Done gathering initial info.
>
>
>
> Doing initial required tests
>
>
>
>    Testing server: Default-First-Site-Name\NT_SERVER
>
>       Starting test: Connectivity
>
>          ......................... NT_SERVER passed test
> Connectivity
>
>
>
> Doing primary tests
>
>
>
>    Testing server: Default-First-Site-Name\NT_SERVER
>
>       Starting test: Replications
>
>          [Replications Check,NT_SERVER] A recent
> replication attempt failed:
>
>             From SKYNET to NT_SERVER
>
>             Naming Context:
> DC=ForestDnsZones,DC=hrm,DC=lan
>
>             The replication generated an error (8524):
>
>             The DSA operation is unable to proceed
> because of a DNS lookup failu
>
> re.
>
>             The failure occurred at 2004-08-17 16:29:52.
>
>             The last success occurred at 2004-08-08
> 04:52:19.
>
>             960 failures have occurred since the last
> success.
>
>             The guid-based DNS name
> 177f2bc1-7971-47e6-8cfb-1b36a2f1f4d5._msdcs.
>
> hrm.lan
>
>             is not registered on one or more DNS servers.
>
>          [SKYNET] DsBindWithSpnEx() failed with error
> 1722,
>
>          The RPC server is unavailable..
>
>          [Replications Check,NT_SERVER] A recent
> replication attempt failed:
>
>             From SKYNET to NT_SERVER
>
>             Naming Context:
> CN=Schema,CN=Configuration,DC=hrm,DC=lan
>
>             The replication generated an error (8524):
>
>             The DSA operation is unable to proceed
> because of a DNS lookup failu
>
> re.
>
>             The failure occurred at 2004-08-17 15:55:20.
>
>             The last success occurred at 2004-08-08
> 04:52:19.
>
>             229 failures have occurred since the last
> success.
>
>             The guid-based DNS name
> 177f2bc1-7971-47e6-8cfb-1b36a2f1f4d5._msdcs.
>
> hrm.lan
>
>             is not registered on one or more DNS servers.
>
>          [Replications Check,NT_SERVER] A recent
> replication attempt failed:
>
>             From SKYNET to NT_SERVER
>
>             Naming Context: CN=Configuration,DC=hrm,DC=lan
>
>             The replication generated an error (8524):
>
>             The DSA operation is unable to proceed
> because of a DNS lookup failu
>
> re.
>
>             The failure occurred at 2004-08-17 16:11:06.
>
>             The last success occurred at 2004-08-08
> 04:52:19.
>
>             645 failures have occurred since the last
> success.
>
>             The guid-based DNS name
> 177f2bc1-7971-47e6-8cfb-1b36a2f1f4d5._msdcs.
>
> hrm.lan
>
>             is not registered on one or more DNS servers.
>
>          [Replications Check,NT_SERVER] A recent
> replication attempt failed:
>
>             From SKYNET to NT_SERVER
>
>             Naming Context: DC=hh,DC=hrm,DC=lan
>
>             The replication generated an error (8524):
>
>             The DSA operation is unable to proceed
> because of a DNS lookup failu
>
> re.
>
>             The failure occurred at 2004-08-17 16:34:10.
>
>             The last success occurred at 2004-08-08
> 05:01:03.
>
>             20174 failures have occurred since the last
> success.
>
>             The guid-based DNS name
> 177f2bc1-7971-47e6-8cfb-1b36a2f1f4d5._msdcs.
>
> hrm.lan
>
>             is not registered on one or more DNS servers.
>
>          REPLICATION-RECEIVED LATENCY WARNING
>
>          NT_SERVER:  Current time is 2004-08-17 16:34:27.
>
>             DC=ForestDnsZones,DC=hrm,DC=lan
>
>                Last replication recieved from SKYNET at
> 2004-08-08 04:52:19.
>
>             DC=hh,DC=hrm,DC=lan
>
>                Last replication recieved from SKYNET at
> 2004-08-08 05:01:03.
>
>          ......................... NT_SERVER passed test
> Replications
>
>       Starting test: NCSecDesc
>
>          ......................... NT_SERVER passed test
> NCSecDesc
>
>       Starting test: NetLogons
>
>          ......................... NT_SERVER passed test
> NetLogons
>
>       Starting test: Advertising
>
>          ......................... NT_SERVER passed test
> Advertising
>
>       Starting test: KnowsOfRoleHolders
>
>          ......................... NT_SERVER passed test
> KnowsOfRoleHolders
>
>       Starting test: RidManager
>
>          ......................... NT_SERVER passed test
> RidManager
>
>       Starting test: MachineAccount
>
>          ......................... NT_SERVER passed test
> MachineAccount
>
>       Starting test: Services
>
>          ......................... NT_SERVER passed test
> Services
>
>       Starting test: ObjectsReplicated
>
>          ......................... NT_SERVER passed test
> ObjectsReplicated
>
>       Starting test: frssysvol
>
>          ......................... NT_SERVER passed test
> frssysvol
>
>       Starting test: frsevent
>
>          ......................... NT_SERVER passed test
> frsevent
>
>       Starting test: kccevent
>
>          ......................... NT_SERVER passed test
> kccevent
>
>       Starting test: systemlog
>
>          An Error Event occured.  EventID: 0xC0002715
>
>             Time Generated: 08/17/2004   16:30:01
>
>             Event String: DCOM got error "%1058"
> attempting to start the
>
>          ......................... NT_SERVER failed test
> systemlog
>
>       Starting test: VerifyReferences
>
>          ......................... NT_SERVER passed test
> VerifyReferences
>
>
>
>    Running partition tests on : DomainDnsZones
>
>       Starting test: CrossRefValidation
>
>          ......................... DomainDnsZones passed
> test CrossRefValidation
>
>
>
>       Starting test: CheckSDRefDom
>
>          ......................... DomainDnsZones passed
> test CheckSDRefDom
>
>
>
>    Running partition tests on : ForestDnsZones
>
>       Starting test: CrossRefValidation
>
>          ......................... ForestDnsZones passed
> test CrossRefValidation
>
>
>
>       Starting test: CheckSDRefDom
>
>          ......................... ForestDnsZones 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 : hrm
>
>       Starting test: CrossRefValidation
>
>          ......................... hrm passed test
> CrossRefValidation
>
>       Starting test: CheckSDRefDom
>
>          ......................... hrm passed test
> CheckSDRefDom
>
>
>
>    Running enterprise tests on : hrm.lan
>
>       Starting test: Intersite
>
>          ......................... hrm.lan passed test
> Intersite
>
>       Starting test: FsmoCheck
>
>          ......................... hrm.lan passed test
> FsmoCheck
>
>
>
> Seems the first and last servers have the most errors.
> Not sure where to go from here.


Relevant Pages

  • RE: DNS/Active Directory Issue
    ... PASS - All the DNS entries for DC are registered on DNS server ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ... The File Replication Service SYSVOL ready test ...
    (microsoft.public.windows.server.general)
  • Re: frsevent error after promoting to a domain controller
    ... I restarted the file replication server and the errors went away. ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ... Starting test: CheckSDRefDom ...
    (microsoft.public.windows.server.active_directory)
  • RE: System cannot log you on error
    ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ... Starting test: CheckSDRefDom ... No network provider accepted the given network path.. ...
    (microsoft.public.windows.terminal_services)
  • Re: One way communication with DCs
    ... > The File Replication Service is having trouble enabling ... > Starting test: CrossRefValidation ... > Starting test: CheckSDRefDom ... > Running partition tests on: ...
    (microsoft.public.win2000.active_directory)
  • RE: System cannot log you on error
    ... retrieve the ... Running partition tests on: ForestDnsZones ... Starting test: CrossRefValidation ... Starting test: CheckSDRefDom ...
    (microsoft.public.windows.terminal_services)