Forum Discussion
zznate
Mar 23, 2021Copper Contributor
Outlook cannot connect to exchange but OWA can
Hi, Ive built a new exchange 2019 environment on windows 2019 server (twice) and each time i get the following error when trying to connect my outlook on the win10 client to exchange "Cannot...
bhallgccc
Nov 29, 2022Copper Contributor
Did you ever figure this out?
I did a test restore of an Active Directory server and an Exchange 2019 server in an offline/disconnected network. Everything works fine except Outlook 2016 gives me a similar error (but instead of mentioning the Information Store, it says "The set of folders can't be opened. You must connect to Microsoft Exchange with the current profile before you can synchronize with your Outlook data file.").
Like your situation, OWA works perfectly fine and mail flows between internal mailboxes using OWA. Connecting Outlook 2016 succeeds in connecting to Exchange (all green arrows, autodiscover working fine), and the profile is successfully created, but then when Outlook loads to the Inbox, that message appears.
I find it interesting that in both your case and mine, there is no Internet. This was restored from a perfectly working Exchange 2019 server that is still in production, the only difference being no Internet for the test restore network.
I did a test restore of an Active Directory server and an Exchange 2019 server in an offline/disconnected network. Everything works fine except Outlook 2016 gives me a similar error (but instead of mentioning the Information Store, it says "The set of folders can't be opened. You must connect to Microsoft Exchange with the current profile before you can synchronize with your Outlook data file.").
Like your situation, OWA works perfectly fine and mail flows between internal mailboxes using OWA. Connecting Outlook 2016 succeeds in connecting to Exchange (all green arrows, autodiscover working fine), and the profile is successfully created, but then when Outlook loads to the Inbox, that message appears.
I find it interesting that in both your case and mine, there is no Internet. This was restored from a perfectly working Exchange 2019 server that is still in production, the only difference being no Internet for the test restore network.