WINS May Report Database Corruption w/ More Than 100 Owners

Last reviewed: September 16, 1997
Article ID: Q162778

The information in this article applies to:

Microsoft Windows NT Server version 4.0

SYMPTOMS

You have configured a Windows NT 4.0 WINS server to pull records from more than 100 replication partners, or to participate in replication involving more than 100 owners.

On stopping and attempting to restart the WINS service, you observe the error message:

   WINS could not come up due to missing/corrupt database. Restore the
   database using WINS Manager or Winscl.exe (in the res kit) and then
   restart WINS. If WINS still does not come up, start with a fresh copy
   of the database.

Restoring the database has no effect on the problem. The WINS service cannot be restarted.

CAUSE

The WINS service encountered an access violation when initializing, or when pulling records from a replication partner.

NOTE: The WINS service does not create an event log entry and Dr. Watson does not record the access violation.

RESOLUTION

To correctly support configurations involving more than 100 owners or replication partners, apply the fix mentioned below.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

Additional query words: wins.mdb crash heap prodnt
Keywords : kbbug4.00 kbfix4.00 kbfix4.00.sp3 NTSrv nttcp kbnetwork
Version : 4.0
Platform : winnt
Issue type : kberrmsg
Solution Type : kbservicepack

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 16, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.