Greetings Skywolfe,
ESENT is the built-in database in Windows that most Microsoft applications use (or the
technology there-in). It supports all sorts of fun recovery options and is actually pretty
neat.
I can't say I've never noticed this happening for me, but I don't monitor my event log that
closely when there's no problems. If the contacts database is corrupted in some way, I don't
doubt you'll get what you experienced as it's key to Messenger working.
Almost all the data in here is a cache, so with Messenger and other "Live" applications
closed (so that wlcomm isn't running), you can just delete that Windows Live Contacts folder
if you really want to. The next time you sign in, what's needed will be re-downloaded from
the server. What isn't stored on the server is the Background settings per contact, but I'm
sure you can just set those up again (if you've even bothered with it in 2009, which I very
much doubt). There's no need for you to really do anything though if it's working.
--
Jonathan Kay
Microsoft MVP - Windows Live Messenger
MSN Messenger/Windows Messenger
MessengerGeek Blog:
http://www.messengergeek.com
Messenger Resources:
http://messenger.jonathankay.com
(c) 2009 Jonathan Kay - If redistributing, you must include this signature or citation
--
"Rage Skywolfe" <RageSkywolfe@xxxxxx> wrote in message
news
14A0AE6-DCE2-42C8-87EF-921F26BA4688@xxxxxx
Quote:
> I got several ESENT Errors today after trying to get messenger started after
> a restart. here are the error files listed.
>
> wlcomm (3280) The log range read from the file "C:\Documents and
> Settings\Skywolfe\Local Settings\Application Data\Microsoft\Windows Live
> Contacts\{b5f8b34d-4ae0-4827-86f3-f695998be313}\DBStore\LogFiles\edb.log" at
> offset 2342400 (0x000000000023be00) for 512 (0x00000200) bytes failed
> verification due to a range checksum mismatch. The read operation will fail
> with error -501 (0xfffffe0b). If this condition persists then please restore
> the logfile from a previous backup.
>
> wlcomm (3280) Corruption was detected during soft recovery in logfile
> C:\Documents and Settings\Skywolfe\Local Settings\Application
> Data\Microsoft\Windows Live
> Contacts\{b5f8b34d-4ae0-4827-86f3-f695998be313}\DBStore\LogFiles\edb.log. The
> failing checksum record is located at position 4575:378. Data not matching
> the log-file fill pattern first appeared in sector 4575. This logfile has
> been damaged and is unusable.
>
> wlcomm (3280) The log range read from the file "C:\Documents and
> Settings\Skywolfe\Local Settings\Application Data\Microsoft\Windows Live
> Contacts\{b5f8b34d-4ae0-4827-86f3-f695998be313}\DBStore\LogFiles\edb.log" at
> offset 2342400 (0x000000000023be00) for 512 (0x00000200) bytes failed
> verification due to a range checksum mismatch. The read operation will fail
> with error -501 (0xfffffe0b). If this condition persists then please restore
> the logfile from a previous backup.
>
> wlcomm (3280) Corruption was detected during soft recovery in logfile
> C:\Documents and Settings\Skywolfe\Local Settings\Application
> Data\Microsoft\Windows Live
> Contacts\{b5f8b34d-4ae0-4827-86f3-f695998be313}\DBStore\LogFiles\edb.log. The
> failing checksum record is located at position 4575:378. Data not matching
> the log-file fill pattern first appeared in sector 4575. This logfile has
> been damaged and is unusable.
>
> wlcomm (3280) The log range read from the file "C:\Documents and
> Settings\Skywolfe\Local Settings\Application Data\Microsoft\Windows Live
> Contacts\{b5f8b34d-4ae0-4827-86f3-f695998be313}\DBStore\LogFiles\edb.log" at
> offset 2342400 (0x000000000023be00) for 512 (0x00000200) bytes failed
> verification due to a range checksum mismatch. The read operation will fail
> with error -501 (0xfffffe0b). If this condition persists then please restore
> the logfile from a previous backup.
>
> wlcomm (3280) Corruption was detected during soft recovery in logfile
> C:\Documents and Settings\Skywolfe\Local Settings\Application
> Data\Microsoft\Windows Live
> Contacts\{b5f8b34d-4ae0-4827-86f3-f695998be313}\DBStore\LogFiles\edb.log. The
> failing checksum record is located at position 4575:378. Data not matching
> the log-file fill pattern first appeared in sector 4575. This logfile has
> been damaged and is unusable.
>
> wlcomm (3280) Database recovery/restore failed with unexpected error -501.
>
> wlcomm (3280) The log range read from the file "C:\Documents and
> Settings\Skywolfe\Local Settings\Application Data\Microsoft\Windows Live
> Contacts\{b5f8b34d-4ae0-4827-86f3-f695998be313}\DBStore\LogFiles\edb.log" at
> offset 2342400 (0x000000000023be00) for 512 (0x00000200) bytes failed
> verification due to a range checksum mismatch. The read operation will fail
> with error -574 (0xfffffdc2). If this condition persists then please restore
> the logfile from a previous backup.
>
> and this one
>
> wlcomm (3280) Corruption was detected during hard recovery in logfile
> C:\Documents and Settings\Skywolfe\Local Settings\Application
> Data\Microsoft\Windows Live
> Contacts\{b5f8b34d-4ae0-4827-86f3-f695998be313}\DBStore\LogFiles\edb.log. The
> failing checksum record is located at position 4575:378. Data not matching
> the log-file fill pattern first appeared in sector 4575. This logfile has
> been damaged and is unusable.
>
> the first one was after starting messenger the window wouldn't come up
>
> second time it came up with the sign in logon window. tuped both e mail and
> pass and it didn't do anything when I clicked the sign in button.
>
> after that I was able to get it loaded fine. I just wondered what happened
> and how you clear the windows live contacts folder or restore files that are
> corrupted.
>
> I am using WLM 9.0
>
> --
> Four Generations Of Trust And Betrayal...One Legacy
>
> Skywolfe