Event ID: 29057 - A problem was encountered while trying to process a saveset in the storage queue, <0x8004011b>.

Problem

For Journal or Mailbox archiving, an Enterprise Vault (EV) server's Storage Queue may reach maximum length and StorageArchive may throw frequent 29057 events indicating a recoverable error for each item it processes, as seen below:



The details of the maximum storage queue length can be found in the Vault Admin Console > Enterprise Vault > Directory > (Site Name) > Enterprise Vault Servers > (Server name/alias) > Services > Storage Sevice, properties of the Storage Service > Storage Queue tab.

 

Error Message

The 0x8004011b translates to "mapi corrupt data."  A dtrace of StorageArchive shows the issue with each item begins here:

1035286 14:02:00.959  [38380] (StorageArchive) <23420> EV:L {CMsgSess::OpenMsg:#63} Opening IMsg on IStg, Unicode [True].
1035293 14:02:00.959  [38380] (StorageArchive) <23420> EV:M {CMsgSess::OpenMsg:#80} Failed to open message: [0x8004011b]
1035297 14:02:00.959  [38380] (StorageArchive) <23420> EV:H {CMAPISaveset::OpenSharedMessageOnIMsg} (Exit) Status: [<0x8004011b>]
1035300 14:02:00.959  [38380] (StorageArchive) <23420> EV:L {CMAPISaveset::OpenSharedMessage} (Exit) Status: [Exception]
1035302 14:02:00.959  [38380] (StorageArchive) <23420> EV:L {CMAPISaveset::get__MAPIOBJECT} (Exit) Status: [Exception]
1035307 14:02:00.959  [38380] (StorageArchive) <23420> EV:L {CMAPISaveset::InitOriginalMessageClass} (Exit) Status: [Exception]
1035310 14:02:00.959  [38380] (StorageArchive) <23420> EV:H {CMAPISaveset2::get_OriginalMessageClass:#414} _com_error exception: [<0x8004011b>]
1035312 14:02:00.959  [38380] (StorageArchive) <23420> EV:H {CMAPISaveset2::get_OriginalMessageClass} (Exit) Status: [<0x8004011b>]

 

Cause

Initial analysis might point to the savesets being corrupt or damaged.  However in several cases the issue is missing the following registry setting:

HKEY_CURRENT_USER
\Software
  \Microsoft
   \Office
    \ version
     \Outlook
      \Options
       \Mail
      
Dword: RecipientMax
Value:  (hex) ffffffff

Solution

This particular issue arises during the StorageArchive process, and thus the RecipientMax registry setting is equally as important on the EV server hosting the vault store and Storage Queue of the targets as the EV servers with archiving tasks. Ensure the key is in place on all EV servers that have either archiving tasks or an active Storage Service.

This is a best practice registry setting and should be in place on all EV servers.  Upon installing EV, the wizard will attempt to add all best-practice settings unless explicitly instructed not to by the person installing.  The key can also be added manually at any time.