XP

N

Nick Swart

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 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, 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.

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

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



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanma
nServer\Parameters]

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


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanma
nWorkstation\Parameters]

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


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRXSm
B\Parameters]

"OplocksDisabled" = dword:00000000
 
M

Mike Lieser [MSFT]

Hello Nick,

You may want to call in and obtain the Hotfix listed in:

810907 Error Messages When You Open or Copy Network Files on Windows XP SP1
http://support.microsoft.com/?id=810907

Try this on a client machine and see if it resolves the problem.

Regards,

Mike Lieser, MCSA, MCSE, CNA
Microsoft SBS Product Support

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.


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 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, 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.

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

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



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanma
nServer\Parameters]

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


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanma
nWorkstation\Parameters]

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


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRXSm
B\Parameters]

"OplocksDisabled" = dword:00000000
 
N

news.is.co.za

I updated winxp with SP1. Obtained the patch, installed it. But nothing
changed!! We are still getting the problem. I did change the registries as
stated below. What can I do as it is getting very critical now. We are
loosing clients and are loosing lots of money because of this problem.

Can somebody PLEASE help us!!!!

I also would like to know if this will happen in Win2000 Prof?

Mike Lieser said:
Hello Nick,

You may want to call in and obtain the Hotfix listed in:

810907 Error Messages When You Open or Copy Network Files on Windows XP SP1
http://support.microsoft.com/?id=810907

Try this on a client machine and see if it resolves the problem.

Regards,

Mike Lieser, MCSA, MCSE, CNA
Microsoft SBS Product Support

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.


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 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, 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.

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

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



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanma
nServer\Parameters]

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


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanma
nWorkstation\Parameters]

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


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRXSm
B\Parameters]

"OplocksDisabled" = dword:00000000
Click to expand...
 
N

Nick

We have just been able to test it with Win2000 Prof and the excact problem
happens. Even if we put the data on a 98 machine and have two 2000Prof
machines accessing, it atill keeps the file locked after the file has been
closed.

And like I explained. It only happens when two or more machines are
accessing. With one machine everything runs perfect. And also only if we
open the file excusively, which is ABSOLUTELY nessicary to do in this case,
and under 98/95 we have NEVER has this problem. Only happening in 2000 and
XP.

We are loosing money and clients. And we just do not know what else to do
anymore.

news.is.co.za said:
I updated winxp with SP1. Obtained the patch, installed it. But nothing
changed!! We are still getting the problem. I did change the registries as
stated below. What can I do as it is getting very critical now. We are
loosing clients and are loosing lots of money because of this problem.

Can somebody PLEASE help us!!!!

I also would like to know if this will happen in Win2000 Prof?

Mike Lieser said:
Hello Nick,

You may want to call in and obtain the Hotfix listed in:

810907 Error Messages When You Open or Copy Network Files on Windows XP SP1
http://support.microsoft.com/?id=810907

Try this on a client machine and see if it resolves the problem.

Regards,

Mike Lieser, MCSA, MCSE, CNA
Microsoft SBS Product Support

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.


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 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, 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.

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

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



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanma
nServer\Parameters]

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


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanma
nWorkstation\Parameters]

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


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRXSm
B\Parameters]

"OplocksDisabled" = dword:00000000
Click to expand...
Click to expand...
 
N

Nick

I would like to apologize for posting so many messages for one question.

I have searched and read a couple of articles on OPLOCKS, and have found one
that caught my attention. #306981. As this article explains it, it sound
very familiar to our problem. Any comments?

Nick said:
We have just been able to test it with Win2000 Prof and the excact problem
happens. Even if we put the data on a 98 machine and have two 2000Prof
machines accessing, it atill keeps the file locked after the file has been
closed.

And like I explained. It only happens when two or more machines are
accessing. With one machine everything runs perfect. And also only if we
open the file excusively, which is ABSOLUTELY nessicary to do in this case,
and under 98/95 we have NEVER has this problem. Only happening in 2000 and
XP.

We are loosing money and clients. And we just do not know what else to do
anymore.

news.is.co.za said:
I updated winxp with SP1. Obtained the patch, installed it. But nothing
changed!! We are still getting the problem. I did change the registries as
stated below. What can I do as it is getting very critical now. We are
loosing clients and are loosing lots of money because of this problem.

Can somebody PLEASE help us!!!!

I also would like to know if this will happen in Win2000 Prof?

Mike Lieser said:
Hello Nick,

You may want to call in and obtain the Hotfix listed in:

810907 Error Messages When You Open or Copy Network Files on Windows
Click to expand...
XP
SP1
http://support.microsoft.com/?id=810907

Try this on a client machine and see if it resolves the problem.

Regards,

Mike Lieser, MCSA, MCSE, CNA
Microsoft SBS Product Support

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.


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 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, 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.

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

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



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanma
nServer\Parameters]

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


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanma
nWorkstation\Parameters]

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


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRXSm
B\Parameters]

"OplocksDisabled" = dword:00000000
Click to expand...
Click to expand...
Click to expand...
 

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

Similar Threads

XP Problem 1
Virus 'W32.Spybot.Worm' identified in file 'wlmsngr.exe' 3
OpLocks Problem 1
Distribution of Registry key script 3
Firewall start/stop with registry-keys 2
What's this IP address in my registry? 4
Firewall start/stop with registry-keys 3
Reg export file question 2

Top