TROUBLESHOOTING
Replicas are different sizes
If changes made to one replica have not yet replicated, the content of replicas may be different until replication occurs.
The source server has insufficient access
The source server access in a destination replica ACL determines what the destination replica can receive from the source server. Give the source server higher access in the destination replica ACL if necessary. The following message in the server log file (LOG.NSF) indicates insufficient server access:
There is no destination server in an access list
Access lists allow only a subset of people and servers in the ACL to access documents. If such access lists exist, add the destination server to them in the source server replica. If the access list uses a role to define access, add the destination server to the role on the source server replica.
An intermediate server has insufficient access
If replication between a source and destination server occurs through an intermediate server, make sure the source and destination server replica ACLs give the intermediate server high enough access to replicate all changes.
Replication settings are filtering documents
Some replication settings act as filters that screen out documents and features. Check the replication settings.
The server is out of disk space
Check to see if the database is a Domino 4 database and has exceeded the maximum database size. Ask your Domino administrator to resolve disk space problems and if necessary, consider moving a replica to another server or deleting databases on the server.
Older documents weren't replicated to a new replica
When the replica was created, the date specified for the replication setting option "This replica includes deletion stubs for all documents deleted since date" is later than it should have been. This option is on the Other panel of the File - Replication - Options for this Application dialog box in the Notes client. Create a new replica with an earlier date specified.
Related topics