In this article:
Issue description
Possible causes
Prerequisites
Resolution
Related topics and articles
How to reach support
Issue description
This issue occurs when ADAudit Plus is unable to collect logs related to policy changes auditing. This can be due to configuration issues, permission restrictions, or missing audit policies.
Prerequisites
Ensure the monitored server is added and configured in ADAudit Plus.
The ADAudit Plus service account must have the necessary permissions to read security event logs.
Required RPC ports (135, 49152-65535) must be open bidirectionally or at least inbound on the target server.
Confirm that the required audit policies are enabled to track Policy Changes events.
Ensure the event log size is set to at least 4GB to prevent log overwrites.
Possible causes
Insufficient or incorrect audit policies: ADAudit Plus may lack the necessary audit policies to ensure that events are logged whenever any activity occurs.
Desired events are not getting logged: The required Event IDs are not being captured on Windows Domain Controllers, Windows servers, and workstations.
Incorrect search criteria: The specified search criteria for the required data may be incorrect.
Unable to log events to the security log (Event ID 521): Arises when the security event log fails to log events.
Log collection failure: This might be due to Access Denied/RPC service unavailable error messages, preventing ADAudit Plus from collecting logs.
Resolution
Step 1: Verify audit policy configuration
Log in to a system with Group Policy Management Console (GPMC) using Domain Admin credentials.
Open GPMC and navigate to:
Default Domain Controllers Policy (if managing domain accounts)
ADAuditPlusMSPolicy
Right-click the relevant policy > Edit > Computer Configuration > Policies > Windows Settings > Security Settings > Advanced Audit Policy Configuration > Audit Policy, and double-click the relevant policy setting.
Navigate to the right pane and right-click the relevant Subcategory, and then click Properties and select Success, Failure, or both, as directed below:
Category | Subcategory | Audit events | Purpose |
Policy Change | Audit Policy Change | Success and Failure | Audit policy auditing |
Step 2: Ensure desired events are logged
Log in with domain admin credentials.
Open Event Viewer (eventvwr.msc) and navigate to Windows Logs > Security.
Verify that the following event IDs are present:
Event ID 4719: Policy change events.
Event ID 4718: User rights removed
Event ID 4717: System audit policy was changed.
Step 3: Verify search criteria
Click the Server Audit tab > Policy Changes.
Choose the Report and select the Domain.
Set the Period (e.g., Today, Yesterday, This Week, This Month). Define a custom period if needed.
Choose the required hours and select the objects for which you need the report.
Step 4: Resolve Event ID 521: Failure to write events to the Security Log
Since ADAudit Plus relies on Event Viewer, it retrieves events from there. A high number of Event ID 521 entries may indicate an issue with event logging.
Restart the Windows Event Log service.
Restart the affected server.
Check security log retention settings:
Ensure the maximum log size is sufficient and set to overwrite as needed.
Step 5: Address log collection failures
Fix Access Denied/RPC Service Unavailable errors preventing log collection.
Ensure RPC ports (135 and dynamic range 49152-65535) are open in the firewall.
If you receive the error A security package specific error occurred, this is due to conflicting IP addresses with the same SPN for multiple machines. Ensure that:
The domain controller showing the error has forward and reverse lookup entries in DNS.
Related topics and articles
When and how to contact support
If the No Data Available error persists after verifying configurations.
If the report shows repeated failures or retrieval errors.
If the dashboard continues to display incorrect or no data despite troubleshooting.
If you suspect a bug in ADAudit Plus.