Error 96 indicates that a log could not be opened. If the Replication Agent had been using that log before it terminated, it should have recorded its next position offset.

Error 76 indicates that the Replication Agent did not record a valid offset in the log. The log position did not correspond to the start of a transaction log entry: it was in the middle of an entry.

An action taken to avoid the 96 error could cause error 76. Because the saved offset is specific to the log on the original source server, replacing the file could cause error 76. An example would be copying another file to replace the original log. Another possible cause is if you changed the agent to connect to a different source server than it was using before, if that server happens to have a log with the same name, you could get this error.

It is possible to receive Replication Agent error 809 under certain conditions. This situation can occur when applications that use c-tree's socket timeout feature generate a lot of transaction log data for files that are not replicated. This activity can force the server to scan the logs up to a checkpoint, which can exceed the connection timeout. That triggers a disconnect, causing the Replication Agent to reconnect and continue.

In this case, the timeout can be avoided by increasing the socket_timeout parameter (e.g., setting to 30 seconds or more). A setting of 300 seconds (5 minutes) should be a reasonable timeout value.

The Replication Agent maintains its own transaction logs and housekeeping files. Removal of these can cause problems. Be sure the FairCom Replication is run in it's own unique directory independent of any existing servers. You can use the LOCAL_DIRECTORY keyword in the agent's ctsrvr.cfg file to position these files, just as you would with a regular server configuration.