Microsoft KB Archive/225346

= Err Msg: WINS Could Not Come Up Due to Missing/Corrupt... =

Article ID: 225346

Article Last Modified on 2/23/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server

-



This article was previously published under Q225346



SYMPTOMS
When you start your Windows 2000 Server-based computer running the Windows Internet Name Service (WINS), you may receive the following 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. To do this:

1) Delete all the files in the %SystemRoot%\system32\wins directory Note: if 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) Net start wins

Please click on OK to terminate WINS.

Also, you may experience one or more of the following symptoms:

 Events may have been registered in the Event Viewer. To view these errors:

 Click Start, point to Programs, point to Administrative Tools, and then click Event Viewer. View the Source column to locate the following event ID numbers:

EVENT ID 4318

Source: WINS

NOTE: The description area error message matches the error message listed earlier in this article.  One or more of the following events may be listed in the System log:

 

Event ID 4224

Source: WINS

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 event viewer for the eseXX 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 database from a backup. The error number is in the second DWORD of the data section below.

 

Event id 7023

Source: Service Control Manager

The Windows Internet Name Service terminated with the following error: %%3758096385

</li></ul> </li> One or more of the following application events may be listed in Event Viewer and the Application log file:

<ul> 

Event ID 100

Source: ESENT

Category: General

wins (596) The database engine 6.00.3801.0007 started.

</li> 

Event ID 300

Source: ESENT

Category: Logging/Recovery

wins (596) The database engine is initiating recovery steps.

</li> 

Event ID 301

Source: ESENT

Category: Logging/Recovery

wins (596) The database engine is replaying log file C:\Winnt\system32\wins\j50.log.

</li> 

Event ID 302

Source: ESENT

Category: Logging/Recovery

wins (596) The database engine has completed recovery steps.

</li></ul> </li> When you try to start WINS, you may receive the following error message:

Could not start the Windows Internet Name Service (WINS) on the Local Computer. Error 3758096385

</li></ul>

<div class="cause_section">

CAUSE
This behavior can occur if the WINS database is damaged or is missing from the %SystemRoot%\system32\wins folder.

<div class="resolution_section">

RESOLUTION
To resolve this issue, replace the WINS database by moving or backing up all of the files in the %systemroot%\system32\wins folder to a new location:

 In WINS Manager, stop replication partners.</li> Create backup copies of the files in the %systemroot%\system32\wins folder, or delete these files.</li> In Computer Manager, restart WINS:

 Click Start, point to Programs, point to Administrative Tools, and then click Computer Management.</li> Double-click the System Tools branch to expand it.</li> Click Services in the Container (left) pane to display the computer services in the Objects (right) pane.</li> Right-click Windows Internet Name Service in the right pane, and then click Start.</li></ol>

NOTE: You must reregister the other server's and computer's services in the environment in the WINS database. To do so, restart the appropriate computers, or reregister their services. For information about how to do so, please see the following article in the Microsoft Knowledge Base:

137423 How to Reregister Services in WINS

</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

<div class="moreinformation_section">

MORE INFORMATION
Windows 2000 uses the same Event ID numbers as Microsoft Windows NT version 4.0 to indicate that a WINS database is not running due to a missing or damaged Wins.mdb file.

Additional query words: 2000

Keywords: kbenv kbnetwork kbprb kbui KB225346

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.