You’re offline. This is a read only version of the page.
1,332
A few months ago I successfully configured the Dynamics 365 App for Outlook. It worked correctly in all environments until yesterday.
Application Versions:
CRM: 8.2.5.4 (on-prem)
AD FS: 3.0 (Server 2012 R2)
Outlook 2016 (16.0.4843.1000)
Exchange is on-prem as well.
Beginning yesterday, when users try to access Dynamics 365 within the Outlook client, they are prompted for credentials, via the AD FS form prompt, however the window does not dismiss after a successful credential challenge. The "We're reviewing you Dynamics 365 information..." spinner continues to spin in the reading pane, but will ultimately time out with the message:
*This post is locked for comments
Same problem here! Is there a solution availabel?
Envrionment:
Dynamics 365 on-prem 8.2.4.6 -> No Updates installed the last few month
Exchange on-prem 2016 -> No Updates installed the last few month
AD FS 3.0 Server (2012r2) -> No Updates installed the last few month
Outlook 365 -> local Windows 10 latest updates
Outlook 2013 (VDI) -> No Updates installed the last few month
OWA not working
Outlook local and VDI not working
Error: MailApp Error
Activity ID: 8ba42b29-43b6-593a-07a6-dc32e5740382 Date: Fri, 01 Nov 2019 13:39:25 GMT Error: [MailApp] Client loader timed out Trace: Error at ClientError (xxx/.../shim.js at Anonymous function (xxx/.../shim.js at Anonymous function (xxx/.../jquery-2.1.1.js:45:37186) at l (xxx/.../jquery-2.1.1.js:45:35813) at s.fireWith (xxx/.../jquery-2.1.1.js:45:36575) at t[] (xxx/.../jquery-2.1.1.js:45:37600) at Anonymous function (xxx/.../shim.js
How could that happen???
Help please :)
The affected file was fixed in CDN. The file is cached locally for 24 hours, so users would need to clear out their local IE cache in order to get the fix immediately, otherwise, it may take up to 24 hours to surface in the client without such manual action. As fix was done on Friday 7/19/2019, so you should not see this issue anymore.
Microsoft just fixed a bug in their Office Javascript API. This fixed the issue for my users.
Hi Everyone
Just wanted to pile on - we are having the exact same issue at our end (CRM 8.2.3.8 On-Premise, Outlook 2016, Exchange Online). Haven't had much luck with uninstalling the patch but we have had confirmation from Microsoft that it's a wide-spread problem and they're "working on it".
In the meanwhile I can confirm that Outlook 2019 is unaffected so we are just going to roll our users up to 2019 as we need to do that sooner or later anyway. Not sure if that's an option for everyone, but our user base is pretty small so not too much work involved.
Also OWA works fine, however for some reason our users find this "impossible" to use, even as a temporary workaround [shrug]. Jerks.
Thanks for raising this issue anyway, it's always nice to know that it's not just us, or something we've done to ourselves.
We have a customer with the same problem since July 9th/July 10th.
We opened a Microsoft Case on July 10th - but no progress so far.
Uninstalling the update KB4464534 didn't fix the problem for us.
And additionally the customer has clients without that update where this error occurs, too.
Regarding the environment of the customer:
- Dynamics 365 On-Prem (Version 8.2.5.4 (DB 8.2.2.2114)) (English with German MUI)
- Exchange Online
- Windows Client: Windows 10 Enterprise Version 1803 (OS Build 17134.829) (English with German MUI)
- Office/Outlook: 2016 (16.0.4849.1000) 32-Bit (English with German MUI)
- IE Version: 11.829.17134.0
Yesterday a Dynamics developer commented on my issue in the Office Javascript API github (github.com/.../612) that they were able to reproduce the issue. It seems like it is a global issue with their side of things and we just have to wait until someone at Microsoft fixes it. Hopefully soon. I have an open support ticket with Microsoft like Jos but haven't heard much yet.
It's giving the white screen after the credential challenge, I made sure KB4464534 was gone after rebooting the affected system. Other people that are experiencing this problem aren't an the office today so i can't test your solution on another computer unfortunately.
I will keep you updated on any official solutions from Microsoft.
Joe,
Is it showing you the white screen before or after the credential challenge? One thing I have noticed is that KB4464534 will reinstall itself on a reboot, probably depending on your Windows Update settings. Can you try pausing Windows Update, reboot, make sure KB4464534 is still gone?
I am working on permanently hiding that KB on my PC this morning. I have been back and forth a few times now between working / not working based on pausing Windows Update and removing that KB.
I am very glad to hear that you have a ticket open with Microsoft though, please be sure to let us know what their solution is.
So, we have the exact same problem since last week and have a ticket open with Microsoft Support but that's taking some time. Today i stumbled against your topic and tried removing KB4464534 on an affected computer. After rebooting i double checked if the KB4464534 was removed and it was. After opening Outlook an trying to track an e-mail it still throws the white screen.
Any suggestions (beside reinstalling outlook 2016)? People who are experiencing this problem are using Chrome and webmail for now as workaround.
Testing over the weekend shows that removing KB4464534 will resolve the issue on Windows 10 for me.
My core set of users are still okay now as well after uninstalling and reinstalling Outlook once. I cannot explain why they were impacted in the first place, and I am still concerned that the issue is going to come back for them. I know everyone in this thread has mentioned impacted PCs being that did not take updates, and I'm having a hard time letting this go because of that.
Also interesting, if you authenticate successfully, then install KB4464534, you will stay authenticated for some time, probably defined by the TokenLifetime on the ADFSRelyingPartyTrust. After the token times out and you are prompted to login again, the authentication will fail.
I think that is consistent with Doug Fraser's findings, if the token is cached then the broken JavaScript will never run and the issue will not occur.
#1
Mohamed Amine Mahmoudi
83
Super User 2025 Season 1
#2
Community Member
54
#3
Victor Onyebuchi
6
Share
Report
All responses (
Answers (
