| Event Id | 4164 |
| Source | wins |
| Description | 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. |
| Event Information | "According To Microsoft:" CAUSE: 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 Windows Internet Name Services). In this case, the tombstones timed out but the WINS had not been up for 3 days. The administrator forced the scavenging using winscl.exe to delete the replica tombstones. This deletion is not a problem unless you have WINS servers that are primary and backup to clients but not Push and Pull partners of each other. If you do have Windows Internet Name Services that are Push and Pull partners of each other, 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 using 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 entry under wins\Parameters. RESOLUTION: Read the replication information in the Windows 2000 Resource Kit to gain an understanding of this process. |
| Reference Links | Microsoft product: Windows Operating System Version: 5.0 Event Source: Wins Event ID: 4164 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.