Article ID: 885871 - View products that this article applies to.
When you revise and then save a file that has a double-byte character set (DBCS) file name in Microsoft Windows Server 2003 or in Microsoft Windows 2000, you may receive an error message that states that the file is corrupted. However, you can still access this file.
When you run the chkdsk command on the disk that contains the corrupted file, you receive an error message that is similar to the following message:
Additionally, the following event is recorded in the System log in Event Viewer:
The type of the file system is NTFS. The volume is in use by another process. Chkdsk might report errors when no corruption is present. WARNING! F parameter not specified. Running CHKDSK in read-only mode. CHKDSK is verifying files (stage 1 of 3)... File verification completed. CHKDSK is verifying indexes (stage 2 of 3)... Correcting minor file name errors in file 31. Correcting minor file name errors in file 34. Deleting index entry <Filename>.DOC in index $I30 of file 29. Deleting index entry <Filename>.doc in index $I30 of file 29. Deleting index entry <Filename>.XLS in index $I30 of file 29. Deleting index entry <Filename>.xls in index $I30 of file 29. Index verification completed. Errors found. CHKDSK cannot continue in read-only mode.
Event Type: Error Event Source: NTFS Event Category: Disk Event ID: 55 Date: <date> Time: <time> User: N/A Computer: <computer name> Description: The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume2.
Windows Server 2003
Service pack informationTo resolve this issue, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/889100/ )How to obtain the latest service pack for Windows Server 2003
Windows 2000Microsoft is researching this problem and will post more information in this article when the information becomes available.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was corrected in Windows Server 2003 Service Pack 1 (SP1).
Article ID: 885871 - Last Review: November 1, 2006 - Revision: 2.2