Cannot open DB on NW5.1 server via a batch file w/4.9 client

[jcassidy]

Server: NetWare 5.1 SP5
Client: 4.90
4.90 SP1
4.90 SP2

We have a database hosted on one of our servers that is accessed by a large
number of users in our company. Currently they open the database using a
batch file. Once we upgraded some users to the 4.9SP2 client they began
receiving the following error:

Opening Database...
The process cannot access the file because it is being used by another
process.

This problem does not appear to occur with the 4.8x client, but does occur
with 4.90, 4.90SP1, and 4.90SP2. I applied the post SP2 patches (including
the NWFS update recommended in TID2970687) but the problem still persists.
Browsing to the database and opening it through explorer works fine, but
opening the file from a command line or batch file does not. The database
in question is flagged as transactional, and this is happening on both
Windows XP and Windows 2k machines with Office 2k or 2003 (all patched to
varying levels of service packs).

Replacing nwfs.sys with the one that came with 4.81 eliminates the issue,
but obviously using such an old version of the file isn't a permanent fix.
Any ideas as to why this might be happening?

Also, if there is a better forum to post this to, please point it out. I looked for a client forum, but could find none.

 

[marvhuffaker]

I don't recall if you have both of these options with your server and service pack version, but it is where you want to start:

SET CLIENT FILE CACHING ENABLED=OFF
SET LEVEL 2 OPLOCKS ENABLED=OFF

Do this on the server console and see if it helps.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting, Inc.

http://www.redjuju.com/support

 

[jcassidy]

I so thought you were on to something, but I can find no oplock parameter of that nature. The only lock params are for file and record and per connection for both.

We turn off file caching at the server in our base builds.

Thank you for the suggestion.

 

[marvhuffaker]

What if you just type that at the console? If it gives you an error, it's not an available option. I don't know where the setting is at in the menu system, I never use that.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting, Inc.

http://www.redjuju.com/support

 

[jcassidy]

What I meant was, I found absolutely nothing in any of the menu items pertaining to oplocks. Just the file caching which is set to off. It doesn't exist. I did try the set parameter first and of course it "errored" out.

I did see a TID that mentioned something about L2 oplocks and was pertaining to NW5.1 SP6 and above. I however am at SP5.

I am currently building a test server to duplicate, then hopefully correct my issue with SP7. I'll post the results. I have a hunch that versions of the server's filesys.nlm and clients' nwfs.sys are now incompatible.

 

[jcassidy]

Well, it was a no go. SP7 didn't correct the issue.

I did find a Client 4.9 Update file that included a filesys.nlm and ncp.nlm to enable oplock 2 on 5.1 SP5. This didn't work with just the NLMs and didn't work with the NLMs plus client files.

I'm half tempted to just use the filesys.nlm from 4.81 in future client systems with 4.9 SP2.