DCDiag Problems, Failed DC

Giganews Newsgroups
Subject: DCDiag Problems, Failed DC
Posted by:  Brian R (rober…@gmail.com)
Date: 18 Jul 2006

I upgraded my NT domain using a Temporary DC (NT4 Upgraded to Win2K3)
some time ago.  I brought a fresh DC up on a clean 2k3 install.  I
moved all the operations masters rolls to the new PC.  Shortly after
bringing the new DC online I had a complete failure of the drive on the
Temporary DC.  I have no backups of that machine and was not able to
bring it back online.  I'm preparing to install the first exchange
server on my network and I'm running DCDiag.  Some errors occured with
regards to the old DC.  The output is below, errors only of course.
I'd like to know if there is anything that can be done to fix my
directory w/o completely rebuilding it.  Any help would be greatly
appreciated

  Testing server: Default-First-Site-Name\NEWDC
      Starting test: Replications
        [Replications Check,NEWDC] A recent replication attempt
failed:
            From OLDDC to NEWDC
            Naming Context: DC=ForestDnsZones,DC=cooldomain,DC=com
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS
lookup failure.
            The failure occurred at 2006-05-17 09:19:31.
            The last success occurred at 2005-05-31 10:31:47.
            1 failures have occurred since the last success.
            The guid-based DNS name
55d59a3c-8dbb-4473-a36f-877dac3928c1._msdcs.cooldomain.com
            is not registered on one or more DNS servers.
        [OLDDC] DsBindWithSpnEx() failed with error 1722,
        The RPC server is unavailable..
        [Replications Check,NEWDC] A recent replication attempt
failed:
            From OLDDC to NEWDC
            Naming Context: DC=DomainDnsZones,DC=cooldomain,DC=com
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS
lookup failure.
            The failure occurred at 2006-05-17 09:19:31.
            The last success occurred at 2005-05-31 10:31:47.
            1 failures have occurred since the last success.
            The guid-based DNS name
55d59a3c-8dbb-4473-a36f-877dac3928c1._msdcs.cooldomain.com
            is not registered on one or more DNS servers.
        [Replications Check,NEWDC] A recent replication attempt
failed:
            From OLDDC to NEWDC
            Naming Context:
CN=Schema,CN=Configuration,DC=cooldomain,DC=com
            The replication generated an error (1722):
            The RPC server is unavailable.
            The failure occurred at 2006-07-18 07:49:42.
            The last success occurred at 2005-05-31 10:31:47.
            39634 failures have occurred since the last success.
            The source remains down. Please check the machine.
        [Replications Check,NEWDC] A recent replication attempt
failed:
            From OLDDC to NEWDC
            Naming Context: CN=Configuration,DC=cooldomain,DC=com
            The replication generated an error (1722):
            The RPC server is unavailable.
            The failure occurred at 2006-07-18 07:49:41.
            The last success occurred at 2005-05-31 10:31:47.
            39634 failures have occurred since the last success.
            The source remains down. Please check the machine.
        [Replications Check,NEWDC] A recent replication attempt
failed:
            From OLDDC to NEWDC
            Naming Context: DC=cooldomain,DC=com
            The replication generated an error (1722):
            The RPC server is unavailable.
            The failure occurred at 2006-07-18 07:49:28.
            The last success occurred at 2005-05-31 10:31:47.
            39634 failures have occurred since the last success.
            The source remains down. Please check the machine.
        REPLICATION-RECEIVED LATENCY WARNING
        NEWDC:  Current time is 2006-07-18 07:54:38.
            DC=ForestDnsZones,DC=cooldomain,DC=com
              Last replication recieved from OLDDC at 2005-05-31
10:31:47.
              WARNING:  This latency is over the Tombstone Lifetime of
60 days!
            DC=DomainDnsZones,DC=cooldomain,DC=com
              Last replication recieved from OLDDC at 2005-05-31
10:31:47.
              WARNING:  This latency is over the Tombstone Lifetime of
60 days!
            CN=Schema,CN=Configuration,DC=cooldomain,DC=com
              Last replication recieved from OLDDC at 2005-05-31
10:31:47.
              WARNING:  This latency is over the Tombstone Lifetime of
60 days!
            CN=Configuration,DC=cooldomain,DC=com
              Last replication recieved from OLDDC at 2005-05-31
10:31:47.
              WARNING:  This latency is over the Tombstone Lifetime of
60 days!
            DC=cooldomain,DC=com
              Last replication recieved from OLDDC at 2005-05-31
10:31:47.
              WARNING:  This latency is over the Tombstone Lifetime of
60 days!

      Starting test: KnowsOfRoleHolders
        Warning: OLDDC is the Schema Owner, but is not responding to
DS RPC Bind.
        [OLDDC] LDAP search failed with error 58,
        The specified server cannot perform the requested operation..
        Warning: OLDDC is the Schema Owner, but is not responding to
LDAP Bind.
        Warning: OLDDC is the Domain Owner, but is not responding to
DS RPC Bind.
        Warning: OLDDC is the Domain Owner, but is not responding to
LDAP Bind.
        ......................... NEWDC failed test KnowsOfRoleHolders

      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.
        ......................... NEWDC failed test frsevent

Replies