Main menu:
The following is a list of the technical bulletins for our products. Most of these bulletins deal with issues that can affect data integrity or other Fritz issues and the issues are outside our control.
Norton Antivirus Software can cause errors with our data tables
Older versions of Norton Antivirus software from Synmantec can cause problems with Fritz data tables, specifically with respect to temporary tables created by DBISAM in a temporary files folder on a local drive. Norton deems any file created with the extension of .dat (the default DBISAM file extension for tables) in the temporary files folder as needing to be scanned and quarantined, and this can cause two errors to occur:
Table or backup file '<Name>' does not exist or
Access denied to table or backup file '<Name>'
If you are experiencing this problem, please contact our tech support team.
Configuring opportunistic locking in Windows
This article was previously published under Microsoft Q296264, and applies to versions of Windows WinXP and prior.
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 computers that are running Windows Vista and Windows Server 2008.
• 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 (http://support.microsoft.com/kb/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:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\
OplocksDisabled REG_DWORD 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:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
EnableOplocks REG_DWORD 0 or 1
Default: 1 (enabled)
Note The EnableOplocks entry configures Windows-
In addition, you can use the following values to tune opportunistic locking for Windows-
The following value specifies the minimum link throughput that the server allows before it disables raw and opportunistic locks for this connection:
MinLinkThroughput REG_DWORD 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 REG_DWORD 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 REG_DWORD 10 to 180 seconds
Default: 35
Note You must restart the computer for these registry changes to take effect.
Applies to...
Microsoft Windows Server 2003, Standard Edition (32-
Microsoft Windows Server 2003, Enterprise Edition (32-
Microsoft Windows Server 2003, Datacenter Edition (32-
Microsoft Windows Server 2003, Web Edition
Microsoft Windows Server 2003, 64-
Microsoft Windows Server 2003, Enterprise x64 Edition
Microsoft Windows XP Professional
Microsoft Windows XP Tablet PC Edition
Microsoft Windows XP Professional x64 Edition
Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Professional Edition
Microsoft Windows 2000 Datacenter Server
Microsoft Windows Small Business Server 2003 Premium Edition
Microsoft Windows Small Business Server 2003 Standard Edition
Windows Server 2008 Datacenter without Hyper-
Windows Server 2008 Enterprise without Hyper-
Windows Server 2008 for Itanium-
Windows Server 2008 Standard without Hyper-
Windows Server 2008 Datacenter
Windows Server 2008 Enterprise
Windows Server 2008 Standard
Windows Web Server 2008