turn off opportunistic locking?

  • Thread starter Thread starter djc
  • Start date Start date
D

djc

I have actually asked this before... a long time ago, and I gon't recall the
outcome. Now it has come up again. This time, I was told by an ACT! expert
that I MUST disable opportunistic locking or ACT! database corruptions will
occur. I currently only have one user using the act database at any one time
so it has not been an issue but a few new users will be coming soon so I
need to find out if I should do this. For some reason, somewhere in my vast,
sketchy, memory (hehe) a red flag raises telling me I have read or heard
somewhere that disabling opportunistic locking can have bad effects.. I have
been instructed to disable opportunistic locking on all clients and the file
server where the ACT! database resides. Can this cause problems with other
services on the same machine? For example, the same server where ACT!
resides is also an AD domain controller, DNS server, and an SQL Server 2000
server...

any info on this would be greatly appreciated. Thanks.
 
Server side, you add a Reg_Dword value named;
"EnableOplocks"
and set it's value to 0
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters


--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I have actually asked this before... a long time ago, and I gon't recall
the
| outcome. Now it has come up again. This time, I was told by an ACT! expert
| that I MUST disable opportunistic locking or ACT! database corruptions
will
| occur. I currently only have one user using the act database at any one
time
| so it has not been an issue but a few new users will be coming soon so I
| need to find out if I should do this. For some reason, somewhere in my
vast,
| sketchy, memory (hehe) a red flag raises telling me I have read or heard
| somewhere that disabling opportunistic locking can have bad effects.. I
have
| been instructed to disable opportunistic locking on all clients and the
file
| server where the ACT! database resides. Can this cause problems with other
| services on the same machine? For example, the same server where ACT!
| resides is also an AD domain controller, DNS server, and an SQL Server
2000
| server...
|
| any info on this would be greatly appreciated. Thanks.
|
|
 
thanks for the reply Dave. However my specific questions (towards the bottom
of the post) were asking about any bad effects this might have to other
system services... The server in question also is a domain controller, dns
server, and a sql 2000 server. The purpose of the post was not a 'how to'
but rather a 'should I?'. Probably my bad for not getting to the point
quicker... hehe..

I do appreciate the reply. Any other info on the 'should I?'

thanks.
 
Some of these may help.

http://search.microsoft.com/search/...a&na=84&qu=EnableOplocks&qp=&qa=&qn=&c=10&s=0

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| thanks for the reply Dave. However my specific questions (towards the
bottom
| of the post) were asking about any bad effects this might have to other
| system services... The server in question also is a domain controller, dns
| server, and a sql 2000 server. The purpose of the post was not a 'how to'
| but rather a 'should I?'. Probably my bad for not getting to the point
| quicker... hehe..
|
| I do appreciate the reply. Any other info on the 'should I?'
|
| thanks.
 
Back
Top