KB31627: "File sharing lock count exceeded. Increase MaxLocksPerFile registry entry" error occurs when performing transaction-heavy operations on a Microsoft Access metadata database

SYMPTOM:
When performing operations involving a high number of transactions against a Microsoft Access metadata, the following error appears:
Sample Code/Error

File sharing lock count exceeded. Increase MaxLocksPerFile registry entry

Some operations that may cause this error to appear are the following:

• Creating a project
• Deleting a project
• Upgrading the metadata

When creating a new project or deleting an existing project, Strategy Desktop shows the following error:

Sample Code/Error

Database error <>: Call SQLExecDirect got SQL_ERROR
File sharing lock count exceeded. Increase MaxLocksPerFile registry entry.

When upgrading a metadata database to using the Strategy Configuration Wizard in 9.x, a similar error appears:

 
Sample Code/Error

Execute Query failed.
Error type: Odbc error. Odbc operation attempted: SQLExecDirect. File sharing lock count exceeded. Increase MaxLocksPerFile registry entry

CAUSE: 
The operations such as creating or deleting projects, or upgrading Strategy version of metadata database involve a high number of transactions against the Microsoft Access database. This error occurs if the number of file locks on the Microsoft Access database file exceeds the MaxLocksPerFile registry string.
ACTION:
Refer to the following Microsoft Knowledge Base technical note on directions for increasing the MaxLocksPerFile registry string:

"File sharing lock count exceeded…" error message during large transaction processing (http://support.microsoft.com/kb/815281)

In cases where a metadata database upgrade is being performed, or a project is being created, the suggested value for the MaxLocksPerFile registry string is 200000. For more information, refer to KB20459.
When deleting a project, another option is to start by deleting individual folders within the project first. This will lower the number of simultaneous file locks on the metadata.
Registry Modification:
WARNING:
Modifying registry values incorrectly may cause serious, system-wide problems that may require the re-installation of Microsoft Windows NT. Any edit of the registry is done at the user`s own risk. Since these are user-initiated changes, they are not covered by any Strategy warranty. If using Microsoft Windows NT, the user should backup the registry and/or update an Emergency Repair Disk (ERD) prior to alterations.
 

KB31627