Cache Manager May Cause Data Corruption
Article ID: 193781
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 4.0 Enterprise Edition
This article was previously published under Q193781
SYMPTOMS
Data corruption can happen on a file located on a server when using test
applications that do the following:
- Test Application One:
Service running under a user account that has no access to the file
server directory where the file is located.
Try to obtain file attributes of a file located on the file server in an
infinite loop.
- Test Application Two:
Application that has rights to the file in the directory that Test
Application One is attempting to use.
Open/creates file, writes 20 bytes of data, closes file, wait 500 ms,
open file, read data, close file, compare Data, wait 500 ms, and start
the loop again.
This application will soon detect data corruption in application data files
during the compare operation of the loop.
CAUSE
A zero length condition in the cache manager was not accounted for and
caused the data to be flushed.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe KB193781