FileLocking Error 1

[cbarrol]

Hello,
I am getting an unusual error that keeps popping up on my NW6.1 server today that reads like this:
"Station 65 (Task 5) timed out waiting for an op-lock on file L2.ICO held by station 70"
The station numbers change as well as the file names, but all of the file names are files in a manufacturing SW program we have been using for years & I never got these errors before.

How can I check and see which PC's NW is referencing as Station 65 & Station 70?

I ran around earlier today and installed MS updates on the clients for the Zotob virus - could they have something to do with the errors?

Thanks,
Craig Barroll

 

[marvhuffaker]

Craig, you can find what connections they are in MONITOR - CONNECTIONS..

I could have sworn that in the past we have talked about turning off oplocks.. That will prevent those altogether.

Try these settings on your server:

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

Marvin Huffaker, MCNE

http://www.redjuju.com