question

SuyPeang-0083 avatar image
0 Votes"
SuyPeang-0083 asked KenanKesgin-3368 edited

Cannot start Microsoft Outlook. Cannot open Outlook window. The set of folders cannot be opened. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost"

Dear All Experts,

I am using Exchange server 2016 on the server 2012. I have created one share mailbox. And added some users to access the share mailbox, when sign in using share mailbox "Cannot start Microsoft Outlook. Cannot open Outlook window. The set of folders cannot be opened. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)". What’s possible issue with share mailbox?

office-exchange-server-administrationoffice-outlook-itprooffice-exchange-online-itprooffice-exchange-hybrid-itpro
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi, @SuyPeang-0083 ,
As this thread is not related to SharePoint, I am removing the SharePoint tag here.

0 Votes 0 ·
Oast avatar image
0 Votes"
Oast answered SuyPeang-0083 commented

Two things to try:

  1. Go to Control Panel > Mail > Email Account > Click Change > Insert your correct User ID and Password > Check box Save Password > Click OK.

  2. Ensure the Microsoft Exchange RPC Client Access service starts when the server boots up

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello,

Thanks for your reply.

Each user have their own mailbox, they have sign in to their email and can open and add share mailbox to their outlook.
But our intention don't want them to use their own email, we want them to use share mailbox only.
We used this scenario and working for a few day ago, and it's just have issue yesterday.

0 Votes 0 ·

The issue has resolve after restart Microsoft Exchange RPC Client Access service

Thanks you!

1 Vote 1 ·
LucasLiu-MSFT avatar image
0 Votes"
LucasLiu-MSFT answered SuyPeang-0083 commented

Hi @SuyPeang-0083 ,
Does the issue occur to only one user or do all users have the issue?
1. In order to better solve the issue, I would like to confirm with you the " sign in using share mailbox" you mentioned. According to my research, the shared mailbox is a type of user mailbox that doesn't have its own username and password. As a result, users can't log into them directly. So would you like to share with me how you logged in?
2. Please try to log in to OWA using the issue mailbox to see if you can log in and open the shared mailbox.
3. Please try to re-create a new outlook profile and then run the “outlook /safe” in the run to open the outlook as safe mode.
4. Please try to re-create the .ost file.
5.In Exchange 2016, MAPI over HTTP is enabled by default at the organization level, please run the following command to check the user whether enable the MAPI:

 Get-OrganizationConfig | fl *mapi*
 Get-CASmailbox -Identity "<>" | fl *mapi*



If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.




· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @SuyPeang-0083 ,
Do suggestions above help? If the issue has been resolved, please click “Accept as answer” to mark helpful reply as an answer, this will make answer searching in the forum easier and be beneficial to other community members as well.

Thanks for your understanding.



If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


0 Votes 0 ·

Hi sir,

The issue has resolve after restart Microsoft Exchange RPC Client Access service

Thanks you!

0 Votes 0 ·