How to stop the granting of opportunistic locks (Oplocks) in Windows

How to stop the granting of opportunistic locks (Oplocks) in Windows

Related Link:

Note: Sage cannot guarantee nor be responsible for the content of third party Internet sites. Contact that site's webmaster with questions or problems.

Microsoft knowledge base article on opportunistic locking
http://support.microsoft.com/kb/296264

How to enable and disable SMBv1, SMBv2, and SMBv3 in Windows Server 2008 R2, Windows 8, and Windows Server 2012
http://support.microsoft.com/kb/2696547

 

 

CAUTION: This solution needs advanced Operating System knowledge. Consult your system administrator for help. Sage isn't liable for issues caused by improper changes to the Windows Registry. Always back up your data before applying advanced solutions.

 

• Server Registry Entry to disable SMB2 this registry entry is required on 2008 server
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
  • SMB2 = 0

 

• Server registry entry to disable Oplocks
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

1. EnableOplocks REG_DWORD 0 or 1
2. Default: 1 (Enabled by Default)
3. Set to "0"

• Workstation registry entry to disable oplocks
  • HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters

1. OplocksDisabled REG_DWORD 0 or 1
2. Default: 0 (not disabled)
3. Set to "1"

Server Messaging Blocks (SMB 2.x)

 Microsoft updated its server message block protocol to SMB 2. Microsoft no longer allows OpLocks to be disabled if using this protocol. If SMB 2 is disabled the system will revert back to SMB 1 and opportunistic locking can be disabled with the appropriate registry entries. See below "How to enable and disable SMBv1, SMBv2, and SMBv3 in  Windows Server 2008 R2, Windows 8, and Windows Server 2012"

*Sage 100 ERP Advanced

Because Sage 100 Advanced is a client-server architecture network file, locking does not occur during the operation of tasks. However, Crystal reports are processed on the workstations in Sage 100 Advanced. Thus, in rare circumstances in a high volume, multi-user printing environment, it is possible that opportunistic locking errors could occur.

If a high-volume printing environment is experiencing issues where programs stop responding, and opportunistic locking is suspected, the issue could be resolved with the registry entries outlined above. However, the issue could also be resolved by using a server-side printing solution such as the C/S ODBC driver (Sage 100 Advanced only) or Crystal Enterprise. Both options are included with Sage 100.

DocLink: How to install and configure the Client/Server (C/S) ODBC Print driver for Sage 100 Advanced version 2013 and higher