HomeGuide Archives:: Worldox GX4System Administrator ResourcesDisable Opportunistic Locking and SMB2

41.2. Disable Opportunistic Locking and SMB2

Background

This is for server Operating Systems that do not support SMB3 (ie. Windows Server 2008 R2 or earlier), where SMB2 is enabled.

Opportunistic locking and SMB2 are known to cause some really nasty file locking and data loss issues with Worldox and many other applications.  As mentioned above, this usually applies to Windows Server 2008 R2 and earlier.  If you are using SMB3 on a newer server O/S, this is not an issue.

But if you are running with SMB2, for Worldox to operate properly, Opportunistic Locking and SMB2 must be disabled on all servers that Worldox will interact with  Both the file server hosting the DocVault, and the server that hosts the network copy of the Worldox application, if it is not the same.  Once SMB2 is disabled, the O/S will revert back to SMB1.  At this point, Opportunistic Locking can also be disabled (since it can't be disabled in SMB2).

Warning:  If your site uses Windows Offline files, Windows Vista or above workstations, and Windows Server 2008 R2 or above, the following procedure could prevent the Offline Files feature from working.  If this applies to your site, please notify support@trumpetinc.com before performing this procedure.

Update to Warning:  The last report of any issue of this kind was before 2014.

Procedure

  1. Apply the .reg file attached to this article to each server
  2. Reboot the server for the changes to be applied
  3. After rebooting the server, be sure to log the Indexer PC out and back in

Manual Procedure

Please read this: It's really easy to get things configured in the wrong place if you do this manually.  If at all possible, please just review the contents of the .reg file, confirm that you are OK with the changes, then apply the .reg file.

If you absolutely insist on creating these by hand, here they are:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\  |  OplocksDisabled REG_DWORD = 1

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters | EnableOplocks REG_DWORD = 0

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\  |  SMB2 RegDWORD = 0

 

If you have problems...

At one (literally just one) of Trumpet's sites, disabling SMB2 resulted in problems with accessing the Group Policy manager from the domain controller. Other symptoms included Event ID 1058 appearing in the event logs.  If this happens at your site, please refer to the following Microsoft Knowledgebase article for the resolution: You cannot open file shares or Group Policy snap-ins on a domain controller

 

Note:

If you decide to turn OpLocks or SMB2 back on - though we really, really recommend against doing so - you can do so by deleting the following values from the registry (be sure to delete the values, not the registry keys themselves):

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\  |  OplocksDisabled

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters | EnableOplocks

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\  |  SMB2

Also, your file server must be rebooted after making these changes.


This page was: Helpful | Not Helpful

© 2012 Trumpet, Inc., All Rights Reserved