Has anyone encountered a issue with Outlook running out of memory when an email archive program is also in use. We were told by our supplier that this is a known issue and the only way to fix is to turn off email archiver. This is not an option. It seems to be linked to the dll for the TRIM addin. Any help would be greatly appreciated, We are on 126.96.36.1995
Update: QCCR2D45095 has been closed by HP as they don't intend to fix the issue. Customers are advised to speak with their e-mail archiving vendor about why their product is causing the TRIM in Outlook add-in to fail.
Note: Any posts I make on this forum are my own personal opinion and (unless explicitly stated) do not constitute a formal commitment on behalf of HPE.
(Please state the version of CM you're using in all posts.
HPE Software Support Online (SSO): https://softwaresupport.hpe.com/
We are also getting the Outlook "Out of Memory" error message.
But our issue is arising when users do a search in Outlook for an email and try to click on the stub of the archived email.
i.e. Nothing at all to do with TRIM!
Turning off the TRIM add-in in Outlook resolves the issue.
What I would like to know is what is TRIM doing in Outlook when a search is being done? An email search has nothing to do with TRIM. We have tested this on a freshly reimaged machine, no document queues set up, no other links between Outlook and TRIM apart from the Add-in, and can consistently replicate the issue and the fact that turning off the TRIM add-in fixes the problem.
The TRIM integration isn't actually doing anything in particular when a search is executed within Outlook. However, the TRIM integration is using the Outlook Explorer and Inspector classes (part of the Outlook Object model) to determine how the buttons on the toolbar or tabs should change based on the currently selected item. When you initiate a search this will fire off events to the explorer and inspector classes and I bet that's where things start getting stuffed up.
Since you're using an archival tool the integration may be running into conflicts or a ton of calls from the API. Not sure exactly but just speculating. There are known issues with some third party integrations (like archiving tools).
Your best course of action is to put in a support ticket and see what HP can determine for you. Outside of that, turn on verbose integration logging and see what it's actually doing during that search. Lastly, upgrade to the latest version.