-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: Failed to retrieve headers. #37
Comments
Could you open the gear icon and click diagnostics, then paste the output here? |
Hi, Thank you for replying. I apologize about post #18. Everything was working before and no major updates have been applied to our environment. How can I diagnose the REST or EWS? Outlook for Mac uses EWS and everything seems to be working. Let me know if you need anything else. Once again, thank you for looking into this.
|
I think I need to put some more breadcrumbs in my error code. But ultimately, I think this is gonna be a server issue. Fiddler will show the traffic of requests. As I note in #18 (comment), you should see one of them failing. |
Hi Stephen, |
I’m on vacation for a week, but when I get back I’d love to look at the fiddler output. |
Updated error logging should get us an error message+stack now |
On the hunch that namespaces are an issue, I renamed my callback - if this fixes this issue I need to do real work to clean up namespaces. |
Hi Stephen, **** The results below were obtained using Fiddler and the IE developer tools ** |
Dunno if I've fixed this one, but I think the error should change. Please speak up if you're still getting "Sys.ArgumentNullException: Value cannot be null. Parameter name: callback" or if the error has morphed. Also let me know if that was your error and now it works. Thanks! |
I've got a repro of this now... |
Ok - so here's the bug:
However, this returns false for our callback function. Over in C2R, this same check now looks like this:
Where argIsFunction is defined like so:
So in 2016 MSI, makeEwsRequestAsync thinks we didn't pass a callback, but in 2016 C2R, it correctly concludes we did. Action plan: Report this back to Office dev, and also continue to hack to see if I can force something past the isInstanceOfType check. |
Didn't mean to close this without verification - anyone still getting Failed to retrieve headers? If you were getting it and it's now fixed, please report that. If you're still getting it, please report updated diagnostics output, including the stack. Thanks! |
Hi Stephen, Outlook for Windows
Still broken on these browsers and clients. Neither Classic or New view worked:
Attached diagnostics output below. -------- Outlook for Mac User Agent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/604.5.6 (KHTML, like Gecko) User Agent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/604.5.6 (KHTML, like Gecko) |
@luisjmoreno It looks like neither of those errors/stacks match the "Failed to retrieve headers" issue, so I'm gonna declare this one as fixed. I'll open new bugs to track these issues. |
This was caused by issuing our requests from an iFrame. Fixed by #50 which moved the calls back to the main frame |
(ported from #18 for @luisjmoreno)
Hi Stephen,
Bad news, I noticed a new change on the MHA version. Unfortunately, this new version broke everywhere in all my devices Mac, Windows and Internet Browsers. MHA doesn't work on any browser or email client such as Outlook for Windows or Mac.
Before this new version / change, MHC was working only on Outlook for Windows. Now, when I run MHA on an email on Windows, I get a message that says "Failed to retrieve headers". I have removed and re-added the app and still does not work.
Screen shot in Outlook for Mac
Screen shot in Outlook for Windows
Screen shot within OWA using Google Chrome (same results within other browsers, including IE)
We are running Exchange 2013 CU18 on premises. I have a different email on Outlook.com where I use MHA too and it works there. Please help!!
The text was updated successfully, but these errors were encountered: