Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
Have HP Envy 17T with Windows 8.1 and Office 365 PowerPro 64 bit installed. Outlook worked fine until I installed CRM 2015 for Outlook. Now when CRM is loading in Outlook the cursor starts flashing from Normal to Busy rapidly and will not stop. Can't type (unless I catch a second between busy and normal). I uninstalled CRM 2015 for Outlook and it is working fine. However, I really need CRM for Outlook working.
I can start Outlook as Administrator and it doesn't create the flickering cursor.
Hope someone can help.
What is the CRM Client for outlook version on ?
What is the CRM Server Version ?
Try to disable all other addin from outlook and try.
I reported the problem via our Office 365 administration web and received a call the next day from Gaurav Tempe who was very helpful. We identified that the root cause of the issue was the missing config file. There was no webformhost.exe process in Task Manager. We created an empty config file on the desktop and named it as "Microsoft.CRM.Application.Outlook.WebFormsHost.exe.config" and imported this file in the folder: Program Files>>>res>>>web>>bin
Problem is resolved.
Some of our users had the same problem and your fix did work. The only confusing part was the file path you indicated. Instead of:
It should be:
C:\Program Files\Microsoft Dynamics CRM\Client\res\web\bin
Thanks for the fix!
It worked! Thanks!
This also fixed my issue. Outlook 2010, CRM 2015, constant flashing. However I noticed when I double click on records in Outlook CRM 2015 that it doesn't pop up in an IE window. IE is set to my default browser. Am I missing something simple or does the newly created config file need to be populated with something?
Same here. With the empty config file, the flashing stopped. BUT I can no longer open up any CRM records from my Outlook CRM plugin.
We've had this problem for a long time already. We had received word from Microsoft that once CRM was upgraded to 2015 the problem would go away. No! Flashing without the config file, and inability to open CRM records with the empty config file. I have no choice but to go without the config file and close my Microsoft Dynamics GP 2015 whenever flashing starts. I cannot understand why Microsoft CRM 2015 would not be compatible with Microsoft Great Plains 2015 ?!
Please, can someone help.
We were having similar issues with Outlook 2013 and the CRM 2013 client installed on Windows 8.1. Even installing the "Update Rollup 4 for Microsoft Dynamics CRM 2013 Service Pack 1" did not fix the issue.
As a workaround we've granted "requireAdministrator" security level to the Outlook executable using the OUTLOOK.EXE.MANIFEST file. Note that our CRM users have administrator privileges on their local computer.
C:\Program Files (x86)\Microsoft Office\Office15\OUTLOOK.EXE.MANIFEST
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity processorArchitecture="*" type="win32" name="outlook" version="220.127.116.11"></assemblyIdentity>
<description>Microsoft Office Outlook</description>
<!-- <requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel> -->
<requestedExecutionLevel level="requireAdministrator" uiAccess="false"></requestedExecutionLevel>
<!--The ID below indicates application support for Windows 7 -->
<!--This Id value indicates the application supports Windows 8 functionality-->
<!-- This Id value indicates the application supports Windows 8.1 functionality-->
<!-- This Id value indicates the application supports Windows 10 functionality-->
<assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="18.104.22.168" publicKeyToken="6595b64144ccf1df" language="*" processorArchitecture="*"></assemblyIdentity>
Also our "Microsoft.CRM.Application.Outlook.WebFormsHost.exe.config" file is not empty, but instead contains the following:
<defaultProxy enabled="false" useDefaultCredentials="true" >
<proxy autoDetect="false" />
You may want to adapt this to correspond with the proxy settings applicable for your network.