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.
LiveComm (4900) C:\Users\PCR\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9b910266200f7c39\120712-0049\: A request to read from the file "C:\Users\PCR\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\9b910266200f7c39\120712-0049\DBStore\livecomm.edb" at offset 1449984 (0x0000000000162000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
|English: Request a translation of the event description in plain English.|
From a support forum: "You need not to worry for this type of events.
- Edb.log. This is a transaction log. Any changes made to objects in Active Directory are first saved to a transaction log.
- Livecomm.edb is a tool designed to read, decode and extract information contained within the Windows Live Mail Store livecomm.edb data file. The livecomm.edb file can contain email related information in use by the Microsoft Live Windows Mail applications.
All events are related to mail exchange they are not related to hard drive. You get Event 532 when logon attempt failed and you need not worry for this Event. When the shadow header page of file was damaged you get Event 472 which is again no cause of worrying."
Several support forums posts suggest verifying the hard disk for errors using chkdsk (T730714) as well as esentutl.exe.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated