Back

ACT Syncing Files - way to get remotes syncing


Here is a circumvention for the ACT! Sync hanging at "Synchronizing Files" issue.

This process needs cooperation at both the publisher (master) end and the subscriber (remote) end of the synchronization. Both ends need to be told to not send the file data. This is the part of the process that seems to get hung and can take multiple hours, even on a fast link, or never finish at all.

1. Back up (using the ACT! File/Backup method) both the publisher and the subscriber data bases. This will be needed to potentially restore supplemental files that are overwritten and lost by the recovery process.

2. On the subscriber end, with ACT! down, edit the ACTSage.Exe.Config file (found in the ACT! Program Files\Act\Act for Windows directory). Find the section that begins <appSettings>. Find the line that begins <add key="Synchronization.SyncFileData">. Change the parameter value="true" to value="false".

3. On the publisher end, it depends on what sync agent is being used. If you are using the Network Sync agent, the config file to change is Act.Framework.Synchronization.Service.exe.config. It will be at Program Files\ACT\Act for Windows\Act Network Sync folder. Find the same key as above and set it to "false". If this process has never been done before, you may need to add a complete <appsettings> section as follows:
<appSettings>
<!-- A bi-directional transport setting to avoid encryption of sync data. Helps in improving sync performance.
Note: Must be set in both client and server -->
<add key="Synchronization.UseEncryption" value="true"/>
<!-- A uni-directional file sync override to shut off any files from syncing. Helps in sync debugging.
Note: Can be set in either or both client and server -->
<add key="Synchronization.SyncFileData" value="true"/>
<!-- A uni-directional file sync setting to sync files in pieces or as a whole. Sets to false only when sync files are small in size (few KBs)
Note: Can be set in either or both client and server -->
<add key="Synchronization.SyncFilesInPieces" value="true"/>
</appSettings>

4. Make this edit with the Network Sync agent stopped. Once the config file is changed, restart the Network Sync agent.

5. Start up ACT! as the subscriber and begin a sync. Be patient. If there is a significant amount of data built up, it still may take a while to get the sync to run.

6. Once the first sync completes successfully, do a second sync. If you interrupted a sync, remember that the first sync only progresses to the point that the interrupted sync would cover. A second sync is needed to get changes since that time to the current time.

7. Shutdown both ACT! on the subscriber and the ACT! sync agent on the publisher. Edit the two config files and set "Synchronization.SyncFileData" back to "true".

8. Look in the various supplemental file folders for zero length files. These files are corrupted. With ACT! down, and with the sync agent down, restore these files individually from the backup ZIP file taken in step 1, overlaying the zero length files. Do this at both the publisher end and the subscriber end. Use a tool such as WinZip to extract just the affected files from the backup files. If there is a zero length file that is not part of the backup, it is a new file. Delete the zero length file before it causes even more trouble. These files will be resolved if possible in a later step in this process.

9. Start up ACT! at the subscriber and the sync agent. Do another sync. It should finish normally, perhaps having no data to transfer. Shut down ACT! at the subscriber.

10. Run a Missing Attachments report from ACTDIAG at both the subscriber and the publisher. These may be files that needed to be transferred but were not. Find the file at the other end, and transport the file using whatever method makes sense (email attachment, FTP, flash drive, etc.). Remember to write the file to the target supplemental file directories with ACT! down on that machine (or the directory watcher will notice the file as updated and will try to sync it again, possibly getting you back to step 1 again).

11. After resolving whatever files can be transferred, run another Missing Attachments report to verify you have resolved the issue the best you can.

12. Do an "After fixing things" backup of both the Publisher and the Subscriber data base again.




Back