New Post: DOES MAPI HAVE A SATURATION LEVEL?

We are actually working with MAPI in several threads at one time, and an error in one thread leads to a waterfall of errors in the others.

In common when first error happens when we are trying to establish connection IMAPISession::OpenMsgStore() call that returns us Mailbox instance, that attempt fails and we get a bunch of errors with creating items and folders. Errors on item and folder levels almost always might be overcome by redoing the problem operation, I mean to do a few more attempts helps. The odd thing is we can be operating just fine and then all of the sudden we will see 20-30 errors in 1-2 seconds and then hours can pass before we get another instance.

IMAPISession::OpenMsgStore()

• MAPI error: not logged
  Low level MAPI error: 1142
  Message from MAPI: The attempt to log on to Microsoft Exchange has failed.
  
• MAPI error: not logged
  Low level MAPI error: MAPI_E_NETWORK_ERROR
  Message from MAPI: Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance.
  

IMAPIFolder::CreateFolder()
IMAPIFolder::CreateMessage()

• MAPI error: MAPI_E_NETWORK_ERROR
  

IMAPIProp::SaveChanges()

• MAPI error: MAPI_E_NETWORK_ERROR
  Low level MAPI error: 0x80040115
  Message from MAPI: Network problems are preventing connection to Microsoft Exchange.
  
• MAPI error: MAPI_E_NO_ACCESS
  Low level MAPI error: 0x80070005
  Message from MAPI: You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator.