Troubleshooting

You are here: Administrators Reference > Site Administration > Replication > Best Practices & Troubleshooting > Troubleshooting

Troubleshooting

If you encounter any problems with replication, the following list may provide some troubleshooting tips.

If the administrator’s email is configured, an email notification is sent when an error occurs on a scheduled or real-time replication. An email goes out every 15 minutes if the error is not corrected. A log file of the replication steps run during the replication process is recorded in the file monitor.templog.txt in the /commonspot/sync/packets directory.
All errors encountered during a packet import are written to the replication.error.log in the /commonspot/logs directory.
It is possible to continue a replication from a failed step as described for reimporting a packet with previous errors.
A full replication automatically performs search collection indexing and stub rebuilding on replicated pages. For this reason, the scope need not include these additional actions. (These actions add processing time to replications, so include them only if needed.) In general, if a stub rebuild or entire re-index is required, do it manually on the Target server.
Ideally, a full replication is only necessary if two sites become out of sync and an incremental update does not replicate the modified content. Because of this, set Full replication to On Demand and only execute it when needed. If you notice content discrepancies that are only corrected by a Full replication, please notify PaperThin Support, as this should not occur under normal processing.
If a scheduled replication fails (as indicated by the status error in the replication record), try to replicate the record manually (by clicking the go icon for the record), to re-initiate replication. When a scheduled replication fails, CommonSpot does not attempt replication again at a scheduled time unless the error is cleared.
Monitor the PaperThin support Web site for patches and hot fixes.
For servers running MS SQL Server, performance benefits related to memory usage have been reported when setting the Limit Connections option in the datasource settings, and restricting connections to a value (for example, 20).
Sites replicating with a large volume of uploaded documents may experience delayed replication processing. You can address this problem by modifying a /commonspot/keys/servervars.cfm setting .

Related Links

You can download PDF versions of the Content Contributor's, Administrator's, and Elements Reference documents from the support section of paperthin.com (requires login).

The following guides are available locally on your CommonSpot Server:

You can also download these other guides from the support section of paperthin.com (with login):

For technical support:

http://www.paperthin.com/support/