MM&M UG UK

 

The home of the Microsoft Messaging and Mobility

User Group in the UK.

Welcome to MM&M UG UK Sign in | Join | Help
in
Home Blogs Forums Photos Articles Links CESN Downloads Aggregated RSS

NEW dcdiag error

Last post 10-15-2008, 6:20 by nathanwinters. 1 replies.
Sort Posts: Previous Next
  •  10-08-2008, 14:39 25510

    NEW dcdiag error

    What do i do:


    Domain Controller Diagnosis

    Performing initial setup:
       Done gathering initial info.

    Doing initial required tests
      
       Testing server: Default-First-Site-Name\4DC
          Starting test: Connectivity
             ......................... 4DC passed test Connectivity

    Doing primary tests
      
       Testing server: Default-First-Site-Name\4DC
          Starting test: Replications
             [Replications Check,4DC] A recent replication attempt failed:
                From DC5 to 4DC
                Naming Context: CN=Schema,CN=Configuration,DC=1DC,DC=class
                The replication generated an error (1908):
                Could not find the domain controller for this domain.
                The failure occurred at 2008-10-08 12:47:04.
                The last success occurred at 2008-09-30 23:52:25.
                181 failures have occurred since the last success.
                Kerberos Error.
                A KDC was not found to authenticate the call.
                Check that sufficient domain controllers are available.
             [DC5] DsBindWithSpnEx() failed with error 1722,
             The RPC server is unavailable..
             [Replications Check,4DC] A recent replication attempt failed:
                From DC5 to 4DC
                Naming Context: CN=Configuration,DC=1DC,DC=class
                The replication generated an error (1908):
                Could not find the domain controller for this domain.
                The failure occurred at 2008-10-08 12:47:03.
                The last success occurred at 2008-10-01 00:16:48.
                237 failures have occurred since the last success.
                Kerberos Error.
                A KDC was not found to authenticate the call.
                Check that sufficient domain controllers are available.
             REPLICATION-RECEIVED LATENCY WARNING
             4DC:  Current time is 2008-10-08 13:46:00.
                CN=Schema,CN=Configuration,DC=1DC,DC=class
                   Last replication recieved from DC5 at 2008-09-30 23:52:25.
                CN=Configuration,DC=1DC,DC=class
                   Last replication recieved from DC5 at 2008-10-01 00:16:48.
             ......................... 4DC passed test Replications
          Starting test: NCSecDesc
             ......................... 4DC passed test NCSecDesc
          Starting test: NetLogons
             ......................... 4DC passed test NetLogons
          Starting test: Advertising
             ......................... 4DC passed test Advertising
          Starting test: KnowsOfRoleHolders
             ......................... 4DC passed test KnowsOfRoleHolders
          Starting test: RidManager
             ......................... 4DC passed test RidManager
          Starting test: MachineAccount
             ......................... 4DC passed test MachineAccount
          Starting test: Services
             ......................... 4DC passed test Services
          Starting test: ObjectsReplicated
             ......................... 4DC passed test ObjectsReplicated
          Starting test: frssysvol
             ......................... 4DC passed test frssysvol
          Starting test: frsevent
             ......................... 4DC passed test frsevent
          Starting test: kccevent
             ......................... 4DC passed test kccevent
          Starting test: systemlog
             An Error Event occured.  EventID: 0x00000457
                Time Generated: 10/08/2008   13:22:33
                (Event String could not be retrieved)
             ......................... 4DC failed test systemlog
          Starting test: VerifyReferences
             ......................... 4DC passed test VerifyReferences
      
       Running partition tests on : 4DC
          Starting test: CrossRefValidation
             ......................... 4DC passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... 4DC 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 : 1DC.class
          Starting test: Intersite
             ......................... 1DC.class passed test Intersite
          Starting test: FsmoCheck
             ......................... 1DC.class passed test FsmoCheck

  •  10-15-2008, 6:20 25534 in reply to 25510

    Re: NEW dcdiag error

    Hi,

    Perhaps you could give us some more details about your network?

    Cheers

    Nathan


    Nathan Winters - MVP Exchange Server
    MCSE & MCSA 2000 & 2003 + Messaging, MCITP Exchange 2007, MCP, VMWare VCP v2 & v3.

    Welcome to the Microsoft Messaging and Mobility User Group: http://www.mmmug.co.uk
View as RSS news feed in XML
Powered by Community Server, by Telligent Systems