After specifying report parameters such as scope, filters, or date range in ADManager Plus, the generated report may either show the message "No Reports Available" or contain only partial data. This issue affects the reliability of reporting functions, potentially hindering tasks like user activity audits, compliance verification, and account cleanup efforts, where complete and accurate data is essential.
Unreachable domain controller (DC): ADManager Plus is unable to connect to the DC due to network issues or the DC being offline.
Replication delays or failures: In multi-DC environments, inconsistent replication can lead to missing or outdated data.
Non-replicated attributes: Attributes like LastLogonTime are not replicated across all DCs, affecting specific report types.
Time synchronization mismatch: If the ADManager Plus server and DCs have significantly different system times, it can cause report filtering issues.
No matching data: The chosen report criteria may not match any available data in the given timeframe.
Insufficient permissions: The service account used by ADManager Plus lacks read permissions to retrieve the necessary data.
Incorrect scope selection: The report’s scope may not include the required organizational units (OUs) or objects.
Ensure administrative access to configure settings in ADManager Plus.
The service account configured in ADManager Plus must have read permissions to query the required AD objects and attributes.
Open Command Prompt on the ADManager Plus server.
Run ping <DomainController>.
If the DC is unreachable, troubleshoot network connectivity issues.
Log in to ADManager Plus.
Navigate to Directory/Application Settings > Active Directory.
Make sure all DCs in your environment are listed.
Run the following command to sync data manually:
Confirm that the system time on the ADManager Plus server and all DCs is synchronized.
Use a Network Time Protocol (NTP) server for accuracy.
Restart relevant services and retry report generation.
Note: Mismatch in system time beyond five minutes may result in trust failures or inaccurate filtering in date-based reports.
Ensure the configured service account has read permissions to all required AD objects and attributes.
Permissions should cover all relevant domains and OUs involved in the report.
Confirm that the scope selected during report setup includes OUs or domains that contain the expected data.
An incorrect scope may result in empty or partial reports.
Regularly monitor the health and connectivity status of all DCs.
Maintain consistent time synchronization across all servers using a trusted NTP source.