Skip to content Skip to sidebar Skip to footer
Home / Dcdiag Uncaught Exception Faised Continuing Search

Dcdiag Uncaught Exception Faised Continuing Search

Post a Comment

locked

DCDIAG will not run tests RRS feed

  • Question

  • When I run DCDIAG /c from any of our 7 DC's or from my desktop and specify a DC, I get the following:

    C:\Windows\System32>dcdiag /c

    Directory Server Diagnosis

    Performing initial setup:
    Trying to find home server...
    Home Server = WAUSTU01
    * Identified AD Forest.

    C:\Windows\System32>

    I've tried multiple users that are Domain Admins and Enterprise Admins.  When I run the AD Replication Status Tool everything comes back as good.

All replies

  • What operating system?

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

  • My bad:

    Servers: 2012 R2
    Domain Functionality 2012 R2

  • Make sure you run elevated;  right-click Command Prompt, and then click Run as administrator, also try piping it to a text file to see if more info is returned;

    dcdiag >C:\diag.txt

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

  • Correct, I am running it as administrator and when I pipe it to a text file it outputs the same as what shows in the command line when it is not piped.

  • when I pipe it to a text file it outputs the same as what shows in the command line when it is not piped.

    with no switches, right?

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

  • I've tried executing individual tests and with the /c which should execute all tests.

  • Have not heard this one. Might try checking system and servicing health;

    sfc /scannow

    dism /online /cleanup-image /restorehealth

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

  • I just ran those commands and sfc had no integrity violations and the dism completed.  Same results.

  • Might also try as a test standing up a new one, patch it fully, join existing domain, add active directory domain services, promo it, and again try running tests.

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

  • When I run DCDIAG /c from any of our 7 DC's or from my desktop and specify a DC, I get the following:

    C:\Windows\System32>dcdiag /c

    Directory Server Diagnosis

    Performing initial setup:
    Trying to find home server...
    Home Server = WAUSTU01
    * Identified AD Forest.

    C:\Windows\System32>

    I've tried multiple users that are Domain Admins and Enterprise Admins.  When I run the AD Replication Status Tool everything comes back as good.

    /c

    Comprehensive. Runs all tests except DCPromo and RegisterInDNS, including non-default tests. Optionally, can be used with /skip to skip specified tests. The following tests are not run by default: Topology CutoffServers OutboundSecureChannels

    So what is the results for run "dcdiag" and "repadmin /replsum"...

    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

  • C:\Windows\System32>repadmin /replsum
    Replication Summary Start Time: 2017-06-23 16:38:49

    Beginning data collection for replication summary, this may take awhile:
    ...........

    Source DSA          largest delta    fails/total %%   error
    XXXFIL1                   09m:53s    0 /   5    0
    XXXFIL1                   11m:11s    0 /   5    0
    XXXFIL1                   11m:11s    0 /   5    0
    XXXFIL1                   11m:11s    0 /   5    0
    XXXDC3                    41m:11s    0 /  25    0
    XXXSTU01                  39m:53s    0 /  15    0

    Destination DSA     largest delta    fails/total %%   error
    XXXFIL1                   05m:00s    0 /   5    0
    XXXRODC1                  08m:07s    0 /   5    0
    XXXFIL1                   01m:48s    0 /   5    0
    XXXFIL1                   14m:08s    0 /   5    0
    XXXFIL1                   10m:14s    0 /   5    0
    XXXDC3                    39m:54s    0 /  10    0
    XXXRODC1                  07m:00s    0 /   5    0
    XXXSTU01                  41m:12s    0 /  20    0

    C:\Windows\System32>

    C:\Windows\System32>dcdiag

    Directory Server Diagnosis

    Performing initial setup:
       Trying to find home server...
       Home Server = WAUSTU01
       * Identified AD Forest.

    C:\Windows\System32>


    • Edited by Tuesday, June 27, 2017 6:59 PM Privacy

  • run "dcdiag /fix" then restart "netlogon" service,and try again.(also run dcdiag from other dc's.)

    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

  • dcdiag /fix did not fix the issue either and I ran it on the other DC's followed by a netlogon service restart.  The output for dcdiag /fix was the same as dcdiag.

  • I'd check the user is a member of \domain admins group

    whoami /groups

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

  • I've tried multiple domain admin accounts with the same results.

    Thanks,

    Ross

  • Hi,
    Do the 7 DCs get the same build for windows server 2012R2 to install? Not sure if there is something wrong in the OS build, in my opinion, you could install another fresh system by downloading a new build and test it again to see if the same error occurs.
    Best regards,
    Wendy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

  • They are not all built off the same image and we just created from ISO and promoted 2 of the DC's within the last month.

  • Might also try from a desktop with RSAT

    https://www.microsoft.com/en-us/download/details.aspx?id=7887

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Proposed as answer by Wendy Jiang Monday, July 3, 2017 3:06 PM
    • Unproposed as answer by fzr600vw Monday, July 10, 2017 3:12 PM

  • I've tried multiple domain admin accounts with the same results.

    Thanks,

    Ross

    I'd still confirm it

    whoami /groups

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    • Proposed as answer by Wendy Jiang Monday, July 3, 2017 3:06 PM
    • Unproposed as answer by fzr600vw Monday, July 10, 2017 3:12 PM

  • I ran whoami /groups and it confirmed the following:

    Domain Admins

    Schema Admins

    Enterprise Admins

  • I have also tried from a desktop and get the same results.

  • Hi,

    I suspect there is some DNS config issue in your environment, as DCDIAG will check the AD DC DNS and verify the records.

    Can you check the DNS state and whether you can resolve DC's FQDN?

    I would also suggest setup a Desktop with new Windows RSAT on it and try it.

    version of DCDiag.exe on my Lab server is 6.3.9600.17031 , can you please confirm your DCDiag version on the DC?

    Also if you have Antivirus software installed I would exclude dcdiag.exe to be scanned.

    Check your event logs and there should be errors logged.

    Regards, Jim MSCS - MCP Disclaimer: This posting is provided AS IS with no warranties or guarantees , and confers no rights. When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer

  • The FQDNs resolve for all DC's.

    The version on the DC is the same version you listed.  The version on the desktop I tried is:
    10.0.10585.0

    Anti-virus has been disabled

    I looked at the different event logs and there isn't anything referring to DCDIAG.

    Thanks,

    Ross

  • Hi,

    We all have listed multiple options that would help in any situation, but seems like your issue will require Microsoft premier support. Can you raise a case with your local MS representative on this issue?

    Regards, Jim MSCS - MCP Disclaimer: This posting is provided AS IS with no warranties or guarantees , and confers no rights. When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer

  • When I run DCDIAG /d I get the following:

    Directory Server Diagnosis

    Performing initial setup:
    Trying to find home server...
    * Verifying that the local machine server1, is a Directory Server.
    Home Server = server1
    * Connecting to directory service on server server1.
    server1.currentTime = 20170710184259.0Z
    server1.highestCommittedUSN = 12033660
    server1.isSynchronized = 1
    server1.isGlobalCatalogReady = 1
    * Identified AD Forest.
    Collecting AD specific global data
    * Collecting site info.
    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=domainname,DC=EDU,LDA
    P_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
    The previous call succeeded
    Iterating through the sites
    Looking at base site object: CN=NTDS Site Settings,CN=xxxxcer,CN=Sites,CN=Con
    figuration,DC=domainname,DC=EDU
    Getting ISTG and options for the site
    Looking at base site object: CN=NTDS Site Settings,CN=xxxxord,CN=Sites,CN=Con
    figuration,DC=domainname,DC=EDU
    Getting ISTG and options for the site
    Looking at base site object: CN=NTDS Site Settings,CN=xxxxxerg,CN=Sites,CN=
    Configuration,DC=domainname,DC=EDU
    Getting ISTG and options for the site
    Looking at base site object: CN=NTDS Site Settings,CN=xxxo,CN=Sites,CN=Conf
    iguration,DC=domainname,DC=EDU
    Getting ISTG and options for the site
    Looking at base site object: CN=NTDS Site Settings,CN=xxxxxps,CN=Sites,CN=Co
    nfiguration,DC=domainname,DC=EDU
    Getting ISTG and options for the site
    Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name
    ,CN=Sites,CN=Configuration,DC=domainname,DC=EDU
    Getting ISTG and options for the site
    Looking at base site object: CN=NTDS Site Settings,CN=domainnameGuest,CN=Sites,CN=Co
    nfiguration,DC=domainname,DC=EDU
    Getting ISTG and options for the site
    * Identifying all servers.
    Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=domainname,DC=EDU,LDA
    P_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
    The previous call succeeded....
    The previous call succeeded
    Iterating through the list of servers
    Getting information for the server CN=NTDS Settings,CN=server4,CN=Servers,CN=D
    efault-First-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=EDU
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=server7,CN=Servers,CN=
    xxxo,CN=Sites,CN=Configuration,DC=domainname,DC=EDU
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=server3,CN=Servers,CN
    =Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domainname,DC=EDU
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=server2,CN=Servers,CN=
    xxxxxps,CN=Sites,CN=Configuration,DC=domainname,DC=EDU
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=server1,CN=Servers,CN=
    xxxxcer,CN=Sites,CN=Configuration,DC=domainname,DC=EDU
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=server7,CN=Servers,CN=
    xxxxord,CN=Sites,CN=Configuration,DC=domainname,DC=EDU
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=server5,CN=Servers,CN
    =domainnameGuest,CN=Sites,CN=Configuration,DC=domainname,DC=EDU
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    Server is an RODC
    All the info for the server collected
    Getting information for the server CN=NTDS Settings,CN=server6,CN=Servers,CN
    =domainnameGuest,CN=Sites,CN=Configuration,DC=domainname,DC=EDU
    objectGuid obtained
    InvocationID obtained
    dnsHostname obtained
    site info obtained
    Server is an RODC
    All the info for the server collected
    server1.currentTime = 20170710184259.0Z
    server1.highestCommittedUSN = 12033660
    server1.isSynchronized = 1
    server1.isGlobalCatalogReady = 1
    * Identifying all NC cross-refs.
    DcDiag: uncaught exception raised, continuing search

  • Hi,
    Agree with Jim, as the problem is limited on further troubleshooting now, maybe, you could have a try opening up a case with Microsoft Technical Support to see if they could get more information regarding this problem: https://www.microsoft.com/en-us/worldwide.aspx
    Best regards,
    Wendy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Wendy Jiang Friday, July 21, 2017 12:24 PM

  • I started a case with Microsoft...unfortunately it hasn't be very productive.  I'll update with any results.

  • I know this is old but did you ever figure this out? Seeing the exact same issue here on a pair of 2016 DCs.

  • I know this is old but did you ever figure this out? Seeing the exact same issue here on a pair of 2016 DCs.

    I'd start a new thread.

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

manningbutervirty.blogspot.com

Source: https://social.technet.microsoft.com/Forums/windowsserver/en-US/34a797f5-b6a6-413d-8a96-9e5e44cd8d7f/dcdiag-will-not-run-tests

Post a Comment for "Dcdiag Uncaught Exception Faised Continuing Search"