FRSDiag Errors when trying to look for a domain controller that no longer exists

Discussion in 'Active Directory' started by eric giblock, Jul 29, 2004.

  1. eric giblock

    eric giblock Guest

    we had 3 domain controllers, demoted one (testing-1a) to
    a member server. so now we have 2 domain controllers (2a
    and 3a).

    from 2a, when i run the FRSDiag tool, i get the following
    error message. keep in mind that TESTING-1A is no
    longer a part of the network, and there is no references
    to the computer in DNS, or Active Directory anymore.

    Please help !?!

    --
    Eric Giblock





    ----------------------------------------------------------
    --
    FRSDiag v1.7 on 7/29/2004 3:05:41 PM
    ..\ACO-CHARDON-2A on 2004-07-29 at 3.05.41 PM
    ----------------------------------------------------------
    --

    Checking for errors/warnings in FRS Event Log .... passed
    Checking for errors in Directory Service Event Log ....
    passed
    Checking for minimum FRS version requirement ... passed
    Checking for errors/warnings in ntfrsutl ds ... passed
    Checking for Replica Set configuration triggers... passed
    Checking for suspicious file Backlog size... passed
    Checking Overall Disk Space and SYSVOL structure (note:
    integrity is not checked)... passed
    Checking for suspicious inlog entries ... passed
    Checking for suspicious outlog entries ... passed
    Checking for appropriate staging area size ... passed
    Checking NtFrs Service (and dependent services)
    state...passed
    Checking NtFrs related Registry Keys for possible
    problems...passed
    Checking Repadmin Showreps for errors...
    DC=aconet,DC=us
    Default-First-Site-Name\ACO-TESTING-
    1A\0ADEL:24a2ec59-7408-4f7e-adbe-8b59767f8117 via RPC
    objectGuid: ebfff3ef-3bb0-4aa6-9096-
    50a41bcd54f2
    Last attempt @ 2004-07-29 14:56.37
    failed, result 8524:
    The DSA operation is unable to
    proceed because of a DNS lookup failure.
    Last success @ 2004-07-27 11:08.03.
    58 consecutive failure(s).

    CN=Configuration,DC=aconet,DC=us
    Default-First-Site-Name\ACO-TESTING-
    1A\0ADEL:24a2ec59-7408-4f7e-adbe-8b59767f8117 via RPC
    objectGuid: ebfff3ef-3bb0-4aa6-9096-
    50a41bcd54f2
    Last attempt @ 2004-07-29 14:56.37
    failed, result 8524:
    The DSA operation is unable to
    proceed because of a DNS lookup failure.
    Last success @ 2004-07-27 11:01.18.
    58 consecutive failure(s).

    CN=Schema,CN=Configuration,DC=aconet,DC=us
    Default-First-Site-Name\ACO-TESTING-
    1A\0ADEL:24a2ec59-7408-4f7e-adbe-8b59767f8117 via RPC
    objectGuid: ebfff3ef-3bb0-4aa6-9096-
    50a41bcd54f2
    Last attempt @ 2004-07-29 14:56.37
    failed, result 8524:
    The DSA operation is unable to
    proceed because of a DNS lookup failure.
    Last success @ 2004-07-27 10:57.43.
    58 consecutive failure(s).

    ......... failed 3


    Final Result = failed with 3 error(s)
     
    eric giblock, Jul 29, 2004
    #1
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.