![]() ![]() > Cannot open mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=7cc5305b5b0948f5a0d6ded589ced900-test1. Here is my summary email:ġ) We were seeing the below errors/warnings in the MapiHttp logs located here: C:\Program Files\Microsoft\Exchange Server\V15\Logging\MapiHttp\Mailbox\Mapi_Http_xx_x.log when a client dropped it’s connection. We were able to identify the issue and remediate. Server is single Exchange 2016 Standard nodeĬlient are Windows 10 Pro using Office 2016 and Office 2019. Removing all Exchange throttling policies and leave just Global/default.Ĭreate a new throttling policy with all unlimited values and assign to test user. \\HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem Setting the following REGKey in Exchange: I've turned up nothing even working with Microsoft. My question is - where can I look in Exchange (or client) to see why this is happening? To me it sounds like a connection limit threshold or throttling type of problem but all logs (Http Proxy, IIS, Ews, etc.) and Fiddler traces on client result in "200 result - A SSLV3-compatible client Hello handshake was found" - even when Outlook won't launch. Tried on multiple client and versions of Office. ![]() ![]() Closing and re-launching Outlook 2-3 times present's this error. The error is much more frequent if the user in question has numerous delegated shared mailbox access on their account. I understand this is very uncommon but stay with me here. Opening and closing Outlook (2k16/2k19) multiple times in a row causes Outlook to have error "Cannot start Microsoft Outlook. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |