Windows Server WINS Event Log Messages, Part 2: Event ID 4210 to 5300 (316836)


The information in this article applies to:

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Standard Edition
  • Microsoft Windows Small Business Server 2003, Premium Edition
  • Microsoft Windows Small Business Server 2003, Standard Edition
This article was previously published under Q316836

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 4210 to event ID 5300.

For additional information about WINS event log messages for event ID 4096 to event ID 4209, click the following article number to view the article in the Microsoft Knowledge Base:

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

MORE INFORMATION

  • 4210 - WINS_EVT_WINSOCK_RECV_ERR
    The Winsock receive function returned with an unexpected error.
  • 4211 - WINS_EVT_WINSOCK_SEND_ERR
    The WinSock send function returned with an unexpected error.
  • 4212 - WINS_EVT_BAD_STATE_ASSOC
    A message was received on an association. The association is in a bad state. This indicates a bug in the WINS code. Restart WINS.
  • 4213 - WINS_EVT_CANT_ALLOC_RSP_ASSOC
    WINS could not allocate a responder association. Check to see if the system is low on resources.
  • 4214 - WINS_EVT_CANT_ALLOC_INI_ASSOC
    WINS could not allocate an initiator association. Check to see if the system is low on resources.
  • 4215 - WINS_EVT_CANT_ALLOC_IMP_DLG
    WINS could not allocate an implicit dialogue. Check to see if the system is low on resources.
  • 4216 - WINS_EVT_CANT_ALLOC_EXP_ASSOC
    WINS could not allocate an explicit dialogue. Check to see if the system is low on resources.
  • 4217 - WINS_EVT_CANT_LOOKUP_ASSOC
    WINS could not look up the association block for a NetBIOS over TCP/IP (NetBT) association. Check to see if the message read is corrupted. WINS looks at bit 11-14 of the message to determine if the association is from another WINS or from an NetBT node. It is possible that the bits are corrupted or that there is a mismatch between what the two WINS servers expect to see in those bits.
  • 4218 - WINS_EVT_CANT_ALLOC_UDP_BUFF
    WINS could not allocate a User Datagram Protocol (UDP) Buffer. Check to see if the system is low on resources.
  • 4219 - WINS_EVT_CANT_FREE_UDP_BUFF
    WINS could not free a User Datagram Protocol (UDP) Buffer. Restart WINS.
  • 4220 - WINS_EVT_CANT_CREATE_COMM_THD
    WINS could not create a communication subsystem thread. Check to see if the system is low on resources.
  • 4221 - WINS_EVT_CANT_SIGNAL_MAIN_THD
    A WINS thread could not signal the main thread after closing its session. This would be caused by the last thread in WINS closing the database.
  • 4222 - WINS_EVT_CANT_SIGNAL_HDL
    A WINS thread could not signal a handle.
  • 4223 - WINS_EVT_CANT_RESET_HDL
    A WINS thread could not reset a handle.
  • 4224 - WINS_EVT_DATABASE_ERR
    WINS encountered a database error. This may or may not be a serious error. WINS will try to recover from it. You can check the database error events under 'Application Log' category of the Event Viewer for the Exchange Component, ESENT, source to find out more details about database errors.

    If you continue to see a large number of these errors consistently over time (a span of few hours), you may want to restore the WINS database from a backup.

    The error number is in the second DWORD of the data section.
  • 4225 - WINS_EVT_DATABASE_UPD_ERR
    WINS could not update the record with the name, %1. Check the application log for the Exchange component, ESENT.
  • 4226 - WINS_EVT_CONFLICT_OWN_ADD_TBL
    WINS could not update the Owner ID-to-Address mapping table in the database. This means the in-memory table that maps to the database table has gotten out of sync with the database table.
  • Check the application log for the Exchange component, ESENT. The WINS database may have to be restored.
  • 4227 - WINS_EVT_CANT_FIND_ANY_REC_IN_RANGE
    The Push Thread was requested for a range of records but could not find any records in the range. Make sure that the replication time intervals are set properly. If the tombstone interval and timeout intervals are not correct (that is, much less than the replication interval), the above condition is possible. This is because the records might get changed into tombstones and then deleted before the remote WINS can pull them. Similarly, if the refresh interval is set to be much less than the replication interval then the records could get released before a WINS can pull them (a released record is not sent).

    Make sure that the replication time intervals are set properly.
  • 4228 - WINS_EVT_SIGNAL_TMM_ERR
    The Timer thread could not be signaled. This indicates this computer is extremely overloaded or that the WINS application has failed. Check for low system resources. It may be necessary to restart WINS.
  • 4229 - WINS_EVT_SIGNAL_CLIENT_ERR
    The Timer could not signal the client thread.
  • 4230 - WINS_EVT_CANT_QUERY_KEY
    WINS could not get information about a key. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.
  • 4231 - WINS_EVT_CANT_QUERY_PULL_KEY
    WINS could not get information about the Pull key. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.
  • 4232 - WINS_EVT_CANT_QUERY_PUSH_KEY
    WINS could not get information about the Push key. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.
  • 4233 - WINS_EVT_CANT_QUERY_DATAFILES_KEY
    WINS could not get information about the DATAFILES key. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.
  • 4234 - WINS_EVT_CANT_QUERY_SPEC_GRP_MASKS_KEY
    WINS could not get information about the SPEC_GRP_MASKS key. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.
  • 4235 - WINS_EVT_CANT_OPEN_PULL_SUBKEY
    WINS could not open a Pull subkey. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.
  • 4236 - WINS_EVT_CANT_OPEN_PUSH_SUBKEY
    WINS could not open a Push subkey. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.
  • 4237 - WINS_EVT_CANT_GET_PULL_TIMEINT
    WINS could not get the time interval from a Pull record.
  • 4238 - WINS_EVT_CANT_GET_PUSH_TIMEINT
    WINS could not get the time interval from a Push record.
  • 4239 - WINS_EVT_CANT_GET_PUSH_UPDATE_COUNT
    WINS could not get the update count from a Push record. No default will be used.
  • 4240 - WINS_EVT_CANT_CLOSE_KEY
    WINS could not close an open key. Check to see if the permissions on the key are set properly, system resources are low, or the registry is having a problem.
  • 4241 - WINS_EVT_TMM_EXC
    WINS Timer thread encountered an exception.
  • 4242 - WINS_EVT_RPLPUSH_EXC
    WINS Push thread encountered an exception. A recovery will be attempted.
  • 4243 - WINS_EVT_RPLPULL_PUSH_NTF_EXC
    WINS Pull thread encountered an error during the process of sending a push notification to another WINS. The error code is given in the data section.
  • 4244 - WINS_EVT_RPC_EXC
    A WINS Remote Procedure Call (RPC) thread encountered an error.
  • 4245 - WINS_EVT_TCP_LISTENER_EXC
    The WINS TCP Listener thread encountered an error.
  • 4246 - WINS_EVT_UDP_LISTENER_EXC
    The WINS User Datagram Protocol (UDP) Listener thread encountered an error.
  • 4247 - WINS_EVT_SCV_EXC
    The WINS Scavenger thread encountered an error.
  • 4248 - WINS_EVT_CHL_EXC
    The WINS Challenger thread encountered an error.
  • 4249 - WINS_EVT_WRK_EXC
    A WINS worker thread encountered an error.
  • 4250 - WINS_EVT_SCV_ERR
    The WINS Scavenger thread could not scavenge a record. This record will be ignored. The Scavenger will continue on to the next available record. Check the application log for the Exchange component, ESENT.
  • 4251 - WINS_EVT_CONN_RETRIES_FAILED
    The WINS Replication Pull Handler could not connect to a WINS server. All retries failed. WINS will try again after a set number of replication time intervals have elapsed.
  • 4252 - WINS_EVT_NO_SUBKEYS_UNDER_PULL
    WINS did not find any subkeys under the Pull key.
  • 4253 - WINS_EVT_NO_SUBKEYS_UNDER_PUSH
    WINS did not find any subkeys under the Push key.
  • 4254 - WINS_EVT_CANT_UPDATE_DB
    An error has prevented WINS from updating the WINS database. The database may be corrupt.
  • 4255 - WINS_EVT_PUSH_PNR_INVALID_ADD
    WINS has been asked to pull entries from itself. Check all the Pull subkeys of this WINS.
  • 4256 - WINS_EVT_PUSH_PROP_FAILED
    WINS was unable to propagate the push trigger.
  • 4257 - WINS_EVT_REQ_RSP_MISMATCH
    WINS sent a name query or a name release with a certain transaction ID. It received a response to the request that differed either in the name that it contained or in the operation code. WINS has thrown the response away.
  • 4258 - WINS_EVT_DB_INCONSISTENT
    The WINS database is inconsistent. The number of owners found in the name-address mapping table are different from the number found in the owner-address mapping table.
  • 4259 - WINS_EVT_REM_WINS_CANT_UPD_VERS_NO
    The local WINS requested a remote WINS to update the version number of a database record owned by the remote WINS. The remote WINS could not do the update and reported an error.
  • 4260 - WINS_EVT_RPL_REG_ERR
    WINS received an error while registering replicas. It will not register any additional replicas of this WINS at this time (the address is in the data section 4th-8th byte). Check a previous log entry to determine the reason for this. If you get the same error during subsequent replication with the above partner WINS, you may want to restore the WINS database from the backup.
  • 4261 - WINS_EVT_RPL_REG_GRP_MEM_ERR
    WINS received an error while trying to register a group's replica with name, %1. The replica is owned by the WINS with the address given in the data section.
  • 4262 - WINS_EVT_RPL_REG_UNIQUE_ERR
    WINS received an error while trying to register a unique replica with name %1. The replica is owned by WINS with address given in the data section.
  • 4263 - WINS_EVT_REG_UNIQUE_ERR
    WINS received an error while trying to register the unique entry with the name, %1.
  • 4264 - WINS_EVT_REG_GRP_ERR
    WINS received an error while trying to register the group entry with the name, %1.
  • 4265 - WINS_EVT_UPD_VERS_NO_ERR
    WINS received an error while trying to update the version number of a record in the WINS database.
  • 4266 - WINS_EVT_NAM_REL_ERR
    WINS received an error while trying to release a record in the WINS database.
  • 4267 - WINS_EVT_NAM_QUERY_ERR
    WINS received an error while trying to query a record in the WINS database.
  • 4268 - WINS_EVT_RPL_STATE_ERR
    WINS received a replica whose state is incorrect. For example, the state may be RELEASED or the replica might be an Internet group that does not have any members but the state is not TOMBSTONE.
  • 4269 - WINS_EVT_UNABLE_TO_CHG_PRIORITY
    The Scavenger thread was unable to change its priority level.
  • 4270 - WINS_EVT_REL_TYP_MISMATCH
    A name release request was received for a record that didn't match the unique or group type indicated in the request. The request has been ignored.
  • 4271 - WINS_EVT_REL_ADD_MISMATCH
    A name release request was received for the record name, %2, that did not have the same address as the requestor. The request has been ignored.
  • 4272 - WINS_EVT_PUSH_TRIGGER_EXC
    An error was encountered while trying send a push trigger notification to a remote WINS. The exception code is the second DWORD of the data section.
  • 4273 - WINS_EVT_PULL_RANGE_EXC
    An error was encountered while trying to service a pull range request from a remote WINS. The exception code is the second DWORD of the data section.
  • 4274 - WINS_EVT_BAD_RPC_STATUS_CMD
    WINS was either provided a bad command code or it became corrupt.
  • 4275 - WINS_EVT_FILE_TOO_BIG
    The static data file that is used to initialize the WINS database is too big.
  • 4276 - WINS_EVT_FILE_ERR
    An error was encountered during an operation on the static data file, %1.
  • 4277 - WINS_EVT_FILE_NAME_TOO_BIG
    The name of the file, after expansion, is bigger than WINS can handle. The condensed string is, %1.
  • 4278 - WINS_EVT_STATIC_INIT_ERR
    WINS could not do a static initialization.
  • 4279 - WINS_EVT_RECONFIG_ERR
    An error occurred during the configuration or reconfiguration of WINS. If this was encountered during boot time, WINS will come up with default parameters. You may want to research the cause of this initialization failure and then reboot WINS.
  • 4280 - WINS_EVT_CONFIG_ERR
    An error occurred during the configuration or reconfiguration of WINS.
  • 4281 - WINS_EVT_LOCK_ERR
    A lock error has occurred. This could happen if the WINS is trying to send a response on a dialogue that is no longer ACTIVE. An implicit dialogue can cease to exist if the association it is mapped to terminates. In this case, getting a lock error is normal.
  • 4282 - WINS_EVT_CANT_OPEN_DATAFILE
    WINS could not import static mappings from the file, %1. Verify that the file exists and is readable.
  • 4283 - WINS_EVT_EXC_PUSH_TRIG_PROC
    WINS encountered an error while processing a push trigger or update notification. The error code is given in the data section. If it indicates a communication failure, check to see if the remote WINS that sent the trigger went down. If the remote WINS is on a different subnet, then maybe the router is down.
  • 4284 - WINS_EVT_EXC_PULL_TRIG_PROC
    WINS encountered an exception while processing a pull trigger.
  • 4285 - WINS_EVT_EXC_RETRIEVE_DATA_RECS
    WINS encountered an exception while retrieving data records.
  • 4286 - WINS_EVT_CONN_LIMIT_REACHED
    The WINS server cannot make or accept this connection since the connections limit has been reached. This situation is temporary and should resolve by itself shortly.
  • 4287 - WINS_EVT_GRP_MEM_PROC_EXC
    The exception was encountered during the processing of a group member.
  • 4288 - WINS_EVT_CLEANUP_OWNADDTBL_EXC
    The Scavenger thread encountered an error while cleaning up the owner-address table. It will try again after the Verify interval has elapsed.
  • 4289 - WINS_EVT_RECORD_NOT_OWNED
    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 server is updating the record after a conflict. It is not a serious error if the WINS server is updating the record as a result of a request to do so from a remote WINS server (When a remote WINS server notices a conflict between an active owned entry and a replica it informs the owner of the replica to update the version number of the record. It is possible that the replica is no longer owned by the remote WINS).

    Check a previous log entry to determine which situation applies here.
  • 4290 - WINS_EVT_WRONG_SPEC_GRP_MASK_M
    The special group mask specified is not valid. It has either a non-hexadecimal character or is less than 32 characters in length. A hexadecimal character is in the range 0-F (or 0-f).
  • 4291 - WINS_EVT_UNABLE_TO_GET_ADDRESSES
    WINS tried to get its addresses but failed. WINS will recover when the IP address comes back.
  • 4292 - WINS_EVT_ADAPTER_STATUS_ERR
    WINS did not get back any names from NetBIOS over TCP/IP (NetBT) when it did an adapter status.
  • 4293 - WINS_EVT_SEC_OBJ_ERR
    WINS could not initialize properly with the security subsystem. At initialization, WINS creates a security object and attaches an Access Control List (ACL) to it. This security object is then used to authenticate Remote Procedure Call (RPC) calls made to WINS. WINS could not create the above security object.
  • 4294 - WINS_EVT_NO_PERM
    The client application does not have the permissions required to execute the function.
  • 4295 - WINS_EVT_ADJ_VERS_NO
    When WINS replicated with its partners, one of the partners showed there was more data that actually existed. WINS adjusted its counter so that new registrations and updates are seen by its partners. This means that recovery did not work properly. You may want to check which of the partners has the highest version number corresponding to the local WINS. Shut down WINS and restart after specifying this number in the registry.
  • 4296 - WINS_EVT_TOO_MANY_STATIC_INITS
    Too many concurrent static initializations are occurring. The number of such initializations currently active is given in the data section. This could be caused by reinitialization or imports from the WINS Manager tool. Try to initialize again.
    The number of currently active initializations is given in the data section.
  • 4297 - WINS_EVT_HEAP_ERROR
    WINS encountered a low memory condition. Check to see if the system is running out of virtual memory.
  • 4298 - WINS_EVT_DATABASE_CORRUPTION
    WINS found some database corruption. The record named, %1, is corrupt. It could be that recovery from the last crash did not work properly. WINS will try to recover. You may decide, however, to restore the WINS database from the backup.
  • 4299 - WINS_EVT_BAD_NAME
    The following name, %1, is too long. Valid NetBios names must not exceed 15 characters. The name has not been entered in the WINS database.
  • 4300 - WINS_EVT_BAD_ADDRESS
    The record with the name, %1, has bad address. It has not been entered in the WINS database.
  • 4301 - WINS_EVT_BAD_WINS_ADDRESS
    The computer running the WINS server does not have a valid address. When WINS requested an address, it received 0.0.0.0 as the address.
  • NOTE: WINS binds to the first adapter in a machine with more than one adapter bound to TCP/IP. Check the binding order of adapters and make sure the first one has a valid IP address for the WINS server.
  • 4302 - WINS_EVT_BACKUP_ERR
    WINS encountered an error doing a database backup to directory %1.
  • 4303 - WINS_EVT_COULD_NOT_DELETE_FILE
    WINS encountered an error while deleting the file, %1.
  • 4304 - WINS_EVT_COULD_NOT_DELETE_WINS_RECS
    WINS encountered an error while deleting one or more records of a WINS. The WINS address is in the second DWORD in data section. Check a previous log entry to determine what went wrong.
  • 4305 - WINS_EVT_BROWSER_NAME_EXC
    WINS encountered an error while getting the browser names for a client.
  • 4306 - WINS_EVT_MSG_TOO_BIG
    The length of the message sent by another WINS indicates a very big message. There may have been corruption of the data. WINS will ignore this message, terminate the connection with the remote WINS, and continue.
  • 4307 - WINS_EVT_RPLPULL_EXC
    The WINS replicator Pull thread encountered an error while processing a request. Check other log entries to determine what went wrong.
  • 4308 - WINS_EVT_FUNC_NOT_SUPPORTED_YET
    WINS does not support this functionality.
  • 4309 - WINS_EVT_MACHINE_INFO
    This WINS computer has %1 processors. It has %2 bytes of physical memory and %3 bytes of memory available for allocation.

  • 4310 - WINS_EVT_DB_ERR
    The record named, %1, could not replace another record in the WINS database. The record's version number is %2. The version number of record in the database is %3.
  • 4311 - WINS_EVT_DUP_ENTRY_IN_DB
    WINS has found some database corruption. It will try to recover. This recovery process can take a long time. Do not kill WINS in the middle of the recovery. If you do, you will have to restart WINS with a clean database.
  • 4312 - WINS_EVT_TERM_DUE_TIME_LMT
    WINS has exceeded the wait time for all threads to terminate. The number of threads still active is given in the second DWORD of the data section. The thread that could be stuck is the replicator thread. It could be because of the other WINS being slow in sending data or reading data. The latter can contribute to back-pressure on the TCP connection on which it is trying to replicate.

    Check the partner WINSs to see if one or more is in a bad state. This WINS terminated itself abruptly.
  • 4313 - WINS_EVT_NAME_FMT_ERR
    The name, %1, is in the wrong format. It has not been put in the WINS database. Check to see if you have a space before the name. If you want this space in the name, enclose the name within quotes.
  • 4314 - WINS_EVT_WINS_STATUS_ERR
    WINS Performance Monitor Counters could not get the WINS statistics.
  • 4315 - WINS_EVT_LOG_OPEN_ERR
    WINS Performance Monitor Counters could not open the event log.
  • 4316 - WINS_EVT_USING_DEF_LOG_PATH
    WINS could not open the log file. Check the log path specified in the registry under WINS\Parameters\LogFilePath and restart WINS, if necessary. WINS is going to use the default log file path of %%SystemRoot%%\system32\WINS.
  • 4317 - WINS_EVT_NAME_TOO_LONG
    WINS found a name in the WINS database with a length of more than 255 characters. The name was truncated to 17 characters.
  • 4318 - WINS_EVT_DB_RESTORE_GUIDE
    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.
  • 4319 - WINS_EVT_DB_CONV_GUIDE
    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.
  • 4320 - WINS_EVT_TEMP_TERM_UNTIL_CONV
    WINS will not start because the existing WINS database needs to be converted to the Windows 2000 format. WINS has initiated this conversion using a process called JETCONV. Once the conversion is successfully completed, WINS will be restarted. The conversion will take anywhere from a few minutes to an hour depending on the size of the databases to be converted.

    NOTE: Rebooting or ending the JETCONV process before it is completed could corrupt your databases. Check the Application Log in the Event Viewer for the status of JETCONV.
  • 4321 - WINS_EVT_INTERNAL_FEATURE
    The NoOfWrkThds parameter's value is too large and cannot be supported.
  • 4322 - WINS_EVT_DB_CONV_351_TO_5_GUIDE
    WINS could not come up because the existing WINS database needs conversion to the Windows 2000 format.
    If this is the first invocation of WINS after an upgrade from NT3.51, first, you need to run the convert utility (upg351db.exe in the %%SystemRoot%%\system32 directory) on the WINS database to convert it to the NT 4.0 database format. Then, you need to run the convert utility (edbutil.exe in the %%SystemRoot%%\system32 directory) on the converted 4.0 WINS database to convert it to the Windows 2000 database format.

    Once you have done that, you should restart WINS.
  • 4323 - WINS_EVT_DB_CONV_4_TO_5_GUIDE
    WINS could not start because the existing database needs to be converted to the Windows 2000 format.

    If this is the first invocation of WINS after an upgrade from NT 4.0, you need To run the convert utility (edbutil.exe in the %%SystemRoot%%\system32 directory) on the WINS database to convert it to the Windows 2000 database format.

    Once you have done that, you should restart WINS.
  • 4324 - WINS_EVT_TEMP_TERM_UNTIL_CONV_TO_5
    WINS cannot start because the existing WINS database needs conversion to the Windows 2000 format. WINS has initiated the conversion using the JETCONV process. Once the conversion is complete, WINS will start automatically. Do not reboot or kill the JETCONV process. The conversion may take anywhere from a few minutes to approximately two hours depending on the size of the databases.

    NOTE: Check the application log to see the status of the WINS database conversion.
  • 4325 - WINS_EVT_CANT_GET_INIT_CHL_RETRY_INTVL_VAL
    WINS could not read the Initial Challenge Retry Interval from the registry.
  • 4326 - WINS_EVT_CANT_GET_CHL_MAX_RETRIES_VAL
    WINS could not read the Challenge Maximum Number of Retries from the registry.
  • 4327 - WINS_EVT_ADMIN_BACKUP_INITIATED
    Adminstrator '%1' initiated a backup of the WINS database.
  • 4328 - WINS_EVT_ADMIN_SCVENGING_INITIATED
    Adminstrator '%1' has initiated a scavenging operation.
  • 4329 - WINS_EVT_SCVENGING_STARTED
    The WINS server has started a scavenging operation.
  • 4330 - WINS_EVT_SCVENGING_COMPLETED
    The WINS server has completed the scavenging operation.
  • 4331 - WINS_EVT_ADMIN_CCCHECK_INITIATED
    Adminstrator '%1' has initiated a consistency check operation.
  • 4332 - WINS_EVT_CCCHECK_STARTED
    The WINS server has started a consistency check operation.
  • 4333 - WINS_EVT_CCCHECK_COMPLETED
    The WINS server has completed the consistency check operation.
  • 4334 - WINS_EVT_ADMIN_DEL_OWNER_INITIATED
    Adminstrator '%1' has initiated the delete owner function of the WINS partner, %2.
  • 4335 - WINS_EVT_DEL_OWNER_STARTED
    The WINS server has initiated the delete owner function of the WINS partner, %2.
  • 4336 - WINS_EVT_DEL_OWNER_COMPLETED
    The WINS server has completed the delete owner function of the WINS partner, %2.
  • 4337 - WINS_EVT_WINS_GRP_ERR
    The WINS Server could not initialize security to allow the read-only operations.
  • 4338 - WINS_EVT_SPOOFING_STARTED
    The WINS server started the burst handling of incoming requests. WINS does this to handle a sudden increase of incoming requests. WINS will also log an event indicating when the burst handling stops. If you see this event frequently, you may want to upgrade the WINS server to a faster computer. You can also try to adjust the burst handling count using the WINS Manager tool.
  • 4339 - WINS_EVT_SPOOFING_COMPLETED
    The WINS server completed the burst handling of incoming requests because the queue length became a quarter of what it was when burst handling began.
  • 4340 WINS_USERS_GROUP_NAME
    WINS Users%0
  • 4341 WINS_USERS_GROUP_DESCRIPTION
    Members who have view-only access to the WINS Server%0
  • 4342 - WINS_EVT_BAD_CHARCODING
    The following name, %1, contains an incorrect format for a character code. The name has not been entered in the WINS database.The character code can be prefixed either by '\' or by '\x' or '\X'. The backslash character itself can be specified as '\\'.
  • 5300 INS_PNP_FAILURE
    WINS encountered a PnP failure that caused it to terminate. The error code is contained in the second word of the data section.

New Informational Messages (Event ID 5000 to 5299)

  • 5000 - WINS_PNP_ADDR_CHANGED
    WINS has received a PnP notification that the IP address of the server has changed. The old IP address and the new IP address are given in the second and the third words in the data section.
  • 5001 - WINS_EVT_SCV_RANGE
    WINS is scavenging the locally owned records from the database. The version number range that is scavenged is given in the data section, in the second to fifth words, in the order: from_version_number (low word, high word) to_version_number (low word, high word).
  • 5002 - WINS_EVT_SCV_CHUNK
    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 numbers) are given in the second to sixth words in the data section.
  • 5003 - WINS_EVT_QUERY_QUE_INC
    The alert limit of the query requests queue has been reached. The current queue length and the new alert limit are in the first and the second words in the data section.
  • 5004 - WINS_EVT_QUERY_QUE_DEC
    The query requests queue decreased below half of the alert limit. The current queue length and the new alert limit are in the first and the second words in the data section
Modification Type:MajorLast Reviewed:12/18/2003
Keywords:kbinfo KB316836
©2003 Microsoft Corporation. All rights reserved.