| Event Id | 4114 |
| Source | Wins |
| Description | WINS could not read the ConsistencyCheck value (type DWORD) from the Parameters\\ConsistencyCheck subkey in the registry. The first consistency check is done at the time specified in the SpTime entry under the ConsistencyCheck subkey and is limited by the MaxRecsAtATime value. If the time is not specified, the check is done at 2 am. To correct the problem, open the registry and verify that the ConsistencyCheck subkey has been correctly sent up and all required values have been set. Correct the values, as needed. |
| Event Information | According to Microsoft: Cause: A ConsistencyCheck value was expected because a ConsistencyCheck subkey was created in the WINS\Parameters subkey. The ConsistencyCheck value is used by WINS to do periodic database consistency checks. The first consistency check is done at the time specified in the SpTime value under the ConsistencyCheck key and limited by the MaxRecsAtATime value. If the time is not specified, the check is done at 2 am. User Action: Open the registry and verify that the ConsistencyCheck entry has been correctly set up and all required values have been set. Correct the values as needed. |
| Reference Links | WINS could not read the ConsistencyCheck value |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.