System - Wins Overview in Event Repository • MonitorWare Knowledge Base

KnowledgeBase Event Repository

This site is the central interface to the Adiscon Event Repository

Event ID

Items count

Access count

16
PRINTF MSG: %1 %2 %3 %4 %5

1

602 Views
4000
WINS encountered an error while processing the command.

1

706 Views
4001
The local WINS can not be deleted.

1

550 Views
4002
The importation from the file failed.

1

555 Views
4003
The backup failed. Was a full backup done before?

1

512 Views
4004
The backup failed. Check the directory to which you are backing the database.

1

506 Views
4005
The name does not exist in the WINS database.

1

494 Views
4006
Replication with a nonconfigured partner is not allowed.

1

2102 Views
4096
WINS has initialized its log for this invocation.

1

1217 Views
4097
WINS initialized properly and is now fully operational.

1

607 Views
4098
WINS was terminated by the service controller. WINS will gracefully terminate.

1

1011 Views
4099
WINS is being gracefully terminated by the administrator. The address of the administrator is %1.

1

563 Views
4100
WINS is being abruptly terminated by the administrator. The address of the administrator is %1.

1

540 Views
4101
WINS received a Name Request with an invalid operation code. The request is being thrown away.

1

494 Views
4102
The connection was aborted by the remote WINS. Remote WINS may not be configured to replicate with t ...

1

1567 Views
4103
***There are no records in the registry for the key.

1

470 Views
4104
***There are no pull records.

1

462 Views
4105
***There are no push records.

1

453 Views
4106
The WINS database of name-to-address mappings is empty. It could mean that aprevious invocation of W ...

1

577 Views
4107
The WINS database of owner-to-address mappings is empty. It could mean thata previous invocation of ...

1

581 Views
4108
***WINS could not read the InitTimeReplication field of the pull/push key.

1

476 Views
4109
WINS could not read the Refresh interval from the registry

1

517 Views
4110
WINS could not read the Tombstone interval from the registry

1

477 Views
4111
WINS could not read the Verify interval from the registry

1

500 Views
4112
***WINS could not read the retry count for retrying communication with a remote WINS.

1

471 Views
4113
WINS could not read the Tombstone Timeout from the registry.

1

548 Views
4114
WINS could not read the ConsistencyCheck value (type DWORD) from theParameters\\ConsistencyCheck sub ...

1

533 Views
4115
WINS could not read the MaxRecsAtATime value (type DWORD) in theWins\\Parameters\\ConsistencyCheck s ...

1

610 Views
4116
WINS could not read the UseRplPnrs value of the Wins\\Parameters\\ConsistencyCheck key. If this valu ...

1

510 Views
4117
WINS just did a consistency check on the records owned by the WINS with the address, %1.The number o ...

1

529 Views
4118
WINS could not do a consistency check on the records. This could be because WINSwas directed to do t ...

1

561 Views
4119
***WINS received a packet that has the wrong format. For example, a label may be More than 63 octets ...

1

1212 Views
4120
***No records meeting the %1 criteria were found in the WINS database.

1

505 Views
4121
WINS could not find any records in the WINS database.This means there are no active or tombstone rec ...

1

686 Views
4122
***The special group has reached its limit. WINS cannot add any more members.

1

474 Views
4123
***The address database already has reached the limit of owners. This is 100.This error was noticed ...

1

463 Views
4124
The WINS server received an update notification from the non-configured WINS server at the address, ...

1

678 Views
4125
WINS received an update notification from the WINS with the address, %1. WINS accepted it.

1

514 Views
4126
The WINS server received a pull request from the non-configured WINS server with the address, %1. Th ...

1

552 Views
4127
The datafiles key could not be opened.

1

492 Views
4128
The NetBios over TCP/IP (NetBT) key could not be opened.

1

621 Views
4129
The NetBios over TCP/IP (NetBT) key could not be queried.

1

512 Views
4130
A worker thread was created by the administrator.

1

511 Views
4131
A worker thread was terminated by the administrator.

1

