01-02-2019 07:44 AM
Is anyone experiencing Outlook lockups using Act 21 update5?
Requesting Help
If you are running Act 21 and syncing to Outlook 2016 without issues can you please reply with the Office version number you are running? I'm desperate to find a solution and I'm willing to create new machine builds to troubleshoot.
My issue
We upgraded a bunch of users to Act 21 due to the licensing issue and now Outlook 2016 (multiple build versions) randomly stop responding. Sometimes it starts working again after 30 seconds to 10 minutes but more often than not we need to end the Outlook task. Act doesn't even need to be open for the issue to appear. The only fix so far is to disable the Act outlook add-in. It's happening on older PC's that used to have a different version of Act installed as well as brand new just out of the box PC's.
All computers are Running Windows 10 with Outlook 2016
Outlook version:
16.0.4738.1000
16.0.6769.2017
16.0.7030.1021
Windows 10 versions:
1703
1709
1803
Any help on this would be greatly appreciated
Thanks
01-02-2019 11:23 AM
01-02-2019 11:40 AM
Thanks for the reply.
We don't use Office click to run. All installs are MSI and our Outlook versions range is from before 16.0.6965.2058 and after. User access control is gone and we tested things out with firewall/antivirus disabled.
As a test, I restored a database backup, removed 21 from one of the troubled machines then installed 20.1 and everything worked. No lockups at all. Reinstalled 21 and the issues came right back.
11-18-2020 12:02 PM
Has anyone experienced this issue? We have nearly 400 computers still running 20.1 because of this issue. I've revisited it a few times but can't figure out what's causing it.
I've tried calling support and they're telling me our databases are corrupt which isn't the case. If we don't have a reason/solution by the end of the year we are ready to move to an alternative.
11-19-2020 08:23 AM
Issue still happening on Windows build 1909
11-19-2020 08:58 AM
Question..... What Outlook folders does the Act add-in scan? Does it try and scan Exchange public folders if they're visible?
I have a suspicion that it's scanning the public folders which are many terabyte's in size hence the Outlook crash.
a week ago
We're a pretty big organization and all troubleshooting paths have been exhausted. We have decided to live without the add-on until our alternative CRM has been built. Act don't seem to care about the problem so we won't be renewing our contract.
Thanks