Knowledge::

Running DataEase on Windows Server 2008 R2 - Opportunistic Locking

Parameters

Returns/Result

Examples

Reference

Running DataEase on Windows Server 2008 R2

Affects DataEase for Windows 6.53, 6.53, LegEasy 6, 7.0,7.1,7.2 and 7.5

There is two issues that causes problems for DataEase or any other file intensive database on 2008 Server. One is the old and trusted Opportunistic Locking that is default and interferes with DataEase locking. This need to be switched off like it had to be done on 2003.

The second ins SMB 2.0 File Cashing.

Windows Server 2008 introduced SMB 2.0. This has to be disabled (or shunted back to SMB 1.0) before Opportunistic Locking can be disabled server side

This is found under the usual registry key

HKLM'System'CurrentControlSet'Services'LanmanServe r'Parameters

1. Value name: Smb2
2. Value type: REGDWORD
3. 0 = disabled
4. 1 = enabled

Then set the opposite under the Smb1 local tree sub.

Configuring opportunistic locking in Windows

SUMMARY

By default, opportunistic locking is enabled for server message block (SMB) clients that run one of the Windows operating systems that is listed in the "Applies to" section. Opportunistic locking lets clients lock files and locally cache information without the risk of another user changing the file. This increases performance for many file operations but may decrease performance in other operations because the server that grants the opportunistic lock must manage the breaking of that lock when another user requests access to the file.

Notes for Windows Vista

The opportunistic locking registry keys are valid only for traditional SMB (SMB1). You cannot turn off opportunistic locking for SMB2. SMB2 was introduced in Windows Vista to enable faster communication between computer that are running Windows Vista and Windows Server 2008 or Windows Server 2008 R2.
If you disable opportunistic locking, the offline files feature in Windows Vista fails.

MORE INFORMATION

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows

The location of the client registry entry for opportunistic locking has changed from the location in Microsoft Windows NT. In later versions of Windows, you can disable opportunistic locking by setting the following registry entry to 1:

HKEYLOCALMACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\

OplocksDisabled REGDWORD 0 or 1
Default: 0 (not disabled)

Note The OplocksDisabled entry configures Windows clients to request or not to request opportunistic locks on a remote file.

You can also deny the granting of opportunistic locks by setting the following registry entry to 0:

HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

EnableOplocks REGDWORD 0 or 1
Default: 1 (enabled)

Note The EnableOplocks entry configures Windows-based servers to allow or to deny opportunistic locks on local files. These servers include workstations that share files.

In addition, you can use the following values to tune opportunistic locking for Windows-based computers that have granted opportunistic locks.

The following value specifies the minimum link throughput that the server allows before it disables raw and opportunistic locks for this connection:

MinLinkThroughput REGDWORD 0 to infinite bytes per second
Default: 0

The following value specifies the maximum time that is allowed for a link delay. If delays exceed this number, the server disables raw I/O and opportunistic locking for this connection.

MaxLinkDelay REGDWORD 0 to 100,000 seconds
Default: 60

The following value specifies the time that the server waits for a client to respond to an oplock break request. Smaller values allow detection of crashed clients more quickly, but might potentially cause loss of cached data.

OplockBreakWait REGDWORD 10 to 180 seconds
Default: 35

Note You must restart the computer for these registry changes to take effect.