You are trying to import into a termbase using your MultiTerm Desktop, but the import fails at the reorganization stage. Or you are trying to reorganize one of your existing termbases but it fails. In the log file, you find the following error message:

File sharing lock count exceeded. Increase MaxLocksPerFile registry entry.

Re-run import using custom import definition

The easiest way to work around this problem is to simply re-run the same import file, but with an import definition that is set to not include an entry if it already exists in a termbase.
 

Increase the MaxLocksPerFile registry value

However, a more structural approach is to manually modify the value of this key. Make sure you first create a backup of your Windows Registry before making any changes. Be very careful when modifying the Windows Registry as changes cannot be undone and may harm your software.

1. Go to Start > Run and type regedit. Click OK.
2. Navigate to the following key:
   • For x86 operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 4.0
   • For x64 operating systems :HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Jet\4.0\Engines\Jet 4.0
3. In the right pane, right-click on the key MaxLocksPerFile and select Modify from the short menu.
4. Select Decimal as Base; the default value is set to 9500.
5. Increase this value to a value that is higher than the double of the default value, for example 20000.
6. Click OK and close the Windows Registry Editor.

This usually only happens if the termbase you are working with is very big. The error message is referring to a value set in the Windows Registry key MaxLocksPerFile and it is too low to support the reorganisation of your large termbase. This key prevents transactions in the Microsoft Jet database engine from exceeding a specified value. If a transaction attempts to create locks in excess of the value set in MaxLocksPerFile, the transaction is split into two or more parts and is partially committed.