478 Views
4132
The owner-address mapping table had an entry with a non-zero owner ID and an address the same as the ...

1

527 Views
4133
An error occurred while trying to inform a remote WINS to updatethe version number.

1

565 Views
4134
The local WINS is going to inform a remote WINS to update the version number ofa record. This is bec ...

1

498 Views
4135
The local WINS has been informed by a remote WINS with address, %1, to updatethe version number of a ...

1

488 Views
4136
A remote WINS requested the update of the version stamp of a record, but the record could not be fou ...

1

481 Views
4137
***A name mismatch was noticed while verifying the validity of old replicas.The local record has the ...

1

543 Views
4138
The value of the version ID counter was changed. The new value (Low 32 bits) is given in the data se ...

1

500 Views
4139
The WINS replication request is being ignored since WINS suspects that theWins\\Partners key informa ...

1

873 Views
4140
WINS is deleting all records of the WINS with owner ID, %d. This owner IDcorresponds to the address, ...

1

509 Views
4141
WINS pulled records from a WINS while doing %1. The partner's address and the owner's address whose ...

1

772 Views
4142
WINS performed a consistency check on the records. The number of records pulled, The address of the ...

1

483 Views
4143
WINS scavenged its records in the WINS database. The number of records scavenged is given in the dat ...

1

573 Views
4144
WINS scavenged replica tombstones in the WINS database. The number of records Scavenged is given in ...

1

531 Views
4145
***WINS revalidated old active replicas in the WINS database.

1

521 Views
4146
WINS Performance Monitor Counters is closing the event log.

1

515 Views
4147
WINS has deleted records of a partner. The internal ID of the partner whoserecords were deleted, the ...

1

652 Views
4148
The local WINS server received a request from a remote WINS server that is not the same version. Bec ...

1

520 Views
4149
Winsock Send could not send all the bytes. The connection could have been aborted by the remote clie ...

1

983 Views
4150
WINS adjusted the scavenging related time interval, %1, so that it is compatible with the replicatio ...

1

520 Views
4151
WINS adjusted the scavenging related time interval, %1. The adjusted value for this scavenging param ...

1

508 Views
4152
The timeout period has expired on a call to another WINS server. Assuming that the network and route ...

1

595 Views
4153
***The Scavenger thread found active replicas that needed to be verified with the owner WINS server ...

1

496 Views
4154
The name registration packet that was just received has too many addresses. The maximum number of ad ...

1

574 Views
4155
A replica clashed with the static record, %1, in the WINS database. The replica was rejected.

1

925 Views
4156
WINS could not initialize the administrator interface because of a problem with the Remote Procedure ...

1

730 Views
4157
WINS did not send a notification message to the WINS server whose address is given in the data secti ...

1

659 Views
4158
WINS received a release for the non-owned name, %1. This name is owned by the WINS whose owner ID is ...

1

580 Views
4159
The administrator deleted a record with the name, %1.

1

630 Views
4160
WINS could not start because of a database error. WINS restored the old database from the backup dir ...

1

585 Views
4161
A non-zero replication type applies for this partner. This means only a subset of records will be re ...

1

533 Views
4162
***A partner has requested only a subset of records. This means we won't replicate all the records i ...

1

498 Views
4163
WINS adjusted the Maximum Records at a time parameter of the ConsistencyCheck key. The value specifi ...

1

532 Views
4164
WINS was forced to scavenge replica tombstones of a WINS. The person with administrative rights on t ...

1

508 Views
4165
WINS has encountered an error that caused it to shut down.

1

591 Views
4166
The replication Pull thread is shutting down due to an error. Restart WINS.

1

507 Views
4167
The replication Push thread is shutting down due to an error. Restart WINS.

1

452 Views
4168
The Name Challenge thread is shutting down due to an error. Restart WINS.

1

459 Views
4169
The worker thread is shutting down due to an error. Restart WINS.

1

511 Views
4170
An abnormal error occurred during the WINS initialization. Check the application and system logs for ...

1

488 Views
4171
WINS could not properly set up the WINS database. Look at the application log for errors from the Ex ...

1

