Opportunistic locking corrupting database?

[Dennis]

We have a complex application with a multi-database backend, and allowing
multiple users on simultaneously. The application is in Access 2002 and
resides on a WinServ2003 server. Since upgrading to the WinServ2003, this
application has been consistenly becoming frozen/corrupted. The error message
generated is:

The database '\\path here\filename.mdb' needs to be repaired or isn't a
database file.

Some users will get this message, while other users continue to work without
incident. The only solution has been to boot everyone out of the database.
Then they can go back in and all is working properly (until the next time).
No actual repair has been required, but has been performed anyway, just to be
sure.

I was reading that Opportunistic locking might be a contributing factor, and
that it should be disabled on the server. This database application is used
simultaneously by dozens of users. The server also hosts other massive
database applications for other departments, so is VERY heavily used. My
questions are:

1) What are the ramifications/performance issues in disabling Opportunistic
locking on the server? (Does that mean that only one user at a time can be in
a database or table?)

2) Might this not even be relevant to the problem?

3) If not, what might be relevant to resolving this issue?

Any assistance on this would be greatly appreciated.

Thank you.

 

[Ian]

Dennis

Does your server run antivirus checks on your database files?

I recently had a problem with extreme file fragmentation caused by AV
software.
You may want to check the server with Defrag and stop your Av software from
checking your DB folders or extensions

 

[taffy1]

Hello Dennis,

I'm interested in any answers to your problem - because I'm going
through a living hell w/ the same circumstances.
More info - I was an NT 4.5 SBS shop w/ Win 98se & W2k clients. Complex
Access 2k app w/ 5-15 users, 700mb mde.

Went to Win Server 2003 and added / upgraded several clients to Win XP
Pro. (had a bunch of permission/security setting isses w/ that!!)

Ended up w/ 5 diff versions of MDAC and msJet40 across the 15 clients.

Did all as advised in MS kb239114 & MS kb303528.
Had db crashs and do table imports into a blank db, etc.
Ran smooth for 3 weeks, then all heck breaks loose again.
Rebuilt the db again.
Looked at the O2k SP3 (access 2000)and did that upgrade on all
clients.
For past 3 days, db getting "The database [database path/name.mde]
needs to be repaired or isn't a database file" ms access. I'm also now
looking at the Op Lock suggestions and have the same ?? as you.

Taffy1