11-19-2018 02:32 PM
Started getting this error message after upgrading to v21 from 20.1. Message is displayed after launching ACT! on both the Parent and the Child databases.
This only happens on my personal database, which is very customized, including custom tables built with Topline Designer. This message does not appear when opening the demo database.
Act! Premium Version 21.0.295.0, Update 1
Windows 10 and Window Server 1012R2
11-19-2018 02:37 PM
11-22-2018 07:24 AM
The "Object of type 'Act.Framework.ComponentModel.Workflow.SendEmailActivity' cannot be converted to type 'System.Collection.ArrayList' error message appears to have been corrected with v21 Update 2.
The sync problem resulting from the database upgrade to 21 from 20.1 was resolved only by creating a new Parent/Publisher database from my existing Remote database. All repairs and efforts to cure whatever corruption happened with the Parent database when upgrading to v21 did not work. Working with ACT! Tech Support they finally suggested creating a new Parent/Publisher database from my existing Remote database which thankfully did work. Apparently the Remote database was not corrupted during the v21 upgrade, only the Parent database.
I am still not sure why the corruption occurred. Another database upgraded at the same time, moved from the same v20.1 server to the new v21 server did not have the problem. The only obvious difference in the corrupted database and the non-corrupted database is that the corrupted database has custom tables. The non-corrupted database has many custom fields, but no custom tables.
I am almost certain that the corruption happened as result of the upgrade to v21 because the original copy of the database on the old v20.1 server had no sync problem.
03-02-2020 04:13 PM
Hi Phillip. Did ever resolve this? I have the same issue on a customers DB recently upgraded from v20.1 to v21.1. They have many custom fields but no custom tables, so a bit different to your experience. I suspect a damaged.Net Framework because of other issues the v21.1 upgrade was an attempt to repair. Upgrading to v21.1 has at least provided a workable version of Act! but it would be good to resolve this error now popping-up.