Hi Guys,
I create 2 profiles for a user which has "receive-as" right for the mailbox database in my lab, one profile "Chunk-RPC" is for Outlook Anywhere, another "Chunk-Http" is for MAPI over Http.
when I logon the "Chunk-RPC" with MFCMAPI, and use the session to Open other user's mailbox from gal, everything is good and no problems, but when I use the "Chunk-Http" to logon, I cannot open other user's mailbox, just got "MAPI_E_CALL_FAILED==0x80004005" error code from OpenMsgStore function, Could you please tell me what's the key issue?
Thanks,
Mic
Comments: ** Comment from web user: Bluemoon1200 **
I create 2 profiles for a user which has "receive-as" right for the mailbox database in my lab, one profile "Chunk-RPC" is for Outlook Anywhere, another "Chunk-Http" is for MAPI over Http.
when I logon the "Chunk-RPC" with MFCMAPI, and use the session to Open other user's mailbox from gal, everything is good and no problems, but when I use the "Chunk-Http" to logon, I cannot open other user's mailbox, just got "MAPI_E_CALL_FAILED==0x80004005" error code from OpenMsgStore function, Could you please tell me what's the key issue?
Thanks,
Mic
Comments: ** Comment from web user: Bluemoon1200 **
I have also been unable to open other mailboxes with MFCMapi and Office 365 / HttpMapi. I used the server DN name from Autodiscover and I verified that CreateStoreEntryID2 is supported to indicate a specific server. As Mic noted, opening the mailbox works fine with MAPI/RPC, so my mailbox permissions are correct.
When I dig down and get the inner MAPI error using MAPI's error interface, I get MAPI_E_NETWORK_ERROR for the low level error and 1318 for the context.
It would be fantastic if this could be resolved. This is causing great frustration for us and our customers.
Jim