In this article:  

• Issue description

• Prerequisites

• Possible causes

• Resolution

• How to reach support

• Related topics and articles

Issue description  

Data is not being collected in real time from a specific server. The Last Event Fetched Time in the ADAudit Plus console indicates a future date, which suggests a time and date discrepancy on the source server.

Prerequisites  

• You must have Remote Desktop (RDP) access to the server experiencing the issue.

• You need permissions to view system settings and the Event Viewer on that server.

Possible causes  

• The date and time settings on the configured server were manually changed to a future date at some point, which generated events with future timestamps.

Resolution  

Follow these steps on the server that is reporting a future timestamp.

Step 1: Check the server's date and time settings  

1. Log in to the affected server via RDP.

2. Click the Start Menu and select Settings (the gear icon).

3. In the Settings window, click Time & Language.

4. Select the Date & time tab.

5. Review the current date, time, and time zone. If the date or time is set to the future, this is the cause of the issue. Correct the settings and restart the ADAudit Plus service.

Step 2: Verify the latest security event timestamp  

If the server's time in the settings appears to be correct now, you must check the latest event written to the security log to find the source of the future timestamp.

1. Press the Windows key + R to open the Run dialog.

2. Type eventvwr.msc and press Enter.

3. In the Event Viewer window, expand Windows Logs and select Security.

4. The events are listed in chronological order. Check the timestamp of the event at the very top of the list. This is the last recorded security event on the server.

5. If this timestamp is still in the future, it confirms that the server's clock was previously set incorrectly. The product will not collect new events until the system clock surpasses this future timestamp.

How to reach support  

If the server's current time is correct and the latest event in the security log does not have a future date, but ADAudit Plus still shows a future Last Event Fetched Time, please contact our support team. Provide screenshots of the server's date and time settings and the Event Viewer to help expedite the resolution.

Related topics and articles  

• What does "Last Event Read Time" in ADAudit Plus mean?