MEMIS.exe unstable in 10.35 release

Raise/discuss any potential issues with MailEnable for consideration in project issue register.
Post Reply
Posts: 6
Joined: Mon Feb 22, 2021 8:30 pm

MEMIS.exe unstable in 10.35 release

Post by » Tue Jul 27, 2021 12:09 am

We are seeing continued crashes of the MEMIS.exe service on 10.35 -- crash was not happening in the beta of 10.35. Started appearing when we moved to the official release.

We have seen where restarting the service causes instant crash. Restarting IMAP service resolves the restart issue with MEMIS.exe

This coincides with certain occasions where IMAP service starts consuming large amounts of processor time - then MEMIS crashes, and IMAP keeps running - but with what seems like a hung thread somewhere.

We are still trying to isolate what causes IMAP to use high CPU.
memis.exe.error.jpg (126 KiB) Viewed 3679 times

Site Admin
Posts: 9586
Joined: Mon Mar 22, 2004 4:44 am
Location: Melbourne, Victoria, Australia

Re: MEMIS.exe unstable in 10.35 release

Post by MailEnable-Ian » Wed Jul 28, 2021 4:34 am


Can you upgrade to the 10.36 beta on our beta page to see if his addresses your crashing problems. If not then please lodge a support ticket and provide access to the server via RDP or Teamviewer so a technician to inspect the relevant log files and configuration in more detail to troubleshoot further.

Ian Margarone
MailEnable Support

Posts: 127
Joined: Sat May 29, 2021 11:16 am

Re: MEMIS.exe unstable in 10.35 release

Post by poweredge » Fri Jul 30, 2021 3:54 am

Is there anyway to downgrade to 10.34?
Posts: 6
Joined: Mon Feb 22, 2021 8:30 pm

Re: MEMIS.exe unstable in 10.35 release

Post by » Fri Oct 29, 2021 1:42 pm

Recent changes to MEMIS.exe (tested in v10.36 and 10.37) seem to have resolved the random crash from MEMIS.exe

Normally users don't come back and post when something is working (only when it's broke). As such, I wanted to take a moment to note that whatever issue was causing the crash (I assume trying to index deleted messages) seems to have been resolved.

Thank you for your time!

Post Reply