Error when clicking on mailbox - 0x8004011D

[bencarter007]

Opening profile, no problems.

Click on mailbox, and we receive this error:

Error:
Code: MAPI_E_FAILONEPROVIDER == 0x8004011D
Function lpSession->OpenMsgStore( ulUIParam, lpEID->cb, reinterpret_cast(lpEID->lpb), nullptr, ulFlags, static_cast<LPMDB*>(&lpMDB))
File D:\a\1\s\core\mapi\mapiStoreFunctions.cpp
Line 39

Any help greatly appreciated...

Ben

[Giovpi]

Same issue. Please help. This started happening to me today. MFCMAPI was just fine a few days ago. I updated to the latest version today thinking that was the issue since the version I had was a few months old but didnt fix the error.

[alpha079]

I am getting the same error.
This error is generated by a Third Party software , in which the Software creates a Outlook Profile. This outlook profiles then open the mailboxes of every user. This is being run in a Service User created by the third party application.

When I try to open the profile in the MFCMAPI tool(by running it in Service User), I am not able to access the openMessage Store. Getting the below error
Error:
Code: MAPI_E_FAILONEPROVIDER == 0x8004011D
Function lpSession->OpenMsgStore( ulUIParam, lpEID->cb, reinterpret_cast(lpEID->lpb), nullptr, ulFlags, static_cast<LPMDB*>(&lpMDB))
File D:\a\1\s\core\mapi\mapiStoreFunctions.cpp
Line 39
..

But when I run the MFCMAPI tool in admin user, I am able to open the MessageStore with the same profile created by Service user.
Please can you help why admin is able to open MessageStore, but not Service User. I am accessing the cloud mailboxes.

Current Env: Window 10

[KoekieMie]

Still having the same issue for quite a while when checking the MDB_ONLINE and MAPI_NO_CACHE flag (eg. for https://learn.microsoft.com/en-us/outlook/troubleshoot/calendaring/errors-when-configure-free-busy-or-delegate-information#method-2-use-mfcmapi-tool)
All the proposed solutions are already done, nothing works (Open Outlook in Cached mode to cash the creds; Using an online profile in Outlook; reinstalling office)

[KoekieMie]

Just discovered that in my case the error was caused by an outbound Firewall Rule blocking MFCMAPI...