CRM 2011 Outlook Client: Disable Mapi Caching not working after UR 14

CRM 2011 Dynamics Customers testing and deploying update Rollup 14, have noticed that performance issues resolved in Outlook Client have returned. The registry key for Disable Mapi Caching appears to be no longer be working (reintroduces poor outlook client performance).

Microsoft Support has confirmed that the setting has now been moved to the OrgDbOrgSetting as follows:

DisableMapiCaching Boolean

AddressBookMaterializedViewsEnabled Boolean

It’s recommended to keep your older registry key in place as well to avoid any further issues should a future update switch back to the registry key method.

For information on the OrgDbOrgSetting Tool for Microsoft Dynamics CRM 2011

For more details on the disable Mapi caching for CRM 2011 Outlook client, please review the Microsoft KBs:



CRM 2011: Outlook Client Script Error – Object Doesn’t Support this Property or Method After Applying Update Rollup 8 UR8

Using the Microsoft CRM 2011 Dynamics Outlook client, we detected a weird issue after applying Update Rollup 8. The issue appeared to be related to JSCRIPT on an activity form. After reviewing each activity types form for onload or onchange JScript, then disabling, the issue below was still appearing:








The error did not provide much details, neither did a CRM platform or Outlook Client trace. It turns out that the IE settings mask the real error message. Also note, that Outlook Client is using the IE Settings to connect to the CRM Server. Additionally, the problem DOES NOT OCCUR USING INTERNET EXPLORER – AKA CRM WebClient.

Inside internet explorer options, click the advanced tab, under browsing uncheck the following boxes:














Now we can see the true error message:

The key in the error message was related to the masterWindow Function. This is an internal function to the Microsoft CRM Platform and is related to how IE Frame window is displayed within the outlook client.

After further inspection of the HTML/Script being generated (using F12 for Developer Bar) and Visual Studio debugger attached to the Outlook Process for Script Errors, we saw specific calls related to gathering and updating Metrics via the Microsoft Customer Experience Improvement Program.

Microsoft gathers Metrics (not goals) about your CRM system and you have the option to opt out during your CRM installation.. It turns out the workaround is opting out, which resolves the error until a hotfix or future rollup can be provided (link to fix will be updated in the future).

Here’s how:

Step 1: From Settings, CRM Administration, Select Privacy Preferences


 Step 2: Disable Participation in the Customer Experience Improvement Program:


CRM 2011:Outlook Client Returns More than 250 records when limited

We had a report that the CRM 2011 Outlook Client was returning more than 250 rows even though being limited by the CRM Administrator. It turns out that new pinning behavior in CRM 2011 Outlook client will override that settings. Let’s take a look..

In Outlook client, to the left of the view name, there is a small “Pushpin.”   This pushpin controls whether the view “obeys” the User Setting for the number of records to be shown per view.  Pushpin shown below in the un-pinned position:








When the pushpin is in the up position, it shows all available records that are based on the Users credentials regardless of the settings limitation.  This allows the user to scroll thru all the records at one time.

Although this can be handy when looking for a record lower in the alphabet, it there are ten’s of thousands of records, it could cause a real performance problem.


CRM 2011 Outlook Client displays different navigation than Web Client after Sitemap Customizations

One of our CRM 2011 customers has a modified sitemap. Apparently, some of there machines where not displaying the navigation/sitemap correctly in outlook, but on the same machine the web client was just fine.

CRM 2011 Outlook Client Screen Shot of Navigation – See Order under Tribridge

Web Client Scren Shot of Navigation – Same Machine

It turns out this machine did not have the Office 2010 Cumulative Update for August 2011.

After installation, everything is showing as it appears in the web client.