Event ID 57, event ID 55, and event ID 50 may be logged when you use Windows Cluster on Windows Server 2003 (885688)



The information in this article applies to:

  • Microsoft Windows Server 2003, Standard Edition
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Web Edition

SYMPTOMS

When you start your Microsoft Windows Server 2003-based computer that is running Windows Clustering, the following events may be logged.
Event Type: Warning
Event Source: Ftdisk
Event ID: 57
Description:
The system failed to flush data to the transaction log. Corruption may occur.

Event Type: Error
Event Source: NTFS
Event ID: 55
Description:
The file system structure on disk is corrupt and unusable. Please run the chkdsk utility on the volume "Drive_letter:"

Event Type: Warning
Event Source: Ntfs
Event ID: 50
Description: {Delayed Write Failed} Windows was unable to save all the data for the file. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

CAUSE

This behavior occurs when the cluster node computer starts. This behavior is caused by a conflict between the NTFS file system and the cluster services driver component (Clusdisk) filter.

RESOLUTION

If you experience the behavior as it has been described, it does not indicate a problem with the cluster node hard disk and can be ignored.

Modification Type:MinorLast Reviewed:5/8/2006
Keywords:kbwinservperf kbTermServ kbtshoot kbprb KB885688 kbAudITPRO