WINS could not start due to a missing or corrupt database. Restore the database using WINS Manager (or winscl.exe found in the Windows 2000 Resource Kit) and restart WINS. If WINS still does not start, begin with a fresh copy of the database. To do this: 1) Delete all the files in the %%SystemRoot%%\system32\WINS directory. NOTE: If the WINS database file (typically named wins.mdb) is not in the above directory, check the registry for the full filepath. Delete the .mdb file. NOTE: If jet*.log are not in the above directory, check the registry for the directory path. Delete all log files 2) Restart WINS.
WINS could not read the UseRplPnrs value of the Wins\Parameters\ConsistencyCheck key. If this value is set to a non-zero ...
WINS could not start because of a database error. WINS restored the old database from the backup directory and will come ...
WINS could not start because the existent database must be converted to the Windows 2000 format. If this is the first invocation ...
WINS could not start because the existing database needs to be converted to the Windows 2000 format. If this is the first ...
WINS could not start due to a missing or corrupt database. Restore the database using WINS Manager (or winscl.exe found in ...
WINS could not update the Owner ID-to-Address mapping table in the database. This means the in-memory table that maps to ...
WINS created a socket and called the 'bind' WinSock API to bind a handle to it. On calling 'getsockname' to determine the ...
WINS did not send a notification message to the WINS server whose address is given in the data section. There were a number ...
WINS encountered a database error. This may or may not be a serious error. WINS will try to recover from it. You can check ...