499 Views
4172
A worker thread could not be created. The computer may be low on resources.

1

484 Views
4173
A thread could not be created. The computer may be low on resources.

1

487 Views
4174
An event could not be created.

1

453 Views
4175
***The Name Challenge Request thread could not be created.

1

437 Views
4176
A registry key could not be created or opened.

1

425 Views
4177
The WINS configuration key could not be created or opened. Check to see if the permissions on the ke ...

1

454 Views
4178
The WINS Pull configuration key could not be created or opened. Check to see if the permissions on t ...

1

428 Views
4179
The WINS Push configuration key could not be created or opened. Check to see if the permissions on t ...

1

499 Views
4180
The WINS\Parameters key could not be created or opened. Check to see if the permissions on the key a ...

1

459 Views
4181
The WINS\Parameters\ConsistencyCheck subkey could not be created or opened. This key should be there ...

1

793 Views
4182
The registry change notification event could not be created. Check to see if system resources are lo ...

1

521 Views
4183
The correct time format is hh:mm:ss. Check the value of SpTime in the registry.

1

544 Views
4184
The registry notification function returned an error.

1

478 Views
4185
***The Name Registration Response could not be sent due to an error. This error was encountered by a ...

1

505 Views
4186
***The Name Registration Response could not be sent due to an error. Thiserror was encountered by a ...

1

462 Views
4187
The Name Registration Response could not be sent due to an error. This error was encountered by the ...

1

502 Views
4188
The Name Release Response could not be sent due to an error. This error is often caused by a problem ...

1

538 Views
4189
The Name Query Response could not be sent due to an error. This error is often caused by a problem w ...

1

532 Views
4190
A record could not be registered because it already existed. However, the same record then could not ...

1

577 Views
4191
WINS could not create a heap because of a resource shortage. Check to see if the computer is running ...

1

822 Views
4192
An error occurred from which WINS will try to recover. If the recovery fails, check previous event l ...

1

599 Views
4193
WINS could not create the notification socket. Make sure the TCP/IP driver is installed and running ...

1

1152 Views
4194
WINS could not create the User Datagram Protocol (UDP) socket to listen for Connection notification ...

1

541 Views
4195
WINS could not create the TCP socket for listening to TCP connections. Make sure the TCP/IP driver i ...

1

542 Views
4196
WINS could not create the TCP socket for making a TCP connection. Make sure the TCP/IP stack is inst ...

1

525 Views
4197
An address could not bind to a socket. Make sure the TCP/IP stack is installed and running properly. ...

1

528 Views
4198
WINS could not listen on the Winsock socket.

1

564 Views
4199
Winsock Select returned with an error.

1

502 Views
4200
***%1 returned with an error code of %2.

1

460 Views
4201
WINS created a socket and called the 'bind' WinSock API to bind a handle to it. On calling 'getsockn ...

1

546 Views
4202
An attempt to connect to the remote WINS server with address %1 returned withan error. Check to see ...

1

824 Views
4203
WINS could not accept on a socket.

1

562 Views
4204
WINS could not read from the User Datagram Protocol (UDP) socket.

1

1828 Views
4205
WINS could not read from NetBIOS over TCP/IP (NetBT).

1

640 Views
4206
WINS could not close a socket.

1

519 Views
4207
***A Winsock Sendto message could not send all the bytes.

1

509 Views
4208
WINS could not send a User Datagram Protocol (UDP) message to a WINS client.

1

819 Views
4209
A Winsock Sendto message returned with an error.

1

633 Views
4210
***The Winsock receive function returned with an unexpected error.

1

438 Views
4211
The WinSock send function returned with an unexpected error.

1

518 Views
4212
A message was received on an association. The association is in a bad state.This indicates a bug in ...

1

488 Views
4213
WINS could not allocate a responder association. Check to see if the system is low on resources.

1

486 Views
4214
***WINS could not allocate an initiator association. Check to see if the system is low on resources.

1

487 Views
4215
***WINS could not allocate an implicit dialogue. Check to see if the system is low on resources.

1

