Windows Server WINS Event Log Messages, Part 1: Event ID 4096 to 4209


Summary


The text of WINS event log messages has been improved in Windows Server so that the messages are easier to understand. This article lists the revised event log messages for event ID 4096 to event ID 4209.

For additional information about WINS event log messages for event ID 4210 to 5300, click the following article number to view the article in the Microsoft Knowledge Base:
316836 Windows Server WINS Event Log Messages, Part 2: Event ID 4210 to Event ID 5300

More Information


  • 4096 - WINS_EVT_LOG_INITED
    WINS has initialized its log for this invocation.
  • 4097 - WINS_EVT_WINS_OPERATIONAL
    WINS initialized properly and is now fully operational.
  • 4098 - WINS_EVT_ORDERLY_SHUTDOWN
    WINS was terminated by the service controller. WINS will gracefully terminate.
  • 4099 - WINS_EVT_ADMIN_ORDERLY_SHUTDOWN
    WINS is being gracefully terminated by the administrator. The address of the administrator is %1.
  • 4100 - WINS_EVT_ADMIN_ABRUPT_SHUTDOWN
    WINS is being abruptly terminated by the administrator. The address of the administrator is %1.
  • 4101 - WINS_EVT_INVALID_OPCODE
    WINS received a Name Request with an invalid operation code. The request is being thrown away.
  • 4102 - WINS_EVT_CONN_ABORTED
    The connection was aborted by the remote WINS. Remote WINS may not be configured to replicate with the server.
  • 4103 - WINS_EVT_NO_RECS
    There are no records in the registry for the key.
  • 4104 - WINS_EVT_NO_PULL_RECS
    There are no pull records.
  • 4105 - WINS_EVT_NO_PUSH_RECS
    There are no push records.
  • 4106 - WINS_EVT_NO_RECS_IN_NAM_ADD_TBL
    The WINS database of name-to-address mappings is empty. It could mean that a previous invocation of WINS created the database and then went down before any registration could be done.
  • 4107 - WINS_EVT_NO_RECS_IN_OWN_ADD_TBL
    The WINS database of owner-to-address mappings is empty. It could mean that a previous invocation of WINS created the table and then went down before its own entry could be added. The WINS server went down very fast (even before all its threads could become fully operational).
  • 4108 - WINS_EVT_CANT_GET_INITRPL_VAL
    WINS could not read the InitTimeReplication field of the pull/push key.
  • 4109 - WINS_EVT_CANT_GET_REFRESH_INTERVAL_VAL
    WINS could not read the Refresh interval from the registry
  • 4110 - WINS_EVT_CANT_GET_TOMBSTONE_INTERVAL_VAL
    WINS could not read the Tombstone interval from the registry
  • 4111 - WINS_EVT_CANT_GET_VERIFY_INTERVAL_VAL
    WINS could not read the Verify interval from the registry
  • 4112 - WINS_EVT_CANT_GET_RETRY_COUNT
    WINS could not read the retry count for retrying communication with a remote WINS.
  • 4113 - WINS_EVT_CANT_GET_TOMBSTONE_TIMEOUT_VAL
    WINS could not read the Tombstone Timeout from the registry.
  • 4114 - WINS_EVT_CANT_GET_CC_INTERVAL_VAL
    WINS could not read the ConsistencyCheck value (type DWORD) from the Parameters\ConsistencyCheck subkey in the registry. The first consistency check is done at the time specified in the SpTime entry under the ConsistencyCheck subkey and is limited by the MaxRecsAtATime value. If the time is not specified, the check is done at 2 am.

    To correct the problem, open the registry and verify that the ConsistencyCheck subkey has been correctly sent up and all required values have been set. Correct the values, as needed.
  • 4115 - WINS_EVT_CANT_GET_CC_MAX_RECS_AAT_VAL
    WINS could not read the MaxRecsAtATime value (type DWORD) in the Wins\Parameters\ConsistencyCheck subkey of the registry. Set this value if you do not want WINS to replicate more than a set number of records in one cycle while doing periodic consistency checks of the WINS database. When doing a consistency check, WINS replicates all records of an owner WINS by either going to that WINS or to a replication partner. At the end of doing a consistency check for an owner's records, it checks to see if it has replicated more than the specified value in the current consistency check cycle. If the value has been exceeded, the consistency check stops, otherwise it continues. In the next cycle, it starts from where it left off and wraps around to the first owner if required.
  • 4116 - WINS_EVT_CANT_GET_CC_USE_RPL_PNRS_VAL
    WINS could not read the UseRplPnrs value of the Wins\Parameters\ConsistencyCheck key. If this value is set to a non-zero (DWORD) value, WINS will do a consistency check of the owners in its database by going to one or more of its replication partners. If the owner of the records happens to be a replication partner, WINS will go to it, otherwise it will pick one at random. Set this value if you have a large number of WINSs in your configuration and/or if you do not want the local WINS to go to any WINS that is not a replication partner.
  • 4117 - WINS_EVT_CC_STATS
    WINS just did a consistency check on the records owned by the WINS with the address, %1. The number of records inserted, updated, and deleted are in the data section (second, third, fourth DWORDS).
  • 4118 - WINS_EVT_CC_FAILED
    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.
  • 4119 - WINS_EVT_PKT_FORMAT_ERR
    WINS received a packet that has the wrong format. For example, a label may be More than 63 octets.
  • 4120 - WINS_EVT_NO_RECS_RETRIEVED
    No records meeting the %1 criteria were found in the WINS database.
  • 4121 - WINS_EVT_NO_RPL_RECS_RETRIEVED
    WINS's Replicator could not find any records in the WINS database. This means there are no active or tombstone records in the database. It could be that the records being requested by a remote WINS server have either been released or do not exist.
  • 4122 - WINS_EVT_GRP_LIMIT_REACHED
    The special group has reached its limit. WINS cannot add any more members.
  • 4123 - WINS_EVT_OWNER_LIMIT_REACHED
    The address database already has reached the limit of owners. This is 100. This error was noticed while attempting to add the address given in the data section.
  • 4124 - WINS_EVT_UPD_NTF_NOT_ACCEPTED
    The WINS server received an update notification from the non-configured WINS server at the address, %1. The WINS server rejected it. This means the remote WINS server is not in the list of Push partners (WINS servers under the Pull key) and the administrator has prohibited (using the registry) replication with non-configured WINS servers. If you want this WINS server to accept update notifications from non-configured WINS servers then set the Wins\Paramaters\RplOnlyWCnfPnrs value in the registry to 0.
  • 4125 - WINS_EVT_UPD_NTF_ACCEPTED
    WINS received an update notification from the WINS with the address, %1. WINS accepted it.
  • 4126 - WINS_EVT_ADD_VERS_MAP_REQ_NOT_ACCEPTED
    The WINS server received a pull request from the non-configured WINS server with the address, %1. The WINS server rejected it since the remote WINS server is not in the list of Pull partners (WINS servers under the Pull key) and the administrator has prohibited (using the registry) replication with non-configured partners. If you want this WINS server to accept update notifications from WINS servers not in the "pull partner" list, then set the "replication only with configured partners" value in the registry to 0.
  • 4127 - WINS_EVT_CANT_OPEN_DATAFILES_KEY
    The datafiles key could not be opened.
  • 4128 - WINS_EVT_OPEN_NETBT_KEY_ERR
    The NetBios over TCP/IP (NetBT) key could not be opened.
  • 4129 - WINS_EVT_QUERY_NETBT_KEY_ERR
    The NetBios over TCP/IP (NetBT) key could not be queried.
  • 4130 - WINS_EVT_WRK_THD_CREATED
    A worker thread was created by the administrator.
  • 4131 - WINS_EVT_WRK_THD_TERMINATED
    A worker thread was terminated by the administrator.
  • 4132 - WINS_EVT_WINS_ENTRY_DELETED
    The owner-address mapping table had an entry with a non-zero owner ID and an address the same as the local WINS address. The entry has been marked as deleted in the in-memory table.
  • 4133 - WINS_EVT_INF_REM_WINS_EXC
    An error occurred while trying to inform a remote WINS to update the version number.
  • 4134 - WINS_EVT_INF_REM_WINS
    The local WINS is going to inform a remote WINS to update the version number of a record. This is because the local WINS encountered a conflict between an active owned name and an active replica that it pulled from a replication partner.
  • 4135 - WINS_EVT_REM_WINS_INF
    The local WINS has been informed by a remote WINS with address, %1, to update the version number of a record. This is because the remote WINS encountered a conflict between an active owned name and an active replica that it pulled from a replication partner.
  • 4136 - WINS_EVT_CANT_FIND_REC
    A remote WINS requested the update of the version stamp of a record, but the record could not be found. Check to see if the record was deleted or updated.
  • 4137 - WINS_EVT_NAME_MISMATCH
    A name mismatch was noticed while verifying the validity of old replicas. The local record has the name %1 while the replica pulled in from the WINS that owns this record has the name %2. This could mean that the remote WINS was brought down and then up again but its version counter value was not set to its previous value before termination.
  • 4138 - WINS_EVT_VERS_COUNTER_CHANGED
    The value of the version ID counter was changed. The new value (Low 32 bits) is given in the data section.
  • 4139 - WINS_EVT_CNF_CHANGE
    The WINS replication request is being ignored since WINS suspects that the Wins\Partners key information has changed (because it received a notification From the registry) which makes the current request pertaining to the partner out of date.
  • 4140 - WINS_EVT_DUP_ENTRY_DEL
    WINS is deleting all records of the WINS with owner ID, %d. This owner ID corresponds to the address, %s.
  • 4141 - WINS_EVT_REC_PULLED
    WINS pulled records from a WINS while doing %1. The partner's address and the owner's address whose records were pulled are given in the data section (second and third DWORD respectively). The number of records pulled is the fourth DWORD.
  • 4142 - WINS_EVT_CC_NO_RECS
    WINS performed a consistency check on the records. The number of records pulled, The address of the WINS whose records were pulled, and the address of the WINS from which these records were pulled are given in the second, third, and fourth DWORDs in the data section.
  • 4143 - WINS_EVT_SCV_RECS
    WINS scavenged its records in the WINS database. The number of records scavenged is given in the data section.
  • 4144 - WINS_EVT_SCV_RPLTOMB
    WINS scavenged replica tombstones in the WINS database. The number of records Scavenged is given in the data section.
  • 4145 - WINS_EVT_SCV_CLUTTER
    WINS revalidated old active replicas in the WINS database.
  • 4146 - WINS_EVT_LOG_CLOSE
    WINS Performance Monitor Counters is closing the event log.
  • 4147 - WINS_EVT_DEL_RECS
    WINS has deleted records of a partner. The internal ID of the partner whose records were deleted, the minimum version number (low word, high word), and the maximum version number (low word, high word) of the records deleted are given in the data section.

