That's what we are trying to find out. Our transport provider isn't returning 0x800C8100.
↧
New Post: When sending email in Outlook 2013 getting 0x800C8100 error
↧
New Post: When sending email in Outlook 2013 getting 0x800C8100 error
oakietx wrote:
That's what we are trying to find out. Our transport provider isn't returning 0x800C8100.Ok - I'll try my question differently: Did a function call return this error? Did it show up in some dialog box? Did you find it in the event logs? Was it delivered to you on a stone tablet? Where did you get this error from that prompted you to post this question? You got it from somewhere...
↧
↧
New Post: When sending email in Outlook 2013 getting 0x800C8100 error
Of course the error code came from Moses on a stone tablet that was dropped to us from a stork...
From Outlook's Send/Receive error window. And this from Outlook's OPMLog.log file:
2014.12.16 14:45:48 Top of Personal Folders: ReportStatus: RSF_COMPLETED, hr = 0xffffffff800c8100
2014.12.16 14:45:48 Top of Personal Folders: Synch operation completed
2014.12.16 14:45:48 Sending done, Error code = 0x800c8100
From Outlook's Send/Receive error window. And this from Outlook's OPMLog.log file:
2014.12.16 14:45:48 Top of Personal Folders: ReportStatus: RSF_COMPLETED, hr = 0xffffffff800c8100
2014.12.16 14:45:48 Top of Personal Folders: Synch operation completed
2014.12.16 14:45:48 Sending done, Error code = 0x800c8100
↧
Source code checked in, #110833
Port SearchFolderDefinition and PropertyDefinitionStream to new SmartView parsing
↧
Source code checked in, #110850
Add ability for add-ins to provide smart view parsing
↧
↧
Commented Unassigned: MAPI over Http issue for OpenOtherMailBoxFromGAL [17172]
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
↧
Source code checked in, #110860
Problem: Uninitialized data in FileTimeToString leads to bad string, exceptions.
Fix: Initialize data
↧
Source code checked in, #110873
Migrate EntryList to new parser
↧
Source code checked in, #110876
Port RestrictionStruct, SearchFolderDefinition, and RuleCondition to new parser
↧
↧
Source code checked in, #110877
Port PropertyStruct to new parser
↧
Source code checked in, #110882
Port EntryIDStruct to new parser.
↧
Source code checked in, #110883
Fix some casts and annotations
↧
Source code checked in, #110886
Port 6 more parsers
↧
↧
Source code checked in, #110893
Port 3 more parsers to new parser
↧
Source code checked in, #110895
Cut old parsing system
↧
Source code checked in, #110896
Port Security Descriptor parsing to new parser
↧
Source code checked in, #110898
Fix mem leak in additional eid parser
↧
↧
Source code checked in, #110899
Fix leak in AppointmentRecurrencePattern
↧
Source code checked in, #110900
Standardize restriction parser, cut dead code
↧
Source code checked in, #110901
Fix leak in property parser
↧