The Push Thread was requested for a range of records but could not find any records in the range. Make sure that the replication time intervals are set properly. If the tombstone interval and timeout intervals are not correct (that is, much less than 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. Similarly, if the refresh interval is set to be much less than the replication interval then the records could get released before a WINS can pull them (a released record is not sent). Make sure that the replication time intervals are set properly.

Details
Product:	Windows Operating System
Event ID:	4227
Source:	Wins
Version:	5.0
Component:	System Event Log
Symbolic Name:	WINS_EVT_CANT_FIND_ANY_REC_IN_RANGE
Message:	The Push Thread was requested for a range of records but could not find any records in the range. Make sure that the replication time intervals are set properly. If the tombstone interval and timeout intervals are not correct (that is, much less than 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. Similarly, if the refresh interval is set to be much less than the replication interval then the records could get released before a WINS can pull them (a released record is not sent). Make sure that the replication time intervals are set properly.

Explanation
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).

User Action
To check and correct WINS interval settings: 1. Open Administrative Tools and then open WINS. 2. On the server in question, expand the server information. 3. Right click Registration Partners, and then click Properties. 4. Verify that the settings are correct. 5. Make any necessary corrections. For assistance, contact the person with administrative rights on this computer.

WINS was forced to scavenge replica tombstones of a WINS. The person with administrative rights on the computer forced the scavenging using winscl.exe. WINS does not scavenge replica tombstones unless they have timed out and the WINS has been running for at least 3 days (This is to ensure that the tombstones have replicated to other WINSs). In this case, the tombstones were timed out but the WINS had not been up for 3 days. The replica tombstones were deleted. This deletion does not constitute a problem unless you have WINS servers that are primary and backup to clients but not both Push and Pull partners of each other. If you do have such WINSs, there is a low probability that this action will result in database inconsistency but if it does (as you will discover eventually), you can get back to a consistent state by initiating consistency checks usding winscl.exe. NOTE: The consistency check is a network and resource intensive operation, you should initiate it only with a full understanding of what it does. You are better off creating the ConsistencyCheck subkey under Wins\Parameters.
WINS could not read the UseRplPnrs value of the Wins\Parameters\ConsistencyCheck key. If this value is set to a non-zero (DWORD) value, WINS will do a consistency check of the owners in its database by going to one or more of its replication partners. If the owner of the records happens to be a replication partner, WINS will go to it, otherwise it will pick one at random. Set this value if you have a large number of WINSs in your configuration and/or if you do not want the local WINS to go to any WINS that is not a replication partner.
The File Replication Service is having trouble enabling replication from %1 to %2 for %3 using the DNS name %4. FRS will keep retrying. Following are some of the reasons you would see this warning. [1] FRS can not correctly resolve the DNS name %4 from this computer. [2] FRS is not running on %4. [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers. This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
Due to contention with the Certificate Services for resources- replication was stalled for %1 minutes- %2 seconds. It took an unusually long time to prepare an asynchronous replication message for transmission. This condition should be transient. If this issue persists, please contact Microsoft Product Support Services for assistance.
Internal event: The Directory Service processed the replication state information request with status code %1.

Related:

Leave a Reply Cancel reply

Links