Warning Event Values

NOTE: The error codes 8000 to 4020 are reserved for Warning events
  • 4148 - WINS_EVT_VERS_MISMATCH
    The local WINS server received a request from a remote WINS server that is not the same version. Because the WINS servers are not compatible, the connection was terminated. The version number of the remote WINS server is given in the data section.
  • 4149 - WINS_EVT_WINSOCK_SEND_MSG_ERR
    Winsock Send could not send all the bytes. The connection could have been aborted by the remote client.
  • 4150 - WINS_EVT_ADJ_TIME_INTVL_R
    WINS adjusted the scavenging related time interval, %1, so that it is compatible with the replication time intervals. The adjusted value for this scavenging parameter is given in the data section (second DWORD). This value was computed by WINS using an algorithm that may use the maximum replication time interval specified. The current value achieves a good balance between consistency of databases across the network of WINS servers and the performance of the WINS servers.
  • 4151 - WINS_EVT_ADJ_TIME_INTVL
    WINS adjusted the scavenging related time interval, %1. The adjusted value for this scavenging parameter is given in the data section (second DWORD). This value was computed by WINS using an algorithm that tries to achieve a good balance between consistency of databases across the network of WINS servers and the performance of the WINS servers.
  • 4152 - WINS_EVT_WINSOCK_SELECT_TIMED_OUT
    The timeout period has expired on a call to another WINS server. Assuming that the network and routers are working properly, either the remote WINS server is overloaded, or its TCP listener thread has terminated.
  • 4153 - WINS_EVT_UNABLE_TO_VERIFY
    The Scavenger thread found active replicas that needed to be verified with the owner WINS server since they were older than the verify time interval. The table of owner-to-address mappings indicated the WINS was not active.
  • 4154 - WINS_EVT_LIMIT_MULTIH_ADD_REACHED
    The name registration packet that was just received has too many addresses. The maximum number of addresses for a multi-homed client is 25. The number of addresses found in the packet is given in the data section.
  • 4155 - WINS_EVT_REPLICA_CLASH_W_STATIC
    A replica clashed with the static record, %1, in the WINS database. The replica was rejected.
  • 4156 - WINS_EVT_RPC_NOT_INIT
    WINS could not initialize the administrator interface because of a problem with the Remote Procedure Call (RPC) service. You may not be able to administer WINS. Make sure that the RPC service is running.
  • 4157 - WINS_EVT_NO_NTF_PERS_COMM_FAIL
    WINS did not send a notification message to the WINS server whose address is given in the data section. There were a number of communications failures with that server in the past few minutes.
  • 4158 - WINS_EVT_REL_DIFF_OWN
    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. Run winscl.exe to get the owner ID to address mapping.
  • 4159 - WINS_EVT_REC_DELETED
    The administrator deleted a record with the name, %1.
  • 4160 - WINS_EVT_DB_RESTORED
    WINS could not start because of a database error. WINS restored the old database from the backup directory and will come up using this database.
  • 4161 - WINS_EVT_PARTIAL_RPL_TYPE
    A non-zero replication type applies for this partner. This means only a subset of records will be replicated between the local WINS and this partner. If later you want to get records that did not replicate, you can either pull them using winscl.exe in the Windows 2000 Resource Kit, or delete all owners acquired only through this partner and initiate replication after that to reacquire all their records. The partner's address is given in the second DWORD of the data section.
  • 4162 - WINS_EVT_PNR_PARTIAL_RPL_TYPE
    A partner has requested only a subset of records. This means we won't replicate all the records in the range requested. Check the partner's registry to see what replication type applies to it. The partner's address is given in the second DWORD of the data section.
    4163 - WINS_EVT_ADJ_MAX_RECS_AAT
  • WINS adjusted the Maximum Records at a time parameter of the ConsistencyCheck key. The value specified, %2, was changed to the minimum value, %1. These are the maximum number of records that will be replicated at any one time for a consistency check.
  • 4164 - WINS_EVT_FORCE_SCV_R_T
    WINS was forced to scavenge replica tombstones of a WINS. The person with administrative rights on the computer forced the scavenging using winscl.exe.
    WINS does not scavenge replica tombstones unless they have timed out and the WINS has been running for at least 3 days (This is to ensure that the tombstones have replicated to other WINSs). In this case, the tombstones were timed out but the WINS had not been up for 3 days. The replica tombstones were deleted.
    This deletion does not constitute a problem unless you have WINS servers that are primary and backup to clients but not both Push and Pull partners of each other. If you do have such WINSs, there is a low probability that this action will result in database inconsistency but if it does (as you will discover eventually), you can get back to a consistent state by initiating consistency checks using winscl.exe.
    NOTE: The consistency check is a network and resource intensive operation, you should initiate it only with a full understanding of what it does. You are better off creating the ConsistencyCheck subkey under Wins\Parameters.

