WINS has exceeded the wait time for all threads to terminate. The number of threads still active is given in the second DWORD of the data section. The thread that could be stuck is the replicator thread. It could be because of the other WINS being slow in sending data or reading data. The latter can contribute to back-pressure on the TCP connection on which it is trying to replicate. Check the partner WINSs to see if one or more is in a bad state. This WINS terminated itself abruptly.
WINS found a name in the WINS database with a length of more than 255 characters. The name was truncated to 17 characters. ...
WINS found some database corruption. The record named, %1, is corrupt. It could be that recovery from the last crash did ...
WINS has deleted records of a partner. The internal ID of the partner whose records were deleted, the minimum version number ...
WINS has encountered an error that caused it to shut down.The exception code is the second DWORD of the data section. Check ...
WINS has exceeded the wait time for all threads to terminate. The number of threads still active is given in the second DWORD ...
WINS has found some database corruption. It will try to recover. This recovery process can take a long time. Do not kill ...
WINS has received a PnP notification that the IP address of the server has changed. The old IP address and the new IP address ...
WINS is scavenging a chunk of N records in the version number range from X to Y. N, X and Y (low word, high word for version ...
WINS is scavenging the locally owned records from the database. The version number range that is scavenged is given in the ...