467 Views
4216
***WINS could not allocate an explicit dialogue. Check to see if the system is low on resources.

1

467 Views
4217
WINS could not look up the association block for a NetBIOS over TCP/IP (NetBT) association. Check to ...

1

532 Views
4218
WINS could not allocate a User Datagram Protocol (UDP) Buffer. Check to see if the system is low on ...

1

493 Views
4219
***WINS could not free a User Datagram Protocol (UDP) Buffer. Restart WINS.

1

482 Views
4220
***WINS could not create a communication subsystem thread. Check to see if the system is low on reso ...

1

478 Views
4221
A WINS thread could not signal the main thread after closing its session.This would be caused by the ...

1

535 Views
4222
A WINS thread could not signal a handle.

1

465 Views
4223
A WINS thread could not reset a handle.

1

503 Views
4224
WINS encountered a database error. This may or may not be a serious error.WINS will try to recover f ...

1

806 Views
4225
WINS could not update the record with the name, %1. Check the application log for the Exchange compo ...

1

518 Views
4226
WINS could not update the Owner ID-to-Address mapping table in the database.This means the in-memory ...

1

629 Views
4227
The Push Thread was requested for a range of records but could not find any records in the range. Ma ...

1

761 Views
4228
The Timer thread could not be signaled. This indicates this computer is extremely overloaded or that ...

1

830 Views
4229
***The Timer could not signal the client thread.

1

507 Views
4230
***WINS could not get information about a key. Check to see if the permissions on the key are set pr ...

1

490 Views
4231
WINS could not get information about the Pull key. Check to see if the permissions on the key are se ...

1

492 Views
4232
WINS could not get information about the Push key. Check to see if the permissions on the key are se ...

1

474 Views
4233
WINS could not get information about the DATAFILES key. Check to see if the permissions on the key a ...

1

493 Views
4234
WINS could not get information about the SPEC_GRP_MASKS key. Check to see if the permissions on the ...

1

474 Views
4235
WINS could not open a Pull subkey. Check to see if the permissions on the key are set properly, syst ...

1

509 Views
4236
WINS could not open a Push subkey. Check to see if the permissions on the key are set properly, syst ...

1

500 Views
4237
WINS could not get the time interval from a Pull record.

1

673 Views
4238
***WINS could not get the time interval from a Push record.

1

588 Views
4239
WINS could not get the update count from a Push record. No default will be used.

1

744 Views
4240
WINS could not close an open key. Check to see if the permissions on the key are set properly, syste ...

1

455 Views
4241
WINS Timer thread encountered an exception.

1

455 Views
4242
WINS Push thread encountered an exception. A recovery will be attempted.

1

572 Views
4243
WINS Pull thread encountered an error during the process of sending a push notification to another W ...

1

1230 Views
4244
A WINS Remote Procedure Call (RPC) thread encountered an error.

1

436 Views
4245
The WINS TCP Listener thread encountered an error.

1

772 Views
4246
The WINS User Datagram Protocol (UDP) Listener thread encountered an error.

1

537 Views
4247
The WINS Scavenger thread encountered an error.

1

539 Views
4248
The WINS Challenger thread encountered an error.

1

531 Views
4249
A WINS worker thread encountered an error.

1

507 Views
4250
The WINS Scavenger thread could not scavenge a record. This record will be ignored. The Scavenger wi ...

1

491 Views
4251
The WINS Replication Pull Handler could not connect to a WINS server.All retries failed. WINS will t ...

1

604 Views
4252
WINS did not find any subkeys under the Pull key.

1

591 Views
4253
WINS did not find any subkeys under the Push key.

1

662 Views
4254
An error has prevented WINS from updating the WINS database. The database may becorrupt.

1

508 Views
4255
***WINS has been asked to pull entries from itself. Check all the Pull subkeys of this WINS.

1

530 Views
4256
WINS was unable to propagate the push trigger.

1

509 Views
4257
WINS sent a name query or a name release with a certain transaction ID.It received a response to the ...

1

524 Views
4258
The WINS database is inconsistent. The number of owners found in the name-address mapping table are ...

