01-25-2017 09:20 PM
I am turning to the Community for help!
This issues is effecting:
Act! Premium Version 220.127.116.11, Update 3 (happened in v17 and v18 also)
Windows 7 and 10
We are constantly running into an issue where randomly a users database will stop syncing and start throwing the "accept incoming sync" error:
This obviously has nothing to do with the system settings or the hosted servers, and it happens during the fourth step in the sync process, so clearly the connection was made successfully.
Once this happens there is no coming back all data is typically lost between syncs. Exporting the data to a syncing database will typically break that one also. I would like to figure out what the cause of this could be, are there logs on my end I can use to gather real information about the issue. The ActDiag Sync Logs are not really helpful and the SQL logs don't seem to show me much about the syncing.
Is this happening to other users?
Thanks for any support.
01-26-2017 12:46 AM
A common cause for failure at this point is when ACT tries to sync an attachment that it is either corrupted or has been saved with restricted access.
It can also be caused where sync from the remote is done when the machine is not on use for any other purpose and goes into energy save or sleep mode after a period of time.
01-26-2017 04:40 PM
Thanks for the response!
Our attachments were an issue in the past, so we don't really allow them anymore. If I go into the attachments folder in Windows Explorer it is empty and still wont sync.
It is also definitely not an energy save mode issue.
01-27-2017 03:49 AM - edited 01-27-2017 06:22 AM
On the server can you stop the Network Sync Service from running (Assuming you are running this.) and start the ACT sync service in ACT Tools Sync - Accept incoming syncs and then try to sync the remote.
If this fails it could be the timeout settings with a link below on how to change them. Roughly how long into the sync is the failure?
01-28-2017 02:36 PM - edited 01-28-2017 02:52 PM
We have Act Premium Cloud. I imagine we do not have access to such files.
Well I found the local files for Synchronization Time Outs, and modified them. It appears that this keeps failing at the same point though. It gets to the same point: 2 of 3180 records
This problem has occurred maybe two dozen times in the past. A database will be working one day and dead with these symptoms the next. Usually with varying amounts of records and data left to sync, but always at the Synchronizing Records and Updates phase.
01-29-2017 02:13 AM - edited 01-30-2017 03:44 AM
I know you say you do not sync attachments but this is a classic symptom of trying to sync a damaged or restricted access attachment. Is it all remotes or just one? If one are there any recent attachments added to the database?
Without going back through the thread have you also carried out all the rebuild options and repair using ACTDIAG for the database?
01-29-2017 11:12 AM
We currently only have 12 attachments in the Database which are from over a month ago. I assume by simply removing all the items from the Attachements Folder I would be able to check to see if that was the issue?
Right now it just is affecting a single DB
I have Rebuilt and Repaired the DB
Thanks again for all your assistance.
01-30-2017 08:08 AM
01-30-2017 11:18 AM
01-30-2017 01:58 PM
It would be an issue if it was created on the remote or made restricted access or corrupted on the remote and it was trying to sync it.