Multi-user Database File Corruption
Problem
Standard network installations are optimised for fast operation with single user applications such as Word or Excel. Problems arise with multi-user applications if local caching is not disabled.
Overview
This document provides a summary of the changes required to be applied to the various platforms to eliminate some possible causes of file corruption. It provides references to other supporting documentation that describe in detail the issues behind each suggested change. Here is our disclaimer.
The following sections contain a summarised list of issues to be addressed with various platforms and network configurations.
Windows 95, 95a, 95b or 95c Workstation on any Windows Network
- Apply Vredir Update to Version 4.00.1116 Reference 1
- Add DiscardCacheOnOpen setting to Registry Reference 2
- Add Load=Spool32 to WIN.INI Reference 3
Windows 98 First Edition Workstation on any Windows Network
- Add DiscardCacheOnOpen setting to Registry Reference 2
- Add Load=Spool32 to WIN.INI Reference 3
- If using Realtek Network Adaptor, apply Realtek Driver update Reference 4
Windows 98 Second Edition and Windows ME Workstation on any Windows Network
- Add DiscardCacheOnOpen setting to Registry Reference 2
- Add Load=Spool32 to WIN.INI Reference 3
Windows 95, 95a, 95b, 95c Workstation on Novell Network
- Add Load=Spool32 to WIN.INI Reference 3
- If using Client32, ensure version is 3.2 or later Reference 5
- If using Client32, set File Cache Level to Zero Reference 5
- Set Frame Type to a specific type and not Auto.
Windows 98 First Edition Workstation on Novell Network
- Add Load=Spool32 to WIN.INI Reference 3
- If using Realtek Network Adaptor, apply Realtek Driver update Reference 4
- If using Client32, ensure version is 2.2 or later Reference 5
- If using Client32, set File Cache Level to Zero Reference 5
- Set Frame Type to a specific type and not Auto.
Windows 98 Second Edition and Windows ME Workstation on Novell Network
- Add Load=Spool32 to WIN.INI Reference 3
- If using Client32, ensure version is 2.2 or later Reference 5
- If using Client32, set File Cache Level to Zero Reference 5
- Set Frame Type to a specific type and not Auto.
Windows NT4, 2000 or XP Workstation with Windows NT4, 2000 or XP Server
- Disable Opportunistic Locking on the Server or each Client Reference 6
References:
1. Apply Vredir Update to Version 4.00.1116
Microsoft Article: Q148367 Possible Network File Damage with Redirector Caching
Location: http://support.microsoft.com/support/kb/articles/Q148/3/67.asp
Faircom Article: FILE CORRUPTION ON WINDOWS 95 AND WINDOWS NT SYSTEMS
Location: http://www.faircom.com/product_tech/ctree/redirect.htmDownload vrdrupd.exe
2. Add DiscardCacheOnOpen setting to Registry
Microsoft Article: Q148367 Possible Network File Damage with Redirector Caching
Location: http://support.microsoft.com/support/kb/articles/Q148/3/67.asp
Faircom Article: FILE CORRUPTION ON WINDOWS 95 AND WINDOWS NT SYSTEMS
Location: http://www.faircom.com/product_tech/ctree/redirect.htmDownload CacheOff.reg
3. Add Load=Spool32 to WIN.INI
Acacia Consulting Services Technote: SPOOL32 Errors in Windows 95
4. If using Realtek Network Adaptor, apply Realtek Driver update
This applies to Windows 98 First Edition Only - Second Edition is ok.
Microsoft Article: Q189778 Possible Problems with Windows 98 Realtek Network Adapter Driver
Location: http://support.microsoft.com/support/kb/articles/Q189/7/78.aspDownload the updated driver http://www.realtek.com.tw/cn/driver/8029-driver.htm
5. If using Client32, ensure version is 3.2 or later
If using Client32, set File Cache Level to Zero.
Refer to Novell document 10013992 How to- Troubleshooting file corruption.
Refer to Database File Corruption on Novell Networks.Novell Knowledgebase www.novell.com
6. Disable Opportunistic Locking in NT, 2000 and XP
NT's Oppurtunistic Locking must be disabled. This is best done at the server by applying registry settings at the server. It can also be done at each client NT Workstation by applying the registry settings at the client. The client settings are really only necessary if access to the server is not possible.
Microsoft Article: Q129202 PC Ext: Explanation of Opportunistic Locking on Windows NT
Location: http://support.microsoft.com/support/kb/articles/q129/2/02.asp
Faircom Article: FILE CORRUPTION ON WINDOWS 95 AND WINDOWS NT SYSTEMS
Location: http://www.faircom.com/product_tech/ctree/redirect.htmDownload NT-Server-OpLocks.reg for the Server or NT-Client-OpLocks.reg for the Clients.