1

557 Views
4259
The local WINS requested a remote WINS to update the version number ofa database record owned by the ...

1

493 Views
4260
WINS received an error while registering replicas. It will not register anyadditional replicas of th ...

1

700 Views
4261
WINS received an error while trying to register a group's replica with name, %1.The replica is owned ...

1

563 Views
4262
WINS received an error while trying to register the unique entry with the name, %1.

1

449 Views
4263
WINS received an error while trying to register the group entry with the name, %1.

1

495 Views
4264
WINS received an error while trying to update the version number of a record inthe WINS database.

1

509 Views
4265
WINS received an error while trying to release a record in the WINS database.

1

500 Views
4267
WINS received an error while trying to query a record in the WINS database.

1

478 Views
4268
WINS received a replica whose state is incorrect. For example, the state maybe RELEASED or the repli ...

1

484 Views
4269
The Scavenger thread was unable to change its priority level.

1

478 Views
4270
***A name release request was received for a record that didn't match theunique or group type indica ...

1

527 Views
4271
A name release request was received for the record name, %2, that did nothave the same address as th ...

1

527 Views
4272
An error was encountered while trying send a push trigger notification to aremote WINS. The exceptio ...

1

486 Views
4273
An error was encountered while trying to service a pull range request from aremote WINS. The excepti ...

1

456 Views
4274
WINS was either provided a bad command code or it became corrupt.

1

450 Views
4275
The static data file that is used to initialize the WINS database is too big.

1

688 Views
4276
An error was encountered during an operation on the static data file, %1.

1

519 Views
4277
The name of the file, after expansion, is bigger than WINS can handle. The condensed string is, %1.

1

504 Views
4278
WINS could not do a static initialization.

1

454 Views
4279
An error occurred during the configuration or reconfiguration of WINS.If this was encountered during ...

1

510 Views
4280
An error occurred during the configuration or reconfiguration of WINS.

1

458 Views
4281
A lock error has occurred. This could happen if the WINS is trying to send aresponse on a dialogue t ...

1

561 Views
4282
WINS could not import static mappings from the file, %1.Verify that the file exists and is readable.

1

516 Views
4283
WINS encountered an error while processing a push trigger or update notification. The error code is ...

1

1376 Views
4284
WINS encountered an exception while processing a pull trigger.

1

462 Views
4285
WINS encountered an exception while retrieving data records.

1

516 Views
4286
The WINS server cannot make or accept this connection since the connections limit has been reached. ...

1

533 Views
4287
The exception was encountered during the processing of a group member.

1

799 Views
4288
The Scavenger thread encountered an error while cleaning up the owner-addresstable. It will try agai ...

1

510 Views
4289
WINS is trying to update the version number of a database record that itdoes not own. This is a seri ...

1

489 Views
4290
The special group mask specified is not valid. It has either a non-hexadecimal character or is less ...

1

477 Views
4291
WINS tried to get its addresses but failed. WINS will recover when the IP address comes back.

1

710 Views
4292
WINS did not get back any names from NetBIOS over TCP/IP (NetBT) when it did an adapter status.

1

552 Views
4293
WINS could not initialize properly with the security subsystem.At initialization, WINS creates a sec ...

1

523 Views
4294
The client application does not have the permissions required to execute the function.

1

1797 Views
4295
When WINS replicated with its partners, one of the partners showed there was more data that actually ...

1

1159 Views
4296
Too many concurrent static initializations are occurring. The number of such initializations current ...

1

508 Views
4297
WINS encountered a low memory condition. Check to see if the system is running out of virtual memory ...

1

614 Views
4298
WINS found some database corruption. The record named, %1, is corrupt.It could be that recovery from ...

1

507 Views
4299
The following name, %1, is too long. It has been entered in the WINS database.If you want the name t ...

1

502 Views
4300
The record with the name, %1, has bad address. It has not been entered in the WINS database.

1

480 Views
4301
The computer running the WINS server does not have a valid address.When WINS requested an address, i ...

1

564 Views
4302
WINS encountered an error doing a database backup to directory %1.

