- Edited by Ghildebr Friday, October 17, 2014 12:54 AM
- Edited by Ghildebr Friday, October 17, 2014 12:54 AM
- Edited by Ghildebr Friday, October 17, 2014 12:54 AM
Hi,
Thank you for sharing the information. You feedback is very import to us. We would continue to monitor and would escalate it if more community members meet the same issue like you.
Best Regards,
Steve Fan
Forum Support
Same here - all my customers face this issue. Uninstalling the patch helps.
Strange thing is, my Mailbox is on Office 365 connected over MAPI/HTTP, I have the patch installed but no issues so far.
Maybe we should change some config settings on the MAPI VDIR in Exchange?
Christian
Has anyone from Microsoft acknowledged that this is a problem? I have approximately 100 users that are affected with this issue. The only course of action that I have found is to uninstall the update. The two bullets bellow are supposedly what was fixed with KB2986204.
- Outlook 2013 may be unable to connect to an Exchange server by using the MAPI over HTTP protocol.
- When you send an email message that contains a large attachment by using Outlook 2013, Outlook may stop responding.
With the patch uninstalled I am having occasional problems with Outlook Freezing when sending attachments. The funny thing is that I never had any connectivity issues until I installed this patch. Does anyone know of an alternate workaround so possibly I could have this patch installed to prevent the freezing issues while still being able to connect?
Hi All,
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Steve Fan
Forum Support
I have the same issue, Outlook since KB2986204 keep prompting for login/password.
But I'm unable to uninstall the update, how did you manage to do that ?
Did you get in touch with someone to help us ?
This issue seems to grow up (http://community.office365.com/en-us/f/172.aspx?Sort=Active&pi14112=1)
The update appear multiple time, its ok for now ...
Just found this article. Hopefully this will have a fix for the issue.
- Edited by George.B.Summers Friday, November 21, 2014 5:38 PM
- Edited by George.B.Summers Friday, November 21, 2014 5:38 PM
Brian,
Can you please open a support case for us to investigate the issue. We are tracking a couple bugs with OAuth and MAPI/HTTP but nothing that matches what you are seeing. So far I am not seeing any other support cases for this issue. Also, is this an on prem issue or are you using the O365 service?
- Edited by Gabriel BrattonMicrosoft employee Thursday, November 13, 2014 6:24 PM
Brian,
Can you please open a support case for us to investigate the issue. We are tracking a couple bugs with OAuth and MAPI/HTTP but nothing that matches what you are seeing. So far I am not seeing any other support cases for this issue. Also, is this an on prem issue or are you using the O365 service?
- Edited by Gabriel BrattonMicrosoft employee Thursday, November 13, 2014 6:24 PM
Brian,
Can you please open a support case for us to investigate the issue. We are tracking a couple bugs with OAuth and MAPI/HTTP but nothing that matches what you are seeing. So far I am not seeing any other support cases for this issue. Also, is this an on prem issue or are you using the O365 service?
- Edited by Gabriel BrattonMicrosoft employee Thursday, November 13, 2014 6:24 PM
*sigh*
This is for the office team:
Is it really that difficult to release an Outlook Version that simply works?
It doesn't matter which feature you look at - they're all buggy.
Especially Autodiscover is a mess if you work with Exchange 2013. Outlook never get's it right... (maybe you should finally start using the Autodiscover Webservice and not the legacy XML file...like Lync does!)
So I ask myself: Are you short on resources? No manpower for on premise testing?
I work with Outlook since the first Version. But it got worse an worse over the years...
Christian
Hello,
I fully agree to Christian. Same problem here, we have to fix it manually which is an enormous effort for us.
I would really kindly ask the microsoft team to bring a fix ASAP.
Really disappointed.
Apologies, but I've never opened a support case before and am not sure how. I also don't have access to the back-end of our email system. I do know that our email system was migrated last winter from on-prem to O365. (I would have responded sooner, however I did not get an email alert that this thread had been responded to even though I have it marked for alerts).
Thanks,
Brian
Brian,
You will need to find the Office 365 Portal Administrator in your company to open a support case. Only the Portal Admin can open a case. I have been watching for any new issues and so far I am not seeing us getting any unexpected volume on authentication related problems. It is possible there is some configuration issue that is specific to your tenant.
The OAB download issue is supposed to be fixed in the November 11 2014 updates, http://support.microsoft.com/kb/2899504. Double check the version shows correctly. It should be 15.0.4667.1000 or 15.0.4667.1002 depending if C2R or MSI. What exactly is the issue that you are seeing?
I had not installed KB2986204 because of this issue but I did install KB2899504 today and KB2986204 is no longer being offered and I have not OAB issues with KB29899504.
Delaney,
There have been some additional fixes since the November updates. Please test by installing all of the latest updates from Windows Update. If you are still seeing auth prompts after that open a support case for us to investigate further. Are you on Office 365? Did the auth prompt issue just start happening?
Gabriel,
The prompts started happening when I installed both 204 and 504, and stopped after I uninstalled them. That was back in December. I've installed all other Office 2013 updates that have come out since then, but have not reapplied these two, as I was waiting to see if another Outlook update would come out before trying again. Yes, we are on Office 365.
KB2956087
It was been install on our machines today.
So looks like we have another one this time: KB2956170
Causing credential popup and stops as soon as this is uninstalled.
This is 4 now! what is going on MS??
Anyone else experienced this?
Derik,
I am not aware of any auth prompt known issues for the Outlook February or March PU's. Are you on Office 365 or on premise? Since there are no known major issues it would be best to open a support case to investigate further.
We have an on premise 2013 box CU7.
We've had this same issue with the following:
KB2986204
KB2899504
KB2956087
and now KB2956170
I have found a couple of machines that have install the last one OK with no prompt so looks to not affect everyone but everyone has the same update level and settings.
I'm not sure even how I go about opening a support request?
This has got to be a widespread issue, not only affecting OAB download but also Autodiscover.
Reference: https://social.technet.microsoft.com/Forums/office/en-US/ed448c52-1dfd-49ec-bb45-20750bc87490/autodiscover-broken-after-office-update?forum=exchangesvrclients
Microsoft, please sit up and take notice! As someone mentioned above, there are way too many replies of "me too" here.
It appears this has now been resolved, at least for us anyway!
After installing KB3039799 password prompts have stopped and all seems to be working as advertised