MailService.exe crash
Problem reported by David Thomas - November 9 at 2:43 AM
Submitted
Since yesterday, we have had a problem with our Smartermail installation.
Server : Windows Server 2012 R2

yesterday at 16:34
Smartermail : 16.3.6870

Application: MailService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FF8D7E563B0 (00007FF8D7D20000) with exit code 80131506.

Faulting application name: MailService.exe, version: 16.3.6870.30534, time stamp: 0x5bcf53ab
Faulting module name: clr.dll, version: 4.7.3190.0, time stamp: 0x5b693b48
Exception code: 0xc0000005
Fault offset: 0x00000000001363b0
Faulting process id: 0x49c
Faulting application start time: 0x01d46bff14c96d14
Faulting application path: C:\Program Files (x86)\SmarterTools\SmarterMail\Service\MailService.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: c12e6bcd-e36b-11e8-8121-c477d0556725
Faulting package full name:
Faulting package-relative application ID:

last night, update of smartermail (16.3.6885) and.NET Framework (KB4462921 and KB4462502)

today at 09:38

Application: MailService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFF4A90F0DA (00007FFF4A760000) with exit code 80131506.

Faulting application name: MailService.exe, version: 16.3.6885.29302, time stamp: 0x5be3108c
Faulting module name: clr.dll, version: 4.7.3221.0, time stamp: 0x5b885a56
Exception code: 0xc0000005
Fault offset: 0x00000000001af0da
Faulting process id: 0x4b8
Faulting application start time: 0x01d47797666b8b1b
Faulting application path: C:\Program Files (x86)\SmarterTools\SmarterMail\Service\MailService.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: e22bbdac-e3fa-11e8-8123-84d9a565a8cf
Faulting package full name:
Faulting package-relative application ID:

Any ideas?

3 Replies

Reply to Thread
2
Scarab Replied
I've been getting these as well. 3 times yesterday and once today on v16.3.6885 Enterprise running under Win2016. Hopefully someone at SM has some insight as to the cause and a fix.
0
Ionel Aurelian Rau Replied
Really disconcerting. So v16.3.6885 is not worth updating to?
4
Scott Forsythe Replied
We also had crashes about a week ago with SM Version 15.7.6821. We upgraded to 15.7.6855 and haven't crashed since. I'm not totally confident that the problem was fixed since it wasn't mentioned in the release notes.

With our problem, the SM service stopped and we received the same error in the Application log:
"The process was terminated due to an internal error in the .NET Runtime...with exit code 80131506"

Vote this thread up.

Reply to Thread