04-25-2012 02:40 PM
Upon entering a new contact today, attempted to schedule date for May 17, 2012. No problem entering date but when attempted to enter time got following message:
Invalid recurrence pattern. Retrieval of named days expects day type of Named. Actual value was None.
After which entire calendar wiped clean. (thankfully still exists on my phone) I have attempted to determine if problem was specific to that contact, but relates to all contacts if attempting to schedule entry for any date beyond May 1, 2012.
Software version: Sage Act! Pro 2012 Version 14.0.572.0 Hot Fix 2
Needless to say, I am unhappy. I have used Act since DOS days, and was quite happy with Act! 2000. I was compelled to purchase this version after purchasing a new computer with Windows 7 OS. I am hopeful someone can suggest a fix to this problem.
04-25-2012 03:44 PM
Update: Installed SP1, did not fix problem. Also, dates seem to appear in dashboard. Calendar erasure appears to be from this month forward. March calendar appears to have all dates intact.
04-26-2012 06:41 AM
Welcome to the Sage ACT! Online Community!
This issue is generally associated with corrupted recurring activities brought into the Sage ACT! calendar through Google synchronization.
If you have synchronized wth Google: Since you have a specific timeframe, try removing the recurring activities from Google for that timeframe and synchronize > test to see if issue is resolved.
04-26-2012 07:58 AM
04-27-2012 07:00 AM
05-24-2013 01:52 PM
I am having an identical error, with the identical event log entry.
I have deleted the recurring event which seems to have triggered this, unsync'ed, re-synced... renamed folders, rebooted, and still the same symptoms... tasks show up, but the calendar is blank. And yes, this is a Google integration and the calendar entry google-side has been deleted, as well as the associated task within ACT.
07-28-2017 03:59 AM
Sorry to hear that this happened, while I am unable to say why the information has disappeared. Would you know what version of Act you updated to? and before the upgrade took place did you manage to take a backup of your database?