Article ID: 149468
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Server 3.51
This article was previously published under Q149468
SYMPTOMS
Clipper applications that are run on a Windows NT client using Client Services for NetWare (CSNW) may corrupt Clipper database index files maintained on a Novell or Novell-compatible server.
CAUSE
In some cases, a file with a read-associated cache can become old when a write overlaps the read cache.
The corruption is caused by old data being read in from the read cache; Clipper then uses that data to build the index file. For example, the following sequence on reads and writes results in index corruption:
- A Clipper application builds a database and index from data set 1.
- The Clipper application reads data set 2.
- The Clipper application reads the database file with data set 1 and caches it.
- The Clipper application writes to the database with data from data set 2.
- The Clipper application re-reads the database with data from set 1 using the stale read cache.
- The Clipper application builds the incorrect index file from the stale database read from the cache.
STATUS
Microsoft has confirmed this to be a problem in Window NT version 3.51. This problem was corrected in the latest U.S. Service Pack for Windows NT Workstation or Server version 3.51. For information on obtaining this update, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
MORE INFORMATION
The third-party products discussed in this article are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.
Additional query words: prodnt
Keywords: kbnetwork KB149468
