Op-Lock? 1

[tteknos]

On my Netware 6 Console Screen, I am getting the following error:

3-13-2003 11:37:53 am: FILESYS-5.13-183 [nmID=F000A]
Station 141 (task 4) has timed out on its op-lock (type = 2).

This occurs only on Windows NT/2000 machines, and it occurs with any version of Client 4.8x. Now, I've read all the documentation on Novell's site about this, but it doesn't ever refer to this being an issue in NW6. In fact, it goes so far as to say it has been an issue that's corrected since NW5 SP3.

It appears that it's related to file caching, and the only other thing I've tried is to turn off File Caching under Advance Settings on Client Properties. I'm not sure if this has corrected the problem as of yet, since the problem only happens once every few days or so. Also, it ONLY happens on PC's in which the users are using a program that we wrote, which accesses a database on the server. Let me know if anyone has run across this problem in NW6, and if turning off the file caching corrected the problem. Thanks in advance.

-Ted

 

[sobak]

Ted,

I just setup a new NW6 box and ran into the same problem. Remembering the setting from the problem I had with NetWare 5 I turned file caching off at the file server level.

SET CLIENT FILE CACHING ENABLED = OFF

This will turn off file caching globally for all clients. I didn't see any problems with doing this but remember this was a test server and not a production server. I'm in the process of upgrading all my 4.11 boxes over to 6 so I'm sure I'll run into this again.


david e
*end users are just like computers, some you can work with...others just need a simple reBOOTing to fix their problems.*

 

[tteknos]

Yea I saw that command in a technical document. I hadn't tried it yet since it is a production server. I tried it by the client setting first, to see if it causes any problems, or fixes the current issue. That was going to be what I did IF this worked. Thanks for the input.

Ted