OpLocks Problem

N

Nick

Hi

We have a 16 bit DOS based application. It accesses data through the
network. The database is dBase III. For years it worked perfectly under any
Windows OS. However with WinXP, and Win2000 Prof, we are encountering file
locking problems. Some of our earlier problems we were able to fix, but the
file locking one we have been unable to resolve..

The following happens when we open the files in Shared mode:
The first user is OK
As soon as another user opens a file exclusively, with another user on the
system, and busy accessing any file in the database, the file they are
trying to access is found locked and remains locked after the operation in
completed.
Interrogating the network with Computer Manager on the Win2000 server (can
be another server as well), you can see the file is in use by the user that
locked it exclusively, although the user is not using the file, and has in
fact closed the file.
To make the file available again to everyone after it becomes locked, the
needs to close the applications, then everyone else can continue working.
This is an intermittent file locking and there is no pattern to the problem.

I have been to http://support.microsoft.com/ and from the articles that I've
read, referenced below, my understanding is that it is an Opportunistic
Locking issue. I have changed registry settings, as shown below, but the
only difference it makes, is access is either faster, or slower, but the
problem persists.

I have updated WinXP to SP1a and Win2000 Prof up to Sp4.

Is there something I'm missing or is it a problem with WinXP or Win2000?

Article I'm referencing to is 812937
http://support.microsoft.com/default.aspx?scid=kb;en-us;812937

And have found a very interesting one, 306981.



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameter
s]

"autodisconnect" = dword:ffffffff
"CachedOpenLimit" = dword:00000000
"EnableOpLockForceClose" = dword:00000001
"EnableOpLocks" = dword:00000000
"SharingViolationDelay" = dword:00000000
"SharingViolationRetries" = dword:00000000


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Para
meters]

"UseOpportunisticLocking" = dword:00000000
"UtilizeNtCaching" = dword:00000000
"UseUnlockBehind" = dword:00000001
"UseLockReadUnlock" = dword:00000000


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRXSmB\Parameters]

"OplocksDisabled" = dword:00000000
 
J

Joe Wu [MSFT]

Hello,

Thank you for your post.

I have analyzed this issue and think it should not be an Opportunistic
Locking issue because you have already disabled the OpLocks in registry.

Generally speaking, this kind of problem is also related to the manner how
the application opens and uses the files. I would like to suggest that you
check whether this problem occurs with other file types, for example,
Notepad files or Office files. If other files work well via network, I
think that we can narrow down the possible reasons to the application and
dBase III.

I look forward to hearing from you. Thanks!

Regards,
Joe Wu
Product Support Services
Microsoft Corporation

Get Secure! - www.microsoft.com/security

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
|Reply-To: "Nick" <[email protected]>
|From: "Nick" <[email protected]>
|Subject: OpLocks Problem
|Date: Wed, 22 Oct 2003 09:57:20 +0200
|Lines: 65
|X-Priority: 3
|X-MSMail-Priority: Normal
|X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
|X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
|Message-ID: <[email protected]>
|Newsgroups: microsoft.public.win2000.general
|NNTP-Posting-Host: www.accfinsupport.co.za 196.36.224.11
|Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
|Xref: cpmsftngxa06.phx.gbl microsoft.public.win2000.general:88778
|X-Tomcat-NG: microsoft.public.win2000.general
|
|Hi
|
|We have a 16 bit DOS based application. It accesses data through the
|network. The database is dBase III. For years it worked perfectly under any
|Windows OS. However with WinXP, and Win2000 Prof, we are encountering file
|locking problems. Some of our earlier problems we were able to fix, but
the
|file locking one we have been unable to resolve..
|
|The following happens when we open the files in Shared mode:
|The first user is OK
|As soon as another user opens a file exclusively, with another user on the
|system, and busy accessing any file in the database, the file they are
|trying to access is found locked and remains locked after the operation in
|completed.
|Interrogating the network with Computer Manager on the Win2000 server (can
|be another server as well), you can see the file is in use by the user that
|locked it exclusively, although the user is not using the file, and has in
|fact closed the file.
|To make the file available again to everyone after it becomes locked, the
|needs to close the applications, then everyone else can continue working.
|This is an intermittent file locking and there is no pattern to the
problem.
|
|I have been to http://support.microsoft.com/ and from the articles that
I've
|read, referenced below, my understanding is that it is an Opportunistic
|Locking issue. I have changed registry settings, as shown below, but the
|only difference it makes, is access is either faster, or slower, but the
|problem persists.
|
|I have updated WinXP to SP1a and Win2000 Prof up to Sp4.
|
|Is there something I'm missing or is it a problem with WinXP or Win2000?
|
|Article I'm referencing to is 812937
|http://support.microsoft.com/default.aspx?scid=kb;en-us;812937
|
|And have found a very interesting one, 306981.
|
|
|
|[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Paramete
r
|s]
|
|"autodisconnect" = dword:ffffffff
|"CachedOpenLimit" = dword:00000000
|"EnableOpLockForceClose" = dword:00000001
|"EnableOpLocks" = dword:00000000
|"SharingViolationDelay" = dword:00000000
|"SharingViolationRetries" = dword:00000000
|
|
|[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Par
a
|meters]
|
|"UseOpportunisticLocking" = dword:00000000
|"UtilizeNtCaching" = dword:00000000
|"UseUnlockBehind" = dword:00000001
|"UseLockReadUnlock" = dword:00000000
|
|
|[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRXSmB\Parameters]
|
|"OplocksDisabled" = dword:00000000
|
|
|
|
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top