Link to home
Start Free TrialLog in
Avatar of dcadler
dcadler

asked on

W2008R2 and RDSH showing event 215 ESENT Errors

I have a Windows 2008R2 server running as a Remote Desktop Session Host Server. In the Application Event Log, I keep getting the following error;

Event ID: 215
Source: ESENT
Task Category: Logging/Recovery
Message: WinMail (41748) WindowsMail0: The backup has been stopped because it was halted by the client or the connection with the client has failed.

The errors started showing up as new user accounts started logging in at 8:00am.

I don't understand the reference to WinMail as I am not using any mail client on the server, that I am aware of.

I am using roaming profiles and folder redirection via group policy linked to the RDSH server OU, if that makes any difference.

My clients are Windows XP SP3 running a client called ThinLaunch to lock it down and automatically present the RDSH Server login

Any ideas?
Avatar of Tehzar
Tehzar
Flag of United States of America image

I experienced something similar when I was backing up exchange in the past, this is what resolved it for me, hope it helps:

http://support.microsoft.com/kb/810333


ZaR
Avatar of dcadler
dcadler

ASKER

The thing is, I am not running a backup. This is a Windows Server 2008R2 running Remote Desktop Session Host. I do not even have the Windows Backup role installed. I do not have Exchange installed. I do not have any mail system installed. This is an out of the box install with just the file server and Remote Desktop Services roles installed.
ASKER CERTIFIED SOLUTION
Avatar of Tehzar
Tehzar
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of dcadler

ASKER

I have LightSpeed AV installed but real-time scan is disabled. I will check indexing
Avatar of dcadler

ASKER

Your recommendation has stopped the ESENT Errors. I believe the solution was when I turned off Indexin ,  Thanks.
Glad to hear it, please let me know if the issue resurfaces

v/r

ZaR