Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Getting an error when using the Outlook Add-In for Outlook 2013. Retrieval of a page from a CRM server failed due to an error.
See Screenshot: www.screencast.com/.../T5FPF4ehUHnP
Same issue for my users with CRM 2011 add-in for Outlook 2010. I haven't yet started uninstalling the six Windows Update October security updates. I will soon, to determine which is the offending update, unless someone else out there has already found which one is at fault.
I encountered this same problem. Functionality was restored after removal of KB4011178 in my testing.
Issue seen in the following environment: Outlook 2013 32bit / CRM Server 2011 / Various CU's for Outlook client testing
Uninstalling Security Update for Microsoft Outlook 2010 (KB4011196) fixed MS Dynamics CRM 4.0 for Outlook 2010 for us.
This has also broken the CRM 2011 Add-In when running in Office 2016 (with the UseWebFormProcessIsolation = 0x0 registry entry defined).
Confirmed on multiple machines running Win10/Office2016.
Rolling back updates (only WSUS updates identified as Critical or Security were applied) on the affected machines has restored functionality temporarily.
One of my users has also reported issues with browser access following the update (some data not being saved), but I have not yet independently confirmed this.
Our on premise CRM 2015 is likewise broken for Outlook Plugin Users, but only those still on Office 2013 Pro+. Most users are on Office 2016 Pro+ from Ofice365 and these users are thankfully not affected. I suspect an Office2013 update but we are simply upgrading those few users up to Office 2016 since all are licensed.
Did you do anything else beside removing the updates? We have the same issue at some clients, but it seems not to be enough to remove the updates. They still have issues to connect to CRM from the Outlook app.
We reverted the users to a system restore point pending further deployment testing and investigation.
Thanks for input. Did you by any chance created a support issue at Microsoft Support, regarding this issue? I was wondering if I should create one - And I think it might could help if I could refere to others.
Thanks flyingflea - uninstalling Security Update for Microsoft Outlook 2010 (KB4011196) fixed MS Dynamics CRM 4.0 for Outlook 2010 for us.
I have not created a support issue with MS Support at this stage because the CRM 2011 client is, I understand, not officially supported with Office 2016/Office 365 and it is only by using the UseWebFormProcessIsolation edit in the registry that were we able to use this particular combination for the past while, pending an upgrade to CRM 2016.
I hope that because the update is security-related and appears to be affecting more recent versions of the CRM Outlook Client, we should see a further security update shortly.
Just for anyone with Outlook 2010, we ran into this with a client today as well and the bad update is KB4011196
I can also confirm that KB4011178 (Outlook 2013) and KB4011196 (Outlook 2010) once removed, fixed the issue for my CRM tracking users on-premise CRM 4.0. Thanks for those that suggested this!
For Outlook 2016, the update to remove is KB4011162
Same issue is evident in my company's environment.
We have Office 2013, and 2016. We have CRM 2016, and 2011, both are having issues connecting via Outlook Addin Tool.
User's can however access it online without issue.
We're going to roll back KB4011178 for now as it's not the big security update as a whole.
Is Microsoft aware of this? I've been deleting this every day and came back the next day.
Business Applications communities