Loads of errors? It still would have helped if you mentioned the gist of them.
So what antivirus are you using?
It appears that your WLMail database is corrupted but WLMail was unable to recover it from a backup, or do a full recovery for some reason.
There are several things you can try, so I will mention a couple from the least to most dramatic. I won't bother you with Esentutl though, since replacing the database is a better option I think.
First though, to be certain your messages remain safe, please make a backup/copy of your WLMail Message Store*.
1. Restore the database backup:
Navigate to your WLMail Message Store folder*.
Within it, you will find the database file called 'Mail.MSMessageStore'. After ensuring that the backup** of the database is in place within the folder Backup\new, delete the database file 'Mail.MSMessageStore'.
When WLMail is restarted, it should automatically restore the database file from the backup. A few messages within the Message Store may be 'recovered' during the process and moved to a folder called 'Recovered items' under 'Storage folders'.
If the problem remains:
2. Force a full recovery of database and messages:
During a full recovery, your database will be re-created, and all your folders/messages will be moved into subfolders of a folder called 'Recovered items' under 'Storage folders'.
Navigate to your WLMail Message Store folder*.
Within it, you will find the database file called 'Mail.MSMessageStore'. Delete the backup of the database within the folder Backup\new (if a recent compaction of the database has occurred, this backup may not exist).
Delete the database file 'Mail.MSMessageStore'.
When WLMail is restarted, it will automatically re-create the database file, and all e-mail messages within the Message Store will be 'recovered' and moved to appropriately named subfolders within a folder called 'Recovered items' under 'Storage folders'.
Be aware that any messages left on your Mail Service Provider's server for a POP3 account, may be re-downloaded.
You should wait for the new database to index all your relocated messages (may take hours, with high processor usage) before beginning to move them out of the 'Recovered items' folder.
Do not move any folders out of the 'Recovered' items folder. Rather, create a new folder in the desired location and move the recovered messages into it.
You can delete the 'Recovered items' folder when you have moved all of the messages out of it, but be aware that doing so will break the Quick views. To repair the Quick views, see http://liveunplugged.spaces.live.com...90CA!205.entry
*Note that Windows Live Mail's Message Store, in its default location, is a hidden folder, so ensure "Show hidden files and folders" is checked under Folder Options in Windows Explorer.
The default location for XP is: C:\Documents and Settings\<USER_NAME>\Local Settings\Application Data\Microsoft\Windows Live Mail
**After deleting the database file, as long as there is a backup of the database file 'Mail.MSMessageStore' within the ...Backup\new folder, the database will simply be restored from the backup with minimal drama upon next restart of WLMail. However, if that backup has not yet been created, such as after a database compaction has recently occurred, then a *full* recovery of the database and messages/folders will occur.
The above solutions would normally repair problems associated with the database.
(Windows Vista Home Premium SP1 with Windows Live Mail Beta 14.0.5027.0908)
"There are more things in Heaven and earth, Horatio, than are dreamt of in your philosophy." - Shakespeare
"Michael" <Michael@xxxxxx> wrote in message news:93128ABB-A51A-433C-8B99-4C75C13FA909@xxxxxx
> Hi All,
> I am having problems stating up Windows Live Mail. hat happens is, I get a
> loads of errors which come up. There is to much error information to display
> so I will copy what is in the event viewer. The error is:
> wlmail (3060) Database recovery/restore failed with unexpected error -515.
> For more information, see Help and Support Center at
> Product: Windows Operating System
> ID: 454
> Source: ESENT
> Version: 5.2
> Symbolic Name: RESTORE_DATABASE_FAIL_ID
> Message: %1 (%2) %3Database recovery/restore failed with unexpected error %4.
> The ESENT storage engine could not automatically recover data when the
> system stopped responding or the power failed. As a result, database data is
> now unavailable.
> Typically, this error occurs because an anti-virus program is actively
> scanning ESENT files.
> User Action
> Do one or all of the following:
> Verify that anti-virus software is not actively scanning ESENT files.
> Restart the database program to see whether the error occurs again. If it
> does, and a database backup is available, restore the database data from the
> backup. Otherwise run a program-specific utility, such as Esentutl.exe or
> Ntdsutil.exe, to repair the data.
> I hope this Information can help to srtot out my problem it has only just
> started to do this.
> I am using Windows XP Home SP3