Windows 7
- 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 ...
- 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 ...
- WINS could not get information about the SPEC_GRP_MASKS key. Check to see if the permissions on the key are set properly, ...
- WINS could not initialize properly with the security subsystem. At initialization, WINS creates a security object and attaches ...
- WINS could not initialize the administrator interface because of a problem with the Remote Procedure Call (RPC) service. ...
- WINS could not look up the association block for a NetBIOS over TCP/IP (NetBT) association. Check to see if the message read ...
- WINS could not open a Pull subkey. Check to see if the permissions on the key are set properly, system resources are low, ...
- WINS could not open a Push subkey. Check to see if the permissions on the key are set properly, system resources are low, ...
- WINS could not open the log file. Check the log path specified in the registry under WINS\Parameters\LogFilePath and restart ...
- WINS could not properly set up the WINS database. Look at the application log for errors from the Exchange component, ESENT. ...
- 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 ...
- 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 ...
- WINS encountered a PnP failure that caused it to terminate. The error code is contained in the second word of the data section. ...
- WINS encountered an error while deleting one or more records of a WINS. The WINS address is in the second DWORD in data section. ...
- WINS encountered an error while processing a push trigger or update notification. The error code is given in the data section. ...
- 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 ...
- WINS is trying to update the version number of a database record that it does not own. This is a serious error if the WINS ...
- WINS just did a consistency check on the records owned by the WINS with the address, %1. The number of records inserted, ...
- WINS performed a consistency check on the records. The number of records pulled, The address of the WINS whose records were ...
- WINS Pull thread encountered an error during the process of sending a push notification to another WINS. The error code is ...
- WINS pulled records from a WINS while doing %1. The partner's address and the owner's address whose records were pulled are ...
- WINS received a release for the non-owned name, %1. This name is owned by the WINS whose owner ID is given in the data section. ...
- WINS received a replica whose state is incorrect. For example, the state may be RELEASED or the replica might be an Internet ...
- WINS received an error while registering replicas. It will not register any additional replicas of this WINS at this time ...
- WINS received an error while trying to register a group's replica with name, %1. The replica is owned by the WINS with the ...
- WINS received an error while trying to register a unique replica with name %1. The replica is owned by WINS with address ...
- WINS Reverse Lookup Received/sec is the average number of WINS reverse lookup requests received by the server in each second. ...
- WINS sent a name query or a name release with a certain transaction ID. It received a response to the request that differed ...
- WINS was forced to scavenge replica tombstones of a WINS. The person with administrative rights on the computer forced the ...
- WINS will not start because the existing WINS database needs to be converted to the Windows 2000 format. WINS has initiated ...
- WINS's Replicator could not find any records in the WINS database. This means there are no active or tombstone records in ...
- WinSAT cannot obtain accurate measurements inside of a virtual machine. Please try again running directly on the native hardware. ...
- Winsock Catalog Provider Entry - Entry Type: %1!s! Description: %2!s! Provider ID: %3!s! Provider Path: %4!s! Catalog Entry ...
- WinSock startup successful : wVersion = %d.%d, wHighVersion = %d.%d vendorInfo addr = x, maxSockets = %d, maxudp = %d (0's ...
- Wired 802.1X Authentication failed. Network Adapter: %2 Interface GUID: %1 Peer Address: %3 Local Address: %4 Connection ...
- Wired 802.1X Authentication succeeded. Network Adapter: %2 Interface GUID: %1 Peer Address: %3 Local Address: %4 Connection ...
- Wired Network Policy Administration. Manage Wired Auto Configuration settings and IEEE 802.3 Security Settings for IEEE 802.3 ...
- Wireless 802.1x authentication failed. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS ...
- Wireless 802.1x authentication started. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS ...
- Wireless 802.1x authentication succeeded. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS ...
- Wireless 802.1x authentication was restarted. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: ...
- Wireless association to this network failed. Windows did not receive any response from the wireless router or accesspoint. ...
- Wireless authentication failed. 3rd party wireless service required for this connection is not responding. Vendor identification ...
- Wireless connection attempt to "%ws" is taking longer than normal to complete The wireless router or access point keeps restarting ...
- Wireless connection attempt to "%ws" is taking longer than normal to complete This might be because the wireless (802.1X) ...
- Wireless connection attempt to "%ws" is taking longer than normal to complete Wireless authentication is experiencing timeouts. ...
- Wireless IHV security failed. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS Type: %5 ...
- Wireless IHV security started. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS Type: %5 ...
- Wireless IHV security succeeded. Network Adapter: %1 Interface GUID: %2 Local MAC Address: %3 Network SSID: %4 BSS Type: ...
- Wireless LAN (WLAN) Service configures and starts the WLAN AutoConfig service, regardless of whether the computer has any ...