WINS could not do a consistency check on the records. This could be because WINS was directed to do the consistency check only with replication partners and it currently does not have any pull replication partners. To get around this problem, you should either allow WINS to do consistency check with owner WINSs or configure the WINS with one or more pull partners.
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 ...
WINS could not do a consistency check on the records. This could be because WINS was directed to do the consistency check ...
WINS could not get information about a key. Check to see if the permissions on the key are set properly, system resources ...
WINS could not get information about the DATAFILES key. Check to see if the permissions on the key are set properly, system ...
WINS could not get information about the Pull key. Check to see if the permissions on the key are set properly, system resources ...
WINS could not get information about the Push key. Check to see if the permissions on the key are set properly, system resources ...