“After Exchange 2010 to Exchange 2013 migration, Outlook 2010 takes a long time to connect to Exchange Server, some Outlook users start complaining about the Connection Time between Outlook and Environment, as it took more than minutes to connect. Why the connection becomes so slow of Connecting Outlook with Exchange environment.” It seems to hang on Trying to connect for 120-140 seconds, then connects and everything runs fine after that. “Getting problem that’s been driving me nuts for a while and have searched solution on different platforms for Outlook 2016 when connecting from the internet using Outlook anywhere is very slow to connect to my Exchange 2013 server. In this blog, we try to fix this Outlook slow connection issue with Exchange Server, as various queries according to different scenarios asked by Outlook and Exchange user in different forums such as: To Connect with Exchange and Outlook environment, an Administrator needs to create a mailbox in an Exchange environment and after that configure the Outlook profile with Exchange using the Auto Discover technique that helps a user to access the mailboxes connect with Exchange Database.īut sometimes Outlook takes a long time to Connect to Exchange 2013,2010 Server environment, even sometimes connection time took long more the 10 minutes, a problem for Outlook user and lead to less effectiveness in work due to a slow connection between the two environments. If you have feedback for TechNet Subscriber Support, to learn more.Raj Kumar ~ Modified: T11:12:19+00:00 ~ Error ~Īs Outlook Application easily gets configured with Exchange Server for messaging communication for hundreds of users of the Organization. Mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, to learn more. Moreover, if this issue also occurs on external Outlook client, try use ExRCA to test Outlook Autodiscover I will share an article about troubleshooting autodiscover service You can also run “Get-ClientAccessServer |fl” to verify URL for autodiscover.
In order to troubleshooting autodiscover service, you may access the autodiscover URL from IE, if you get "600 invalid request", autodiscover is Ok. If anyone could open outlook successfully, please press ctrl and right click outlook button in the test bas, input email address and password, click Test E-mail AutoConfiguration, check the following information: If there is only one user encountering this issue, please try to delete this Outlook profile and re-create a new one to have a try. How many users encounter this problem, all users, parts of users, or only one particular user? Is that internal user or external user? Does anyone has an Idea of what I forgot or did wrong ? I even tried to create public folder in case. Looked in the logs nothing about my attempts to connect.įinally tried with MFCMAPI and got another error : Error:Ĭode: MAPI_E_FAILONEPROVIDER = 0x8004011Dįunction CallOpenMsgStore( lpMAPISession, reinterpret_cast(m_hWnd), lpEntryID, ulFlags, reinterpret_cast(lppMAPIProp))Īnd am now stuck with these. I tried to run a connectivity test for MAPI, nothing wrong.
CONNECTING OUTLOOK 2016 TO EXCHANGE 2013 HOW TO
So I searched how to fix this and played with certificate, () and nothing went better. Your folders with your Outlook data file (.ost)".
You must connect to Microsoft Exchange with the current profile before you can synchronize While setting up our Exchange, i came across a problem : "Cannot start Microsoft Outlook.