ACC2000: Avoiding Memory Leaks and EventID Error 2009 That Occur with Indirect Synchronizations (320803)

The information in this article applies to:

Microsoft Access 2000

This article was previously published under Q320803

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

This article applies only to a Microsoft Access database (.mdb).

SYMPTOMS

When you use indirect synchronization to synchronize your replica set on either Microsoft Windows NT 4.0 or Microsoft Windows 2000 Server, the synchronizer leaks file search handles. As a result, Error 2009 is logged in the Event Log for the server. After this happens you must restart the Windows Server because you cannot run other applications until the synchonizer releases the handles.

RESOLUTION

To resolve this problem, make sure that you have the following files and versions or later:

   File Name        File version
   -----------------------------
   Msrpfs40.dll     4.0.4314.0
   Mstrai40.exe     4.0.3714.0
   Mstran40.exe     4.0.3714.0

For additional information about how to obtain and install these files, click the article number below to view the article in the Microsoft Knowledge Base:

320805 MOD2000: Updated Version of Microsoft Jet Replication Files Available in Download Center

STATUS

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

MORE INFORMATION

Steps to Reproduce the Behavior

Configure the Windows Server for indirect synchronization.
Create a zero-byte file in the Dropbox folder, and then save the file with any name that has an .msg extension.
Start the Synchronizer (Mstran40.exe.)

After about six hours the Windows Server System Event Log starts to fill with Event ID 2009 errors.

A File Directory Search is used about every 10 seconds and is not released until the Synchronizer is stopped. You can easily see this on the Performance Monitor.

Modification Type:	Major	Last Reviewed:	6/30/2004
Keywords:	kbbug kbfix KB320803