Enterprise Vault 10.0.3 Hotfix: CMAPI throws CONTENTMANAGEMENTAPI_E_INTERNAL_FAILURE for items having no PR_SUBJECT property

  • Modified Date:
  • Article ID:000018101


Collection software, such as Clearwell that use the method call 'pItem->Get(DETAIL_LEVEL_ITEM_CONTENT_SECTION_LIST)' would cause CMAPI to throw CONTENTMANAGEMENTAPI_E_INTERNAL_FAILURE exception for items sent from wireless devices where the subject is missing.  


Error Message

  •  ERROR EVContentRetrieverJob null - Error in m_getSectionIDForJournalMessage: pItem->Get() , error code: 0x80040306 , message: CONTENTMANAGEMENTAPI_E_INTERNAL_FAILURE:An internal failure occurred
  • Failure to successfully collect all items from Enterprise Vault; message: CONTENTMANAGEMENTAPI_E_INTERNAL_FAILURE.


 Emails sent by wireless devices do not include a subject line.  Microsoft Exchange 2010 does not add a blank PR_SUBJECT attribute for wireless device messages.  Enterprise Vault method 'pItem->Get(DETAIL_LEVEL_ITEM_CONTENT_SECTION_LIST)' to extract items from EV, requires the existence of the PR_SUBJECT attribute.




Cumulative Hotfix 2 must be installed prior to applying this hotfix


Files updated
Installation instructions
1. Stop the Enterprise Vault Storage service.
2. Take a backup copy of 'StorageOnlineOpns.exe', located in the Enterprise Vault installation folder, (usually C:\Program Files (x86)\Enterprise Vault).
3. Replace the original file with the file from the hotfix package.
4. Start the Enterprise Vault Storage service.
Uninstallation instructions
1. Stop the Enterprise Vault Storage service.
2. Replace the hotfixed version of the file with the backup taken during installation.
3. Start the Enterprise Vault Storage service.


Applies To

Product: Enterprise Vault (EV)
Version: 10.0.3 with Cumulative Hotfix2

(Hotfix will only function with EV version 10.0.3 with Cumulative Hotfix 2 installed.  The resolution is rolled into EV version 10.0.4)

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)