10-19-2009 09:05 AM
10-21-2009 10:00 AM
First I'd recommend updating to 9.0.1 There are significant fixes. This update would need to be applied to each machine.
Run Check and Repair from within Act.
Cut a new remote. Restore it.
In the original remote Lookup > Contact Activity > Records that have changed since Oct 14th.
Export that lookup to the new database.
10-19-2009 09:24 AM
In our experience there are a number of reasons for it. It doesn't appear to have been resolved entirely in latter versions of ACT! until release 11.1
best advice is to upgrade or a work around is to run a script that stops and starts the sync process on the server each day to release memory.
10-19-2009 09:30 AM
10-19-2009 09:40 AM
10-19-2009 11:52 AM
10-19-2009 12:02 PM
I am relatively unfamiliair with ACT, is there any risk of losing data with re-creating the database for the remote user? Does the data need to be backed up first? I found instructions on through the knowledge base on how to do it, I just want to make sure no data will be lost during the database re-creation. What about data he has entered since the sync has stopped working? will that be lost during the recreation?
10-19-2009 12:20 PM
10-19-2009 02:32 PM
I just want to make sure I get this right, the database needs to be recreated and then the information that has been entered since the last successfuly sync (3 days ago) needs to be imported? Where would that information be imported from? It's all stored on his local machine remote database, does it need to be exported out and then imported once the database is re-created?
10-19-2009 02:48 PM
1. Find all data that has changed on the remote within last 3 days (Lookup Contact Activity)
2.Export to new ACT! database. Import into new incl all user records. This is not a merge at contact field level, it will overwrite, so you need to identify if on the main database there is data changed on the equivalent records that you want to preserve. Then export to main database but backup the main database first so that you can recover if there is a problem.
3. Cut new remote database and restore to the remote.
4. Alternatively use a merge software such as Oakmerge at www.oakmerge.com if there is a large amount of data and it needs to merge. I guess not much will have changed in 3 days however.