Our team recently came across an issue where customers reported to us that the CRM Client for Outlook appears to be properly configured and connected, but the CRM records do not display as expected.
The problem manifests as “waiting for a page to be retrieved” and the expected records from CRM are never brought after waiting over an hour.
In our screenshot, the Contacts Entity is selected, and the CRM Client is configured properly, with the CRM menu showing as active when in the ribbon menu.
The issue has been traced to the October 2017 Microsoft Outlook security update. The details from the related Microsoft KB article explain the problem:
“The October 2017 Microsoft Outlook security update disables roaming home pages in Outlook to address a significant vulnerability with the application, and as such, inadvertently causes the add-in to fail.”
To fix the issue, you need to add a registry entry based on the version of Office that you have installed. (setting value to 2, for future use, per the article)
Microsoft Outlook 2016:
Microsoft Outlook 2013:
Microsoft Outlook 2010:
Once this registry key is added to the local client, reboot the PC. The add-in will be able to render webpages without issue. Microsoft recommends applying the extra registry key instead of removing the security update, as it addresses a significant vulnerability in Outlook.
The full article with detailed explanation is
Beringer Technology Group, a leading Microsoft Gold Certified Partner specializing in