WINS could not come up because the existing WINS database needs conversion to the Windows 2000 format. If this is the first invocation of WINS after an upgrade from NT3.51, first, you need to run the convert utility (upg351db.exe in the %%SystemRoot%%\system32 directory) on the WINS database to convert it to the NT 4.0 database format. Then, you need to run the convert utility (edbutil.exe in the %%SystemRoot%%\system32 directory) on the converted 4.0 WINS database to convert it to the Windows 2000 database format. Once you have done that, you should restart WINS.
WINS adjusted the scavenging related time interval, %1, so that it is compatible with the replication time intervals. The ...
WINS adjusted the scavenging related time interval, %1. The adjusted value for this scavenging parameter is given in the ...
WINS cannot start because the existing WINS database needs conversion to the Windows 2000 format. WINS has initiated the ...
WINS could not close an open key. Check to see if the permissions on the key are set properly, system resources are low, ...
WINS could not come up because the existing WINS database needs conversion to the Windows 2000 format. If this is the first ...
WINS could not create a heap because of a resource shortage. Check to see if the computer is running short of virtual memory. ...
WINS could not create the TCP socket for listening to TCP connections. Make sure the TCP/IP driver is installed and running ...
WINS could not create the TCP socket for making a TCP connection. Make sure the TCP/IP stack is installed and running properly. ...
WINS could not create the User Datagram Protocol (UDP) socket to listen for Connection notification messages sent by another ...