12-27-2012 11:03 PM
I have been running ACT 2007 since 2007 on two PCs running XP Pro with one synchronize db. Recently the remote PC running ACT in a sync mode has been locking up after launching the application. I uninstalled and reinstalled the program twice and it still locks up after launch. Anyone experienced similar problem?
12-28-2012 05:37 AM
12-28-2012 01:17 PM
12-31-2012 10:55 AM
I have a similar propblem with ACT 2007. My old computer died and I am attempting to re-install ACT 2007 (9.0) on my new desktop. Initially tried copying ACT directory from old disk to new "C" drive - That did not work. Then downloaded the ACT 9.0 update file from this site. It aborts during installation with error message "Z_StrActNotFound".
HELP! - I really need to get access to my customer database. My old computer was running Windows XP, new one is on Windows 7 if that matters. I was able to locate my customer Serial# and Activation code, but cant get far enough to re-register.
Any ideas on how to get past this error and re-install on my new computer? (I would prefer not to upgrade, as the old version does everything I need)
12-31-2012 11:20 AM
ACT! 2007 isn't supported on Windows 7.
01-02-2013 05:58 AM
Since it appears to be database specific, I would perform maintenance on the main database using ACTDiag. Here is an article with instructions: KB Article 26854
01-02-2013 12:26 PM
Should I perform the maintenance on the remote computer DB (where I cannot run ACT) or should I do that to the main DB on my base computer (where ACT is running normally)? Since the problem is with ACT on the remote computer I have been using the main computer to continue adding contacts. Would it work if I delete the remote computer's ACT DB and export out to that computer the DB from the main computer and then re-establish the sync again?
01-02-2013 01:52 PM
Run maintenance on the remote database (that isn't responding).
You may or may not be able to import the data from the 'bad' remote - depending on what is causing the issue. If the maintenance does not resolve the issue, go ahead and create a new remote to restore on the workstation and test open/syncing with it. If successful, continue using it.
Generally when importing a 'broken' remote, we recommend an Export by opening the remote database and performing a Contact Activity search for a date near the time the remote stopped synchronizing, then use the Export function - selecting Current Lookup. This would be to reduce the amount of data being exported. Since you can't work within the database, that doesn't sound like an option.
You may be able to use the Import function from the new remote, to pull in the old remote data.
Keep in mind that importing/exporting data from a corrupted database has the potential of introducing the issue into the receiving database.