This article is tracking recent issues for user(s) that have upgraded to Act! v22.1. Our support team are monitoring the situation and this content will be updated as further information emerges.
Product : Act! v22.1
Email integration functionality is different in v22.1
This is due to a change in the architecture behind the email integration. please see the following article for more information:
Act! in the Cloud contact detail view displays a blank window
If you are experiencing an issue when logging into Act! in the Cloud where Contact, Companies or Groups detail view displays a blank page this can be resolved by deleting cache as described in the article below.
Error: "Looks like we are unable to authenticate, please renter your password" when opening Microsoft Outlook
If when opening Outlook you are prompted for a password as described above. You should enter your Act! password then complete the Email System Set-up wizard. Instructions in the article below.
What does "Act! is Loading your Address Book" Mean?
Setting up Outlook integration for the first time as a new user or as an upgrading user requires your contacts to load into an address book in Outlook. Users are reporting long load times, more information can be found in the article below.
Update: Some users are reporting that while the address book is loading for the first time the Outlook UI becomes unresponsive. This is currently under investigation. Initial findings indicate that exchange accounts are taking longer to load the address book and Outlook 2019 64-bit UI is more likely to become unresponsive. Users are reporting that if Outlook is minimised this process does complete but may take some time.
Out of Memory Exceptions or Act Shared WordCrush Spell Checker exceptions
Users are reporting either Exception of type 'System.OutOfMemoryException' was thrown or The type initializer for 'Act.Shared.WordCrush.WordCrushSpellChecker' threw an exception, errors intermittently displaying. This is under investigation and it may be necessary to collect log files to understand the cause. Please contact the support team for your region.