Hi Team, I was checking my event log. I got a warning source: ftdisk, category: disk, event ID 57, warning: failed to flush transaction log error..etcI checked out microsoft KB article about it http://support.microsoft.com/kb/885688 and it mentions "clustering" ....I don't have this server clustered at all actually. It's a stand alone box exchange box 2003 std under windows 2003 std server. I checked the log to see how many times this event had pop up. Only three times. Once back in june, last month and this month. only those three times..hmmm????anyway....anybody have any recommendations or suggestions as to what angle i need to approach here from a troubleshooting perspective?Thanks in advance.

Could be storage issues, yes. What time did these events occur? Anything else going on at the same time? Backups, AV Scans , other event log errors? ( Can you post the exxact error as well?)How do you have the server configured? Placement of store, trans logs, etc...?Also, run ExBpa against the server for a health check.

Thanks Andy, Exact error is : "The system failed to flush data to the transaction log. Corruption may occur" Event ID: 57Category: DiskType: Warningthis is at 9:27 am today. Nothing running, no backups or anything. I checked my backupserver to see of I had CPS on (if any snapshot took place at that time...nothing there) Server is set up as follows (stand alone..this is all pre admin work i"m working with) circular logging enabled ( I ruled that out because back when I had the other 57 error I had it enabled so that is a wash imo, but not sure) I run full backups also no incrementals is why I have circular enabled to keep logs from growing insane out of the blue. C: OS and Exchange and logs D: Data StoresF: swap files

Andy I also ran ExBpa healthscan. Issue I'm showing is 'heapDeCommitFreeBlock Threshold' not set. Server exchsrv.meidev.local has 1 GB or more of memory, accommodates 53 mailboxes, and the 'HeapDeCommitFreeBlockThreshold' parameter has not been set to 262144. Virtual memory may become quickly fragmented and system instability may occur.I can go in and set this up after hours since it's a registry tweak...not sure how harmless the tweak in production now.

Hi,Please try to use chkdsk to see if we have issue on the hardisk.Please apply the latest update for the Windows Server 2003 system.More related information to share with you:Event 57 explainationhttp://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.2&EvtID=57&EvtSrc=ftdisk&LCID=1033Event ID 50, 26, or 57 is logged when you use HP SecurePath on a computer that is running Windows Server 2003 Service Pack 1 (SP1) or an x64 edition of Windowshttp://support.microsoft.com/kb/912593/en-usRegards,Xiu