Outlook Client

Webformhost errors with Office 2016

I encountered an error with the CRM 2011 Client for Outlook when running on Office 2016. The error is about webformhost failing.

Although CRM 2011 is compatible with Office 2016 according to the compatibility matrix, it seems that several people have this issue.

The resolution that worked for me was to add a registry key as follows:

HKEY_CURRENT_USER > Software > Microsoft >MSCRMClient > UseWebFormProcessIsolation'

Use a DWORD32 key type and set the value to 0.

Flashing cursor in Outlook with CRM Client

I have seen instances of the CRM client in Outlook where the cursor keeps flashing. A search revealed an unexpected fix.

  1. Create a file named Microsoft.CRM.Application.Outlook.WebFormsHost.exe.config with no content.
  2. Move the file to the C:\Program Files\Microsoft Dynamics CRM\Client\res\web\bin or wherever your CRM client is installed.

That's it. This I found at https://community.dynamics.com/crm/f/117/t/166875


Install CRM Client 2011 after removing CRM Client 2013

If you have installed CRM 2013 for Outlook and then need to go back to CRM 2011 for Outlook, perform these steps:

  • Uninstall CRM 2013 for Outlook
  • Delete the program folder, the default location is C:\Program Files\Microsoft Dynamics CRM (or C:\Program Files (x86)\Microsoft Dynamics CRM for a 32-bit install on a 64-bit computer).
  • Delete the MSCRM registry keys located at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft and HKEY_CURRENT_USER\Software\Microsoft. There might be several keys including MSCRMClient, MSCRMIntegration, MSCRM_Setup and MSCRM.


CRM 2011 Client for Outlook- problem communicating with server

The installating guide for CRM 2011 strongly recommends that a low privilege domain account is used for the CRM and ASP.NET services.

Having followed this advice I found I was unable to configure the Outlook Client to connect to the CRM server. The error I got was "there is a problem communicating with the server". Examining the log file, Crm50ClientConfig.log, revealed the following error: