The following notice was provided to us by the Swiftpage development team, and we wanted our customers to be aware of a situation that may impact them. Please note this is a Microsoft issue, not an Act! one, but it can have real implications on Act!'s ability to integrate with som versions of Outlook 2016. As our Act4outlook relies on the "mscoree.dll" file included with Act!'s integration with Outlook,  Act4outlook cannot overcome this broken file.

 

Issue:  Certain versions of outlook 2016 are simply broken for integration applications that rely on outlooks' MAPI interface, we fall under this umbrella.  There is not a solution we can apply to our software to solve this without a complete re-architecture.

Resolution: 

 

There are two distinct situations we are aware of that have slightly different solutions broken out as follows:

 

User has Retail copy of Outlook 2016.  Retail copy ships with a version that is known to be broken for MAPI and thus our integration. To resolve this issue you must DOWNGRADE office to 16.0.4229.0. To Downgrade I have included a batch file to make this process easier. After this outlook auto-updater needs be disabled as well for office updates. To disable:  

 

Key: HKEY_LOCAL_MACHINE\software\policies\microsoft\office\16.0\common\OfficeUpdate

DWORD: EnableAutomaticUpdates = 0

 

 

Case #2:
User has 365 Subscription.  They will need to update to the “current” subscription Channel from the “deferred” Channel or “No Update” Channel if set as such.  Again, for ease of application/deployment, the simplest way is accomplish this is to download the fix here.  This should update you to the latest Subscription version which corrects the MAPI API Problem.  This will resolve the issue.