General discussion

Locked

Opportunistic Locking

By enquiries ·
I have a client/server Visual FoxPro application running on Windows Server 2003 and XP Workstations. One workstation is experiencing intermittant crashes with a VFP error 1502 (File is in use elsewhere), when no other user is utilizing this part of the system. The vendor is suggesting that this is an environment issue.

I have found a number of references to registry settings for opportunistic locking and when checking with the vendor they have said that this should be set to "On".

However "regedit" shows no key for opportunistic locking at all.

The question is if there is no reference key for it do I need to create a key in order for Windows to behave correctly?

One would have expected all required keys to be created when the network clients were created.

Tom Macaulay

This conversation is currently closed to new comments.

2 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by sgt_shultz In reply to Opportunistic Locking

i think it is entirely likely you will have to create the key. but you are right to balk imho.
if all things equal and having no problems elsewhere with other network clients same sp same software installed etc etc etc then i would not start hacking my registry yet.
maybe something else would explain this. while thinking about it and since you now have your feet in front of the bad box use opportunity to double check first things first. start with foxpro application configuration. same on bad client as on good clients, yes? save versions, same settings. what can you find out about what the configuration is and should be. screen dump. make notes. same network protocols, yes? also check routine maintenance on xp box. what sp? what updates? plenty of free defragged hd space? up to date virus stuff? what nic is installed. how is the thing cabled. maybe network communications problem? maybe local (client) hd/controller problem? or some other local performance problem.
did this ever work? sounds like you are saying it is new problem and used to work. what may have changed lately. sp? driver updates? bios updates? windows updates? busy malware in the background? virus? what other things havent' been right with this machine lately.
i would try to learn to reproduce the problem. i would examine event logs. i would examine open files and sessions at the time of failure.
well if only one workstation exhibit problem you have to give that to them. you are not omitting interesting fact like all other no problem workstations on your network are win2k and only this one xp box giving grief, are you?
try to get vendor to describe to you an environment in which this problem will not be displayed. ask them if any other clients have mentioned this problem. perhaps they will say something like 'we have similar running on windows 2000 server sp whatever with win2000 pro sp whatever clients'. if they do not mention windows 2003 and xp clients, do not dispair. that is a clue.

Collapse -

by wellmax1.maxwell In reply to Opportunistic Locking

HKEY LOCAL MACHINE
SYSTEM
CURRENT CONTROLL SET
SERVICES

1.LAN MAN SERVER -PARAMETERS-ENABLE OPLOCK (0) NO

2.LAN MAN WORKSTATION-PARAMATERS-USE OPPURTUNISTIC LOCKING (0) NO

3.MRX SMB-PARAMETERS-OPLOCKS DISABLE (1)

IF THE OPLOCKS ARE NOT IN THE REGISTRY JUST RIGHT CLICK IN THE RIGHT HAND FIELD AND ADD THEM WITH THE FOLLOWING PARAMATERS ABOVE.

Back to Windows Forum
2 total posts (Page 1 of 1)  

Related Discussions

Related Forums