Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The DNS server has completed a scavenging cycle but no nodes were visited. Possible causes of this condition include:
1) No zones are configured for scavenging by this server.
2) A scavenging cycle was performed within the last 60 minutes.
3) An error occurred during scavenging.
The next scavenging cycle is scheduled to run in 0 hours.
The event data will contain the error code if there was an error during the scavenging cycle.
|English: Request a translation of the event description in plain English.|
When you right-click a DNS server in the DNS snap-in, and press Scavenge Stale Resource Records, your DNS Server event log might record this event. See "JSI Tip 8156" for more information on this event.
See ME942923 for additional information about this event.
As per Microsoft: "This behavior occurs if you try to manually scavenge a DNS zone that supports dynamic updates immediately after you enable scavenging. You cannot scavenge the zone until the date and the time in the The zone can be scavenged after box is reached. If you try to manually scavenge the records before this date and time, the event ID 2502 message is logged. To work around this behavior, we recommend that you wait until the date and time that is defined in the The zone can be scavenged after box is reached before you start scavenging". See ME842463 for more details.
|Private comment: Subscribers only. See example of private comment|
|Links: ME842463, ME942923, JSI Tip 8156|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated