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.
taskhostex (2524) The database cache size maintenance task has taken 60 seconds without completing. This may result in severe performance degradation. Current cache size is 30 buffers above the configured cache limit (114 percent of target). Cache size maintenance evicted 8 buffers made 11662 flush attempts and successfully flushed 0 buffers. It has run 14358 times since maintenance was triggered.
|English: Request a translation of the event description in plain English.|
From a support forum:
"I have been having the same issue with ESENT 910 event on win8, system becomes unstable and some programs don't work properly, logging out and logging back in does not fix the problem, a restart does. However I have come across a temporary quick fix, kill the program with the instance ID that the event gives. My problem seems to be somewhere in svchost (netsvc), killing the process fixes the stability issues and everything works fine, until whatever triggers the problem happens again. I did not check which service is causing the error, will try to pin it down if it happens again.
After the error happened again and some further investigation, it seems like Windows Update Service is the problem. To fix it, go to control panel-troubleshooting and run Windows Update Repair, after the repair, remove the cached Windows Update files, you can do this by right-clicking on c: drive-properties-Disk Clean-up once it opens and scans the system, select Clean up system files, it will do another scan, select Windows Update Cache files and free the space, clean up the other unneeded files too. It looks like that fixes the problem."
See EV100396 (Piles of ESENT id 910 warnings) for the original posting.
The PID mentioned is the number listed in the event description right after the process that reported the problem. For the example shown above, the process would be taskhostex and the PID 2524. To see the PID, open the Task Manager and using the View, Select Columns menu, check the PID (Process Identifier) option.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated