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 existent database must be converted to the Windows 2000 format. If this is the first invocation of WINS after an upgrade  From NT3.51, you need to run the convert utility (upg351db.exe in the %%SystemRoot%%\system32 directory) on the WINS database to convert it to the new  database format. Once you have done that, you should restart WINS.

WINS could not read the ConsistencyCheck value (type DWORD) from the Parameters\ConsistencyCheck subkey in the registry. ... WINS could not read the MaxRecsAtATime value (type DWORD) in the Wins\Parameters\ConsistencyCheck subkey of the registry. ... 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 ...