Blog

Smart,Industry,Concept.,Automation,And,Data,Exchange,In,Manufacturing,Technologies.

UPDATED 3/21/13: CRM 2011 for Outlook Will Not Export to a PDF or Office document but it works correctly through Internet Explorer

Are you suddenly seeing the problem that CRM 2011 for Outlook will not export to a PDF or Office document but it works correctly through Internet Explorer?  Here are some possible solutions.

Microsoft has recommended removing these updates, if present: KB2699988, KB2719177, KB2722913 to address this problem.

If removing the above updates does not work, or the updates are not present on the PC, you have 3 more options. (updated as of early this morning 10/19/12)

The latest news from Microsoft is that this is NOT fixed in CRM Rollup 11, but is expected to be addressed in Rollup 12.

Note that the Microsoft’s initial response was option 3a, but this creates a security weakness. Applying the change in 3b fixes the potential problem created through 3a.

1.   The first way would be to run the report from the WebClient,andexport the results from there. (CRM through Internet Explorer)

2.   The second option would be to hitCtrl+Alt,andthen click the export button, from within the OutlookClient.When you choose the file type, it should prompt you to SaveorOpen.

3.    The third option would be to make the following registry key changes:

      a.      The first is the FEATURE_MIME_HANDLING setting in the registry.

           i.      Open the registry (regedit)
         
ii. Go to HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftInternet ExplorerMAINFeatureControlFEATURE_MIME_HANDLING, and change the DWORD entry for OUTLOOK.EXE from 1 to 0
           iii.      Restart Outlook

           iv.      If you have 32 –bit Outlook and 32-bit OS then the path is:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftInternet ExplorerMAINFeatureControlFEATURE_MIME_HANDLING

       b.      The second is the in the FEATURE_RESTRICT_FILEDOWNLOAD in the registry at the following location:

            i.      Open the registry (regedit)
            ii.      Go to HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftInternet ExplorerMAINFeatureControlFEATURE_RESTRICT_FILEDOWNLOAD, and change the DWORD entry
for OUTLOOK.EXE from 1 to 0

            iii.      Restart Outlook
            iv.      If you have 32 –bit Outlook and 32-bit OS then the path is:
                  
   
HKEY_LOCAL_MACHINESOFTWAREMicrosoftInternet ExplorerMAINFeatureControlFEATURE_RESTRICT_FILEDOWNLOAD
 

UPDATED 3/21/13  

The problem with exports not working has been resolved in CRM 2011 Rollup Update 12. For on-premises CRM, when you choose your export format for an unexpected login box…

 Through a support ticket with Microsoft, I learned that this is the way the problem with the export process was resolved. Per MS support: (quoting from case closing)

Cause:
1. This behavior has changed due to IE security restrictions.
2. We are not able to request the report to be downloaded inside the Outlook process due to the way that IE changed how file downloads work in IE9.
3. Because of this the report download must be done in a new instance of IE if the end user does not have the cookie for authentication inside this new instance of IE it will be directed to ADFS to authenticate.
4. This behavior is now considered as by design.
5. This is described here: http://support.microsoft.com/kb/2795627. After you apply hotfix 2699988, and when Internet Explorer 9 is installed, you cannot export reports from a Microsoft Dynamics CRM 2011 Outlook client.

Resolution:
1. When using the internal URL customer will not face issues. This only occurs when using the external URL.
2. There is no really workaround to this as this has been changed for security reason.
3. The only workarounds are ones that disable certain IE security features for the IE Web Browser Control used within specified processes (in our case Outlook). Office Outlook by default opts into these features being turned on. It is not suggested to opt out of these security features.
4. This problem is most commonly seen once you are using IE9 as your browser on Windows.
5. The only official workaround should be to provide login and password to CRM end users.