Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
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.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the WINS service?
What is the role of WINS.MDB file and how can be compacted?
This behavior occurs because the WINS database is corrupt or could not be found in the %SystemRoot%\System32\Wins directory. The error messages indicate that the WINS database is not running because of a corrupt, missing, or renamed Wins.mdb file. See ME205100 for more information about this problem. The article applies to Microsoft Windows NT Server 4.0.
See ME943514 and MSW2KDB for additional information about this event.
This behavior can occur if the WINS database is damaged or is missing from the %SystemRoot%\system32\wins folder. See ME225346 to fix this problem. The article applies to Microsoft Windows 2000.
|Private comment: Subscribers only. See example of private comment|
|Links: ME205100, ME225346, ME943514, MSW2KDB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated