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.
Push thread was requested for a range of records but could not find any in the range. This is a serious error. Make sure the time intervals are set properly. If the tombstone interval & timeout intervals are not correct (i.e. too small -- being << the replication interval), the above condition is possible. This is because the records might get changed into tombstones and then deleted before the remote WINS can pull them. In the same vein, if the refresh interval is set to be << replication interval then the records could get released before a WINS can pull them (a released record is not sent).
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the WINS service?
Make sure the latest service pak is installed.
1.) Stop WINS services on the problematic server.
2.) Go to winnt\system32\wins folder
3.) Backup all files in this folder to a location of your choice.
4.) Delete all files in this folder.
5.) Start WINS services
This fixed the issue with a Win2k server in mix-mode running WINS replication with two other Domains that are trusted and trusting WinNT 4.0 servers.
As per Microsoft: "If the tombstone interval and timeout intervals are not correct (for example, , too small; being significantly less than the replication interval), this error occurs. This is because the records might get changed into tombstones and then deleted before the remote WINS can pull them. In the same way, if the refresh interval is set at too great of a replication interval, the records could get released before a WINS can pull them (a released record is not sent)". See MSW2KDB for information about this event.
This error appeared after I enabled the Database Verification. The problem was that the Database Verification started at the the same time as the Push/Pull Replication. After changing the start time of the Database Verification this event no longer occurred.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated