Troubleshooting Failed Diagnostic Tests
This KB is intended for troubleshooting Diagnostic Tests with Failed results. If you encounter any errors displayed in the monitor that prevent the execution of Diagnostic tests, or if there is no data available for Diagnostic Tests, please refer this KB.
Follow the below steps to troubleshoot Failed Diagnostic Tests:
- Check the RCA for the Failed tests (From version 16630 onwards)
- Click on the red Health icon of the monitor to open the Root Cause Analysis pop-up window.
- Expand the Health status of the specific test that is down. (Example: Health of Distributed File System Check)
- Click on the Availability status of the specific test. (Example: Availability of Distributed File System Check)
- At the bottom of the same window, under the Root Cause Message heading you can find the reason why the specific test is down.
- Based on the displayed error, the customer can investigate the issue in their environment and resolve it.
- This can also be checked directly from the red Availability icon of the specific test in the Diagnostic Tests tab.
- Run the ADDiagnosticTests.ps1 script to check the full output from the AD server.
- Follow the steps in the KB article below to execute the script and review its output:
https://pitstop.manageengine.com/portal/en/kb/articles/active-directory-diagnostic-tests-error-in-specific-tests-only - Run direct command in the AD server.
- Open the administrative PowerShell on the relevant AD server.
- Execute the following command: dcdiag
- Review the output generated by the command.
Please note that we present the results exactly as received from the AD server. If customers encounter any issues related to the output from the AD server, they should either consult their own team or reach out to Microsoft for assistance.
Special Cases:
- In the event that the RID Master Accessibility Check fails in Applications Manager but passes when the direct command is executed on the AD server, please refer to the KB article provided below:
https://pitstop.manageengine.com/portal/en/kb/articles/error-for-rid-master-accessibility-check-only-in-applications-manager - Performance Polling:
- The Diagnostic Tests are mapped under Performance Polling which can be accessed through Settings -> Performance Polling -> Optimize Data Collection -> Monitor Type -> Active Directory -> Metric Name -> Table name.
- By default this is this is set to poll once every 60 minutes, although customers have the flexibility to modify this interval.
- If an alert is triggered by the Diagnostic Tests, and the error is resolved promptly upon checking direct commands, the Applications Manager will clear the alert only after the subsequent poll, following the polling settings.
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check prerequisites to be done Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...Troubleshooting Authentication Failed error
Authentication Failure Authentication failure occurs when the request to a resource is missing or has invalid credentials. Check if URL requires authentication Access the URL in an incognito/private window and check if any pop up asking for ...Active Directory Diagnostic Tests - Troubleshoot Errors in Specific test
In Active Directory Monitor, Diagnostic tests have been introduced in build 14040. To troubleshoot any errors in a specific test in the Diagnostic tests tab, follow the below steps: 1) Open Powershell in administrator mode in the machine ...Troubleshooting WinRM errors
This KB serves as a guide for troubleshooting errors when using the WinRM mode of data collection. First, ensure that all the following conditions are met: Refer to the below link and check if all the WinRM prerequisites have been completed properly ...Webpage Analyzer - Troubleshooting
Prerequisites: Web page which the customer want to monitor should be accessible from the Machine where the APM is installed. Check if the customer have configured any proxy for accessing the particular URL If yes, then the same proxy must be ...