Microsoft KB Archive/304026

= ACC2000: Troubleshooting Common Replication Errors =

Article ID: 304026

Article Last Modified on 11/17/2003

-

APPLIES TO


 * Microsoft Access 2000 Standard Edition

-



This article was previously published under Q304026



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

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



SUMMARY
This article discusses common errors that you may see when you use Replication in Microsoft Access. The first section gives general troubleshooting steps that you can try. The second section gives an error message and then steps that Microsoft uses to troubleshoot that particular issue. This article does not guarantee that the steps will resolve the issue, but they will help to rule out possible causes before you call technical support.



Generic Troubleshooting Questions and Suggestions
 Has what you were trying to do ever worked?  If yes, then what has changed? Has new software been installed? Have the permissions changed on the local computer or on the network?  If you are using indirect replication or Internet replication, is a direct synchronization possible?  If so, then try to do a direct synchronization first, and then try the Indirect or the Internet synchronization again.</li></ul> </li> Try creating a new replica from the hub replica, and then try the synchronization again.</li> Does the error only occur on a particular computer or when a particular replica is trying to synchronize?  If yes, try creating a new replica, and then put it on the computer that is giving the error. Then, try to synchronize directly with the new replica.</li></ul> </li> Replicate the Northwind database and test to see if the behavior can be reproduced. The default location for Northwind is as follows:

C:\Program Files\Microsoft Office\Office\Samples\Northwind.mdb

NOTE: The path to Northwind.mdb may be different on your computer.</li> Have you downloaded and applied the latest version of Microsoft Jet to all computers involved in the replica set? To download the latest version of Microsoft Jet, click the article number below to view the article in the Microsoft Knowledge Base:

239114 How To: Obtain the Latest Service Pack for the Microsoft Jet 4.0 Database Engine

</li> When you are using Internet Replication, verify the following: <ol style="list-style-type: lower-alpha;"> The Drop Box and Scripts directories are set to Allow Anonymous connections through IIS</li> The anonymous user account has full permissions to the following directories through NTFS security:  Drop Box folder</li> Scripts folder</li> Folder containing the managed replica</li></ul> </li> Verify the aliasing of the folders in Microsoft Internet Information Server (IIS) and make sure the permissions to those are as follows: <ul> <li>FTP and WWW Drop Box have Read and Write permissions.</li> <li>Scripts folder has Read and Execute permissions.</li></ul> </li> <li>Examine the following in Replication Manager <ul> <li>Make sure the option is selected indicating that Replication Manager is on a Web Server.</li> <li>Verify that the Drop Box and Scripts folders are the same as that represented in IIS.</li></ul> </li> <li>Examine the following in the replica <ul> <li>Look to see if replicas contain the correct entry under the Synchronize Now dialog box in Access. This must reflect the entry that is in Replication Manager. For example, if it is configured with www.mydomain.com, then the list in a replica must display http://www.mydomain.com.</li></ul> </li></ol>

NOTE: Please see the &quot;References&quot; section later in this article for more information about Internet replication

</li> <li>When you are using indirect replication, verify the following <ol style="list-style-type: lower-alpha;"> <li>Both replicas involved in the synchronization have Replication Manager configured correctly and have the synchronizer running.</li> <li>The users have full permissions to the Drop Box folder of their synchronizer and full permissions to the synchronizer they are replicating with. To test this, have the users connect to the folder, and have them try to add a text file.</li> <li>Examine Replication Manager to verify that the Drop Box is the correct share that must be used for the replicas.</li></ol>

NOTE: Please see the &quot;References&quot; section later in this article for more information about Indirect Replication.

</li> <li>Troubleshooting a particular failing point: <ol style="list-style-type: lower-alpha;"> <li>Verify that MSG,TMP, or REP files (or all) are being created in the appropriate Drop Box folder. These files are created during the synchronization process.</li> <li>Look to see if the MSG, TMP, or REP files (or all) disappear during the synchronization process. This can indicate permissions issues that point to either the hub server or the user computer.</li></ol> </li></ol>

Indirect and Internet Synchronization Errors and Troubleshooting Steps
If you receive the following error message, follow the steps that are given to try to resolve the error:

No Suitable Synchronizer.

This error can be viewed through Replication Manager by right-clicking the synchronizer, and then clicking Synchronization History.
 * 1) Examine permissions for users and make sure that they have Write permissions to the Drop Box folder on the hub server. In some situations, the anonymous user account must be added directly to the folder.
 * 2) Users who are behind a firewall or a Proxy Server are able to send data, but the packets that are being returned cannot get back through the firewall. This is not supported in Access 97 but is possible with Access 2000.
 * 3) Make sure that Replication Manager is started and running correctly. Stop Replication Manager, and then restart it to make sure that there are no errors.
 * 4) Configure Replication Manager correctly. Walk through the configuration of Replication Manager and confirm that it is pointing to the correct Drop Box on the hub server.

NOTE: Please see the &quot;References&quot; section later in this article for more information about Internet and Indirect Replication.

If you receive the following error message, follow the steps that are given to try to resolve the error:

Partner Member in the Replica set is not being managed.


 * 1) Examine the permissions for the Drop Box folder. Allow all users, including the anonymous user account, Write and Read permissions.
 * 2) Make sure that the replica is being managed by Replication Manager.
 * 3) Examine NTFS permissions for the anonymous user account in IIS. Make sure IIS is handling the password information.
 * 4) Create a new folder on the hub server and allow everyone full control to that folder. Then, place the Hub replica in that folder.

If you receive the following error message, follow the steps that are given to try to resolve the error

Internet Too Slow or Replication Manager is not Correctly Configured.


 * 1) Make sure that Anonymous connections are being used to the FTP site. You can do this through IIS.
 * 2) Try to ping the IP address or the domain name from the user's computer.
 * 3) Examine the configuration of Replication Manager and verify that the correct Drop Box on the hub is being referenced.
 * 4) Examine the CGI Timeout properties in IIS and try increasing them.
 * 5) Look to see if JPEG images are trying to be synchronized from within the database. Because these files can be large, they can cause a timeout error.
 * 6) Look to see if the synchronization is taking place to and from the same server. This causes a looping structure and will time out.
 * 7) Is there more than one instance of MSTrai**.exe running? If so, stop both instances, and then try the synchronization again.

If you receive the following error message, follow the steps that are given to try to resolve the error:

Internal Internet Failure.


 * 1) Examine the permissions on the IIS Server and make sure that they are configured properly for all virtual directories.
 * 2) Examine the location for the Drop Box folder for the FTP and WWW aliases and make sure they are pointed to the correct folder on the computer.
 * 3) Examine the IP Address or the Domain Address for the computer. Verify that this is the name or address being referenced in Replication Manager.

<div class="references_section">