1

588 Views
4303
WINS encountered an error while deleting the file, %1.

1

516 Views
4304
WINS encountered an error while deleting one or more records of a WINS.The WINS address is in the se ...

1

572 Views
4305
WINS encountered an error while getting the browser names for a client.

1

489 Views
4306
The length of the message sent by another WINS indicates a very big message.There may have been corr ...

1

857 Views
4307
The WINS replicator Pull thread encountered an error while processing a request.Check other log entr ...

1

1551 Views
4308
***WINS does not support this functionality.

1

514 Views
4309
This WINS computer has %1 processors. It has %2 bytes of physical memory and %3 bytes of memory avai ...

1

499 Views
4310
The record named, %1, could not replace another record in the WINS database.The record's version num ...

1

458 Views
4311
WINS has found some database corruption. It will try to recover.This recovery process can take a lon ...

1

990 Views
4312
WINS has exceeded the wait time for all threads to terminate. The number ofthreads still active is g ...

1

517 Views
4313
The name, %1, is in the wrong format. It has not been put in theWINS database. Check to see if you h ...

1

512 Views
4314
WINS Performance Monitor Counters could not get the WINS statistics.

1

1944 Views
4315
WINS Performance Monitor Counters could not open the event log.

1

521 Views
4316
***WINS could not open the log file. Check the log path specified in the registryunder WINS\\Paramet ...

1

519 Views
4317
WINS found a name in the WINS database with a length of more than 255 characters. The name was trunc ...

1

468 Views
4318
WINS could not start due to a missing or corrupt database.Restore the database using WINS Manager (o ...

1

715 Views
4319
WINS could not start because the existent database must be converted to theWindows 2000 format. If t ...

1

539 Views
4320
WINS will not start because the existing WINS database needs to be converted to the Windows 2000 for ...

1

503 Views
4321
The NoOfWrkThds parameter's value is too large and cannot be supported.

1

1730 Views
4322
WINS could not come up because the existing WINS database needs conversion to the Windows 2000 forma ...

1

549 Views
4323
WINS could not start because the existing database needs to be converted to the Windows 2000 format. ...

1

513 Views
4324
WINS cannot start because the existing WINS database needs conversion to theWindows 2000 format. WIN ...

1

474 Views
4325
***WINS could not read the Initial Challenge Retry Interval from the registry.

1

1452 Views
4326
WINS could not read the Challenge Maximum Number of Retries from the registry.

1

1230 Views
4327
Adminstrator '%1' initiated a backup of the WINS database.

1

505 Views
4328
Adminstrator '%1' has initiated a scavenging operation.

1

508 Views
4329
The WINS server has started a scavenging operation.

1

424 Views
4330
The WINS server has completed the scavenging operation.

1

513 Views
4331
Adminstrator '%1' has initiated a consistency check operation.

1

589 Views
4332
The WINS server has started a consistency check operation.

1

570 Views
4333
The WINS server has completed the consistency check operation.

1

460 Views
4334
Adminstrator '%1' has initiated the delete owner function of the WINS partner, %2.

1

515 Views
4335
The WINS server has initiated the delete owner function of the WINS partner, %2.

1

477 Views
4336
The WINS server has completed the delete owner function of the WINS partner, %2.

1

464 Views
4337
The WINS Server could not initialize security to allow the read-only operations.

1

904 Views
4338
The WINS server started the burst handling of incoming requests. WINS does this to handle a sudden i ...

1

534 Views
4339
The WINS server completed the burst handling of incoming requests because the queue length became a ...

1

469 Views
4340
WINS Users%0

1

451 Views
4341
Members who have view-only access to the WINS Server%0

1

477 Views

About the KnowledgeBase Event Repository

This is a repository of known Windows Events, hopefully together with a description of what it means, when it appears and how to troubleshoot it. The event repository was initially provided as a tool for parser creation but has since evolved. It is now part of the overall knowledgebase in the hope that it provides a useful service to the community. Please add your comments and questions (which we try to answer), as this increases the event repository usefulness for all of us.