|
| This event can occur if the WINS database is not running because of a corrupt, missing, or renamed Wins.mdb file.
The file should be located in the %SystemRoot%\System32\Wins folder.
If there is insufficient privilege to the WINS directory or files, this event may also occur at service startup. See Microsoft Knowledge Base Article Q158865 for more details. |
| |
|
If the database is determined to be corrupt, you will probably need to restore from your most recent backup. To do so, use the WINS Manager. Detailed instruction are given in Microsoft Knowledge Base article
Q205100.
|
| |
|
Microsoft Knowledge Base Article: Q162778
WINS May Report Database Corruption w/ More Than 100 Owners
Microsoft Knowledge Base Article Q158865
WINS Fails to Start After Changing File Permissions
Microsoft Knowledge Base
Search for articles about WINS event 4224
Microsoft Knowledge Base
Search for articles about WINS events in general
|
| |
|
Windows 2000 message text:
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.
Windows NT 4.0 message text:
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. |
| |
|
| WINS event 4224 |
| |
|
| This particular event can cause an "event flood" because whenever the WINS database is not available, it potentially affects a large number of machines, each of which generates an event indicating that it, along with all the others, cannot communicate with the WINS DB.
Under these circumstances, getting an alert from each machine having a WINS communication problem is probably not productive. Therefore this rule consolidates all these events. It counts how many events occur in the specified period of time (default is 3600 seconds (1 hour)). If the "threshold" (default is 5000 events) specified in the associated alert rule for this event is reached, a single alert will be sent.
You can adjust the period of time over which these events are consolidated. Increasing the number of seconds makes it more likely that the threshold configured in the associated alert rule will be met. Decreasing the number makes it less likely. Adjust both values to tune this alert to your network. |
| |
|
Home