File Locking Issues

  • Thread starter Thread starter Andre Southgate
  • Start date Start date
A

Andre Southgate

Hi There!

I am running Windows 2000 Server SP4 on a Compaq Proliant
ML350 with 2GB of Memory and I have the following Issues:

Our Client runs both Solution 6 and MYOB Accountants Office
and from time to time they will get "too many files open" or
File Lock errors in MYOB.

We have one user who takes 20-40 minutes to log in and I
can't for the life of me work out why.

Also we seem to be using 500MB of memory total according to
Task Manager, yet only 1.3GB is available. I can't see
anything obvious.

Any assistance appreciated.
 
Oplocks are off. I understand from Solution 6 that if I
enable them, I will have problems with ledgers being
corrupted. Should this be enabled?
 
Sorry, but can't quite make out what you mean by "solution 6". However, the
oplocks should remain off for databases at both client and server.

It's also recommended that SP3 be installed on both W2K clients and server.

This document might also be of help, since it offers details on both oplocks
and read caching when used with databases. While this doc has been revised,
these guys observed the "OpLock" issue about a year before OpLocks were
recognized as a database issue by Microsoft (at least as far as the W2K
knowledge base is concerned).
http://www.dataaccess.com/whitepapers/opportunlockingreadcaching.html

Note that flaky hardware (NICs) and incorrect datasource Dll versions may
also contribute to the problems your seeing. I don't know what type of data
source connectors MYOB is based on, but disabling the OPLocks on databases
using ODBC and DAO applications solves the file lock issue.
 
Back
Top