Microsoft KB Archive/198633

= You receive an "File sharing lock count exceeded" error message when you synchronize two replicas in Access 2000 =

Article ID: 198633

Article Last Modified on 7/29/2004

-

APPLIES TO


 * Microsoft Access 2000 Standard Edition

-



This article was previously published under Q198633





For a Microsoft Access 97 version of this article, see 173006.

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

Advanced: Requires expert coding, interoperability, and multiuser skills.



SYMPTOMS
When you synchronize two replicas, you may receive the following error message:

Synchronization between '' and '' failed.

File sharing lock count exceeded (Error 3052).

The error may also occur when you run a Visual Basic for Applications procedure that uses the Synchronize method.



CAUSE
A member of the replica set contains too many changes for synchronization to be completed successfully. For example, if one of the replicas has increased in size by 100 megabytes (MB) because you have added a large number of new records, you may receive this error. The replica that contains too many changes may be the database from which you are trying to synchronize, or it may be another member of the replica set.



RESOLUTION
In Microsoft Access 2000, you can take advantage of a feature that allows you to increase the MaxLocksPerFile setting for Microsoft Jet database engine 4.0 by editing the Windows Registry. The default value of this setting is 9500. However, changing this value is not recommended if one of the replicas is located on a Novell Netware server, because the server's maximum record locks per connection is 10000. If both replicas are located on servers running Microsoft Windows NT 4.0 or Microsoft Windows 95 or later, the maximum value of this setting is limited only by available resources.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.


 * 1) Quit Microsoft Access.
 * 2) Click Start and then click Run.
 * 3) In the Open box, type regedit.
 * 4) Locate the HKEY_LOCAL_MACHINE registry folder.
 * 5) Expand HKEY_LOCAL_MACHINE until you locate the SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 4.0 folder.
 * 6) Click on the Jet 4.0 folder to view its contents.
 * 7) Select the MaxLocksPerFile entry; on the Edit menu, click Modify.
 * 8) In the Edit DWORD Value dialog box, select Decimal and increase the number in the Value Data box.
 * 9) Click OK to save the MaxLocksPerFile setting.
 * 10) Quit the Registry Editor.
 * 11) Start Microsoft Access and synchronize the replicas.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
The MaxLocksPerFile setting allows the Microsoft Jet database engine to complete large transactions without exceeding a specified record lock limit. Instead of exceeding this limit, the Jet database engine splits a transaction into two or more parts; after one part has been committed, the Jet database engine frees the locks so that they can be reused. As a result, fewer locks are required to complete the transaction. This prevents a Novell Netware server, which limits the maximum record locks per connection to 10000, from crashing when that value is exceeded.

However, the Jet database engine does not split the transaction when it synchronizes two replicas. If the transaction cannot be completed within the limit specified in the MaxLocksPerFile setting unless it is split into parts, you receive the error described in the "Symptoms" section, and the synchronization does not occur.

Steps to Reproduce Problem
WARNING: The following steps may require up to 400 MB of free disk space. The sample procedure fills a table with a large amount of data; running it may take a long time, during which your CPU is unavailable.  Start Microsoft Access and open a new blank database. Create the following table:

 Save the table as tblTable1. When asked if you want to create a primary key, click No.</li> On the Tools menu, point to Replication, and click Create Replica. When prompted to close the database, click Yes. When prompted to make a backup, click No.</li> In the Location of New Replica dialog box, note the location and file name of the new replica. Click OK.</li> Click OK when prompted that the Design Master was successfully created.</li> Open a new, blank module.</li> On the Tools menu, click References.</li> Scroll down through the Available References and click to select the check box for the Microsoft DAO 3.6 Object Library. Then click OK.</li>  Type the following procedure: Function Filler(lngNumRecs As Long) Dim lngLoopCount As Long Dim strFillerString As String Dim db As Database Dim rs As Recordset

strFillerString = ""

For lngLoopCount = 1 To 40 strFillerString = strFillerString & "x" Next lngLoopCount

Set db = CurrentDb Set rs = db.OpenRecordset("tblTable1")

For lngLoopCount = 1 To lngNumRecs rs.AddNew rs![ID] = lngLoopCount rs![Field1] = strFillerString rs![Field2] = strFillerString rs![Field3] = strFillerString rs![Field4] = strFillerString rs.Update Next lngLoopCount

db.Close MsgBox "Process Completed." End Function </li>  Save the module as Module1. Type the following line in the Immediate window, and then press ENTER: ?Filler(500000) NOTE: This procedure may take a long time to run and may require as much as 400 MB of free disk space. After the process has completed, continue on to the next step. </li> On the Tools menu, point to Replication, and then click Synchronize Now.</li> In the Synchronize Database ' ' dialog box, click OK.</li> Click Yes to close the database and begin synchronization.</li></ol>

A progress indicator with the message "Synchronizing Replicas" appears, but eventually you receive the error described in the "Symptoms" section.

<div class="references_section">