"File sharing lock count exceeded" Error

finPOWER, emPOWER and fdPOWER can use either a Microsoft Access or Microsoft SQL Server database. This article applies to Microsoft Access (Jet) databases.

If a database commit contains too many changes a Run-time error 3052 "File sharing lock count exceeded" may occur. This is an unlikely occurrence, but may occur if updating a batch of several thousand transactions for example.

This occurs because a Jet database setting, MaxLocksPerFile, is set too low. When a commit exceeds the limit set here it attempts to split the commit into two parts but fails.

You may increase the MaxLocksPerFile setting for Jet by editing the Windows Registry. The default value of this setting is 9500. If the database is located on a Microsoft Windows Server, the maximum value of this setting is limited only by available resources.

For more information on how to change this setting see Microsoft Support article Q815281.

However, changing this value is not recommended if the database file is located on a Novell Netware server because the server's maximum record locks per connection is 10000. See knowledgebase article TSB1009 for more information.