We have been plagued over the last year with the random issue of our Arev sessions freezing. All sessions stop, most will resume normally after a few moments, while some crash.

We have traced this problem to Novell Network 6's use of Microsoft op-locks on the Arevc.ini file.

Unfortunately the fixes give contradictory directions and they also say if done wrong then database corruption could be a result.

Any Netware 6/Arev/NLM 5.5 users who have had this op-locks problem and if so where you able to fix it. Or are we the last…

If locking is being performed on the ini file, that implies that the ini file is located on the network. Have you tried relocating it to the user hard drives?

We used individual .ini files, with the name set in the login script - then no locking on the file occurs that conflicts with other users.

Yes good idea that is what we will do if the op locks problem isn't easily solved.

Our concern is that there are other os files (for example arevpid.dat) that could have this same op-locks issue but cannot be moved to a local drive. So we would like to fix this.

Novell recommends the following settings when running DB apps on Netware 5+. This assumes you are using their Client32 on the Windows workstations. The Novell documentation states DB corruption can occur without these settings:

From the netware console type:

SET LEVEL 2 OPLOCKS ENABLED=off

SET CLIENT FILE CACHING ENABLED=off

You'll have to restart the server for these settings to take effect unless they already are in effect. (Netware will tell you the status when you type in the commands). These can also be set in the STARTUP.NCF file. Once set they should stay at those settings until manually changed.

One of my clients had a similar problem on Netware 6.0 and the above settings solved it.

Thanks for all your help!

Our powers that be have instead mandated we all start using the Netware client 4.91 sp4 as they say this is the fix recommended to us by Novell.

So far so good…

View this thread on the forum...