Error Event Values

  • 4165 - WINS_EVT_ABNORMAL_SHUTDOWN
    WINS has encountered an error that caused it to shut down.The exception code is the second DWORD of the data section. Check previous event log entries to determine a more specific cause for the error.
  • 4166 - WINS_EVT_RPLPULL_ABNORMAL_SHUTDOWN
    The replication Pull thread is shutting down due to an error. Restart WINS.
  • 4167 - WINS_EVT_RPLPUSH_ABNORMAL_SHUTDOWN
    The replication Push thread is shutting down due to an error. Restart WINS.
  • 4168 - WINS_EVT_CHL_ABNORMAL_SHUTDOWN
    The Name Challenge thread is shutting down due to an error. Restart WINS.
  • 4169 - WINS_EVT_WRK_ABNORMAL_SHUTDOWN
    A Worker thread is shutting down due to an error. Restart WINS.
  • 4170 - WINS_EVT_CANT_INIT
    An abnormal error occurred during the WINS initialization. Check the application and system logs for information on the cause. WINS may need to be restarted.
  • 4171 - WINS_EVT_CANT_INIT_W_DB
    WINS could not properly set up the WINS database. Look at the application log for errors from the Exchange component, ESENT.
  • 4172 - WINS_EVT_CANT_CREATE_WRK_THD
    A worker thread could not be created. The computer may be low on resources.
  • 4173 - WINS_EVT_CANT_CREATE_THD
    A thread could not be created. The computer may be low on resources.
  • 4174 - WINS_EVT_CANT_CREATE_EVT
    An event could not be created.
  • 4175 - WINS_EVT_CANT_CREATE_CHL_THD
    The Name Challenge Request thread could not be created.
  • 4176 - WINS_EVT_CANT_OPEN_KEY
    A registry key could not be created or opened.
  • 4177 - WINS_EVT_CANT_OPEN_WINS_KEY
    The WINS configuration key could not be created or opened. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.
  • 4178 - WINS_EVT_CANT_OPEN_PULL_KEY
    The WINS Pull configuration key could not be created or opened. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.
  • 4179 - WINS_EVT_CANT_OPEN_PUSH_KEY
    The WINS Push configuration key could not be created or opened. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.
  • 4180 - WINS_EVT_CANT_OPEN_PARAMETERS_KEY
    The WINS\Parameters key could not be created or opened. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.
  • 4181 - WINS_EVT_CANT_OPEN_CC_KEY
    The WINS\Parameters\ConsistencyCheck subkey could not be created or opened. This key should be there if you want WINS to do consistency checks on its database periodically.
    NOTE: Consistency checks have the potential of consuming large amounts of network bandwidth.
    Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.
  • 4182 - WINS_EVT_CANT_CREATE_REG_EVT
    The registry change notification event could not be created. Check to see if system resources are low.
  • 4183 - WINS_EVT_WRONG_TIME_FORMAT
    The correct time format is hh:mm:ss. Check the value of SpTime in the registry.
  • 4184 - WINS_EVT_REG_NTFY_FN_ERR
    The registry notification function returned an error.
  • 4185 - WINS_EVT_NBTSND_REG_RSP_ERR
    The Name Registration Response could not be sent due to an error. This error was encountered by a NetBT request thread
  • 4186 - WINS_EVT_RPLSND_REG_RSP_ERR
    The Name Registration Response could not be sent due to an error. This error was encountered by a RPL thread.
  • 4187 - WINS_EVT_CHLSND_REG_RSP_ERR
    The Name Registration Response could not be sent due to an error. This error was encountered by the Name Challenge Thread.
  • 4188 - WINS_EVT_SND_REL_RSP_ERR
    The Name Release Response could not be sent due to an error. This error is often caused by a problem with the NetBIOS over TCP/IP (NetBT) interface.
  • 4189 - WINS_EVT_SND_QUERY_RSP_ERR
    The Name Query Response could not be sent due to an error. This error is often caused by a problem with the NetBIOS over TCP/IP (NetBT) interface.
  • 4190 - WINS_EVT_F_CANT_FIND_REC
    A record could not be registered because it already existed. However, the same record then could not be found. The WINS database might be corrupt. Check the application log for the Exchange component, ESENT.
  • 4191 - WINS_EVT_CANT_CREATE_HEAP
    WINS could not create a heap because of a resource shortage. Check to see if the computer is running short of virtual memory.
  • 4192 - WINS_EVT_SFT_ERR
    An error occurred from which WINS will try to recover. If the recovery fails, check previous event log entries to determine what prevented a successful recovery. Take the appropriate action to solve the error that prevented recovery.
  • 4193 - WINS_EVT_CANT_CREATE_UDP_SOCK
    WINS could not create the notification socket. Make sure the TCP/IP driver is installed and running properly.
  • 4194 - WINS_EVT_CANT_CREATE_NTF_SOCK
    WINS could not create the User Datagram Protocol (UDP) socket to listen for Connection notification messages sent by another Pull thread in the local WINS.
  • 4195 - WINS_EVT_CANT_CREATE_TCP_SOCK_FOR_LISTENING
    WINS could not create the TCP socket for listening to TCP connections. Make sure the TCP/IP driver is installed and running properly.
  • 4196 - WINS_EVT_CANT_CREATE_TCP_SOCK_FOR_CONN
    WINS could not create the TCP socket for making a TCP connection. Make sure the TCP/IP stack is installed and running properly.
  • 4197 - WINS_EVT_WINSOCK_BIND_ERR
    An address could not bind to a socket. Make sure the TCP/IP stack is installed And running properly.
    This event might mean that the 'nameserver' port (specified in the services file) which is used as the default by WINS for replication and discovering other WINSs has been taken by another process or service running on this computer. You have two options - either bring down that other process or service or direct WINS to use another port. If you choose the second option, set the value 'PortNo' (REG_DWORD) under the Wins\Parameters subkey in the registry to 1512.
    NOTE: Changing the port number this way will prevent this WINS from replicating or discovering other WINSs unless they too are directed to use the same port number as this WINS.
  • 4198 - WINS_EVT_WINSOCK_LISTEN_ERR
    WINS could not listen on the Winsock socket.
  • 4199 - WINS_EVT_WINSOCK_SELECT_ERR
    Winsock Select returned with an error.
  • 4200 - WINS_EVT_WINSOCK_ERR
    %1 returned with an error code of %2.
  • 4201 - WINS_EVT_WINSOCK_GETSOCKNAME_ERR
    WINS created a socket and called the 'bind' WinSock API to bind a handle to it. On calling 'getsockname' to determine the address bound, WINS received an error.
  • 4202 - WINS_EVT_WINSOCK_CONNECT_ERR
    An attempt to connect to the remote WINS server with address %1 returned with an error. Check to see that the remote WINS server is running and available, and that WINS is running on that server.
  • 4203 - WINS_EVT_WINSOCK_ACCEPT_ERR
    WINS could not accept on a socket.
  • 4204 - WINS_EVT_WINSOCK_RECVFROM_ERR
    WINS could not read from the User Datagram Protocol (UDP) socket.
  • 4205 - WINS_EVT_NETBT_RECV_ERR
    WINS could not read from NetBIOS over TCP/IP (NetBT).
  • 4206 - WINS_EVT_WINSOCK_CLOSESOCKET_ERR
    WINS could not close a socket.
  • 4207 - WINS_EVT_WINSOCK_SENDTO_MSG_ERR
    A Winsock Sendto message could not send all the bytes.
  • 4208 - WINS_EVT_NETBT_SEND_ERR
    WINS could not send a User Datagram Protocol (UDP) message to a WINS client.
  • 4209 - WINS_EVT_WINSOCK_SENDTO_ERR
    A Winsock Sendto message returned with an error.