Troubleshoot AppInsight for Active Directory

This topic describes issues you may encounter when using AppInsight for Active Directory in SAM.

Be sure to review AppInsight for Active Directory requirements and permissions. Click here for details on the AppInsight for Active Directory template.

Issue: AppInsight for Active Directory widgets do not display polled data.

After configuring AppInsight for Active Directory, you may not see active data in widgets or receive alerts immediately because polling may occur at different intervals, ranging from minutes to hours. After 24 hours, widgets and alerts should start reporting data.

The default polling interval for AppInsight for Active Directory is 10 minutes.

You can also check AppInsight for Active Directory logs located in this default location: c:\ProgramData\SolarWinds\Logs\APM\ApplicationLogs.

Issue: Node status does not appear in AppInsight for Active Directory widgets, and Active Directory widgets display IP addresses instead of node names.

To ensure that node status appears in AppInsight for Active Directory widgets with proper node names, configure nodes to support both WMI and ICMP polling. ICMP-only nodes cannot supply DNS or SysName values required to compute replications for destination domain controller FQDN names. See this article in the SolarWinds Success Center for details.

Issue: Domain controllers display "Unknown" for several custom performance counters.

Check the server to make sure the Windows NT Directory Service (NTDS) category of performance counters is present. If the base set of performance counters libraries was corrupted, you may need to rebuild it.

Issue: Components display Unknown status after initial poll.

Generic application monitors like Windows Event Log Monitor and Performance Counter Monitor may have an Unknown status after the first round of polling. Wait 10 minutes for the next successful poll.

If the status of a domain controller remains Unknown after polling, make sure that a node exists for the domain controller and that AppInsight for Active Directory is assigned to the node. See Configure AppInsight for Active Directory.

Issue: After enabling Total counters in the AppInsight for Active Directory template, the AppInsight for Active Directory application appears Down and warnings occur in SAM logs.

Restart the Orion Collector service to clear its cache. See Enable total counters for details.

Issue: Domain Controllers display Unknown status in AppInsight for Active Directory widgets.

Make sure the node is being monitored and that the AppInsight for Active Directory template is assigned to the node. See Configure AppInsight for Active Directory.

Issue: AppInsight for Active Directory applications appear Down and warnings occur in logs after enabling and later disabling the Total Counters feature in the template

You can edit the AppInsight for Active Directory template to enable the Total Counters feature. If you decide to disable the feature again later, AppInsight for Active Directory applications may incorrectly display as Down and warnings may appear in SAM logs. Enabling and disabling components for AppInsight applications can also place the Orion Collector service in an unsynchronized state.

Use the Orion Service Manager to restart the Orion Collector service to clear its cache.

Issue: The Replication widget shows only a few domain controllers.

The Replication widget displays domain controllers (shown on the right, below) that replicate with the monitored domain controller (shown on the left) in the same domain, by design.

Issue: The Trust Summary widget does not display expected data.

If expected data does not appear in the Trust Summary widget, here are some ways to investigate:

  • Navigate to My Dashboards > Applications > Active Directory to check the status of the AppInsight for Active Directory application.
  • Verify that domain controllers are assigned the Global Catalog (GC) role. You can use PowerShell to check if the IsGlobalCatalog flag is set to True:

      Get-ADDomainController-Filter {Site-eq 'Default-First-Site-Name'}} | FT Name,IsGlobalCatalog

      Get-ADDomainController | ft Name,IsGlobalCatalog

  • Verify that domain controllers configured as GC servers use port 3268, the default port to collect trust data. If your domain controllers use port 3269 instead, update that setting in the AppInsight for Active Directory template.
  • Check SAM logs and AppInsight for Active Directory logs located in this default location: c:\ProgramData\SolarWinds\Logs\APM\ApplicationLogs.