Article ID: 929020
Article Last Modified on 10/11/2007
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
SYMPTOMS
On a Microsoft Windows Server 2003-based computer, you can back up and restore a sparse file by using a backup program. However, if an antivirus program is running, a large sparse file may be damaged after you restore it.
CAUSE
A backup program closes the sparse file during the restore operation. Then, an antivirus program opens the sparse file as a section file to check whether it includes virus patterns. When the antivirus program calls the ZwCreateSection function, a timing issue occurs between the following operations:
- The delayed write operation that is requested by the file close action
- The flush cache operation that is requested by the antivirus program
In this scenario, the NTFS file system driver incorrectly sets the valid data length of the sparse file to a value that is smaller than the actual size of the file. Therefore, any attempt to read the data that is beyond the incorrect valid data length returns all zeros.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2003 with SP2, x86-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Ntkrnlmp.exe | 5.2.3790.4077 | 2,492,416 | 09-May-2007 | 12:32 | Not Applicable | SP2 | SP2QFE |
| Ntkrnlpa.exe | 5.2.3790.4077 | 2,304,000 | 09-May-2007 | 11:42 | x86 | SP2 | SP2QFE |
| Ntkrpamp.exe | 5.2.3790.4077 | 2,343,936 | 09-May-2007 | 11:41 | Not Applicable | SP2 | SP2QFE |
| Ntoskrnl.exe | 5.2.3790.4077 | 2,452,480 | 09-May-2007 | 12:32 | x86 | SP2 | SP2QFE |
Windows Server 2003 with SP2, x64-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Hal.dll | 5.2.3790.4077 | 280,064 | 09-May-2007 | 13:11 | x64 | SP2 | SP2QFE |
| Ntkrnlmp.exe | 5.2.3790.4077 | 4,591,616 | 09-May-2007 | 13:11 | x64 | SP2 | SP2QFE |
| Ntoskrnl.exe | 5.2.3790.4077 | 4,521,984 | 09-May-2007 | 13:11 | x64 | SP2 | SP2QFE |
Windows Server 2003 with SP2, Itanium-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Ntdll.dll | 5.2.3790.4077 | 1,636,864 | 09-May-2007 | 13:10 | IA-64 | SP2 | SP2QFE |
| Ntkrnlmp.exe | 5.2.3790.4077 | 6,559,744 | 09-May-2007 | 13:10 | IA-64 | SP2 | SP2QFE |
Windows Server 2003 with SP1, x86-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Ntkrnlmp.exe | 5.2.3790.2933 | 2,463,232 | 09-May-2007 | 11:53 | Not Applicable | SP1 | SP1QFE |
| Ntkrnlpa.exe | 5.2.3790.2933 | 2,275,328 | 09-May-2007 | 11:14 | x86 | SP1 | SP1QFE |
| Ntkrpamp.exe | 5.2.3790.2933 | 2,315,776 | 09-May-2007 | 05:04 | Not Applicable | SP1 | SP1QFE |
| Ntoskrnl.exe | 5.2.3790.2933 | 2,423,296 | 09-May-2007 | 11:52 | x86 | SP1 | SP1QFE |
Windows Server 2003, x64-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Hal.dll | 5.2.3790.2933 | 280,064 | 09-May-2007 | 12:59 | x64 | SP1 | SP1QFE |
| Ntkrnlmp.exe | 5.2.3790.2933 | 4,635,136 | 09-May-2007 | 12:59 | x64 | SP1 | SP1QFE |
| Ntoskrnl.exe | 5.2.3790.2933 | 4,490,240 | 09-May-2007 | 12:59 | x64 | SP1 | SP1QFE |
Windows Server 2003 with SP1, Itanium-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Ntdll.dll | 5.2.3790.2933 | 1,636,864 | 09-May-2007 | 12:59 | IA-64 | SP1 | SP1QFE |
| Ntkrnlmp.exe | 5.2.3790.2933 | 6,524,416 | 09-May-2007 | 12:59 | IA-64 | SP1 | SP1QFE |
WORKAROUND
To work around this problem, configure the antivirus program to exclude the sparse files when the program scans for viruses.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about the terms that are used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional query words: data lost ValidDataLength
Keywords: kbbug kbfix kbqfe kbpubtypekc kbexpertiseinter kbhotfixserver kbwinserv2003postsp2fix KB929020
