SmarterMail service stops several times every day
Problem reported by Astralis - July 29, 2017 at 4:52 AM
Submitted
This has been an ongoing problem for a while. I asked about this before and changed the DNS within SM to use Google DNS and it appeared to work for a while. But the problem has returned and the MS event viewer does not offer any clues.
 
Please advise. 

12 Replies

Reply to Thread
0
Paul Blank Replied
It is doubtful that your DNS setting(s) are the issue. A couple of years ago, I had the SM service stop on me a couple of times. The SM server had mirrored (RAID1) drives, and one of those drives was failing. I finally figured this out, replaced the bad drive, and the problem went away.
 
That said, the SM service stopping could be due to many causes. It does not appear to be a common problem with SmarterMail.
 
Your system logs might provide a clue.
 
0
Astralis Replied
The system logs do not point to anything about this. I mentioned this in my OM.
0
Paul Blank Replied
Yes, you did mention it. I recall that there was no clue in the system logs either when I had that drive issue. The drive problem had gotten worse and the controller management software was what alerted me. Your issue, of course, could still be something entirely different. 
0
Astralis Replied
Not sure if it matters, but this is not a RAID server. I appreciate that you share your experience to help troubleshoot. I've had several people manually time the moment the SM server stops working. There is no pattern yet except that it will go down multiple times per day -- up to six times every day but maybe one or two times a week it will go down every 6 hours. It seems so random, so far.
0
Paul Blank Replied
Since SM is not known for the service shutting itself down as a general rule, you should still try and check fully for disk errors and system memory errors, many of which are not reported in the logs, as you already know.
 
Have you tried setting the service to restart automatically if it stops (in the Recovery tab of the services dialog)? This is not a very elegant fix, but it can help in the short term.
 
When I come upon problems such as these, I will sometimes "simply" - I know it isn't necessarily simple - move the entire product to a different machine. I understand that cost may be a concern, but it might be the best way to rule out hardware errors.
0
Astralis Replied
Thank you. I never thought about the restart automatically tool. Totally knew that and forgot it existed.
0
Astralis Replied
Update: The server is staying alive after I selected the server to restart on fail. So far, everything has been great. Because I am unable to trace why SM is failing is a problem, though. At the least I get my mail...
1
Von-Austin See Replied
Employee Post
Astralis,
 
It sounds like mailservice.exe may be forcefully crashing due to an unhandled exception. I would strongly advise opening a support ticket with us so we can gather some process dump files to determine what's crashing the software on your server. 
 
You can take a shot at this yourself using DebugDiag2 Collection to capture the process dump when a crash is observed. DebugDiag 2 can be obtained from Microsoft's download page here: https://www.microsoft.com/en-us/download/details.aspx?id=49924
 
  • Once installed launch Debug Diag Collection and setup a new rule for Crash and select Next.
  • You should then be presented with a list of processes. Locate mailservice.exe and select Next.
  • You can leave the default values on the next page and hit next.
  • Enter the name for your crash rule and select the Output location then select Next.
  • Select the Activate Rule Now option and select Finish. 
 
Once the crash occurs, you should find a full dump file located in the output directory you specified when creating the rule. You can leverage the DebugDIag2 Analysis application to perform a Crash\Hang analysis on the dump file. The report generated should give you more information as to what specifically had caused the crash. If you could provide the stack trace we may be able to point you in the right direction.
 
If you were to open a support ticket can can certainly work with you to analyze the process dump on our end to see what specifically was occurring in our code when the crash took place. 
 
 
Von See
Technical Support Supervisor
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Paul Blank Replied
Thanks for posting this, Von. Take note that this is for >=Server 2008 And =>Vista.
So it probably won't work right out of the box with Server 2003/XP. There is some stuff online regarding getting it to work, but I haven't tried it.
 
 
 
0
Astralis Replied
Thanks for this. I will give this a try. It's crashing so bad. The auto-restart via Windows properties has been helpful but only about 50 percent of the time. Otherwise, this requires me to check to manually restart it. Unless there's another solution, I will craft a script to run a BAT file to restart the app on crash, but I'm concerned that I might lose too much email throughout the day.

Interstingly, this never happened until the past year.
0
Astralis Replied
What do you make of this?

Loading control script C:\Program Files\DebugDiag\scripts\CrashRule_Process_MailService.exe.vbs
DumpPath set to C:\Program Files\DebugDiag\Logs\Crash rule for all instances of MailService.exe
[9/12/2017 10:45:29 PM]
Process created. BaseModule - C:\Program Files (x86)\SmarterTools\SmarterMail\Service\MailService.exe. BaseThread - System ID: 7568
C:\Windows\system32\ntdll.dll loaded at 0x77040000
Thread created. New thread - System ID: 3084
Thread created. New thread - System ID: 4152
Thread created. New thread - System ID: 3404
Thread created. New thread - System ID: 8900
Thread created. New thread - System ID: 2884
Thread created. New thread - System ID: 3964
Thread created. New thread - System ID: 2024
Thread created. New thread - System ID: 6024
Thread created. New thread - System ID: 5948
Thread created. New thread - System ID: 6936
[9/12/2017 10:45:30 PM]
Thread created. New thread - System ID: 6036
Thread created. New thread - System ID: 8120
Thread created. New thread - System ID: 3860
Thread created. New thread - System ID: 3388
Thread created. New thread - System ID: 8032
Thread created. New thread - System ID: 4420
Thread created. New thread - System ID: 7444
Thread created. New thread - System ID: 5504
Thread created. New thread - System ID: 1752
Thread created. New thread - System ID: 7804
Thread created. New thread - System ID: 3548
Thread created. New thread - System ID: 6440
Thread created. New thread - System ID: 4836
Thread created. New thread - System ID: 8672
Thread created. New thread - System ID: 8344
Thread created. New thread - System ID: 4336
Thread created. New thread - System ID: 8940
Thread created. New thread - System ID: 2300
Thread created. New thread - System ID: 7520
C:\Windows\system32\mscoree.dll loaded at 0xfa360000
C:\Windows\system32\KERNEL32.dll loaded at 0x76cf0000
C:\Windows\system32\ADVAPI32.dll loaded at 0xfdb90000
C:\Windows\system32\RPCRT4.dll loaded at 0xfdec0000
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll loaded at 0xfa220000
C:\Windows\system32\SHLWAPI.dll loaded at 0xff1f0000
C:\Windows\system32\GDI32.dll loaded at 0xfe480000
C:\Windows\system32\USER32.dll loaded at 0x76c20000
C:\Windows\system32\msvcrt.dll loaded at 0xfe4f0000
C:\Windows\system32\IMM32.DLL loaded at 0xfda70000
C:\Windows\system32\MSCTF.dll loaded at 0xfdcc0000
C:\Windows\system32\LPK.DLL loaded at 0xfe290000
C:\Windows\system32\USP10.dll loaded at 0xfdaa0000
C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.19373_none_151129cef4086113\comctl32.dll loaded at 0xfc130000
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll loaded at 0xf8ee0000
C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4016_none_88dc01492fb256de\MSVCR80.dll loaded at 0x748d0000
[9/12/2017 10:45:31 PM]
C:\Windows\system32\shell32.dll loaded at 0xfe590000
C:\Windows\system32\ole32.dll loaded at 0xfe010000
C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\0f7b33b7db5dd844076f0338e8541da6\mscorlib.ni.dll loaded at 0xf7120000
C:\Windows\assembly\NativeImages_v2.0.50727_64\System\4e4b98872bc3ea158f51db39d99d300b\System.ni.dll loaded at 0xf66e0000
C:\Windows\assembly\NativeImages_v2.0.50727_64\System.ServiceProce#\342a95aee5e7b64469a137bf41f89b3e\System.ServiceProcess.ni.dll loaded at 0xfb460000
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll loaded at 0xf9cd0000
C:\Program Files (x86)\SmarterTools\SmarterMail\Service\MailServer.dll loaded at 0x744a0000
C:\Program Files (x86)\SmarterTools\SmarterMail\Service\SmarterTools.Licensing.dll loaded at 0x74c40000
C:\Program Files (x86)\SmarterTools\SmarterMail\Service\SmarterTools.Common.dll loaded at 0x742e0000
C:\Program Files (x86)\SmarterTools\SmarterMail\Service\MailStore.dll loaded at 0x74230000
C:\Program Files (x86)\SmarterTools\SmarterMail\Service\SmarterTools.ReportEngine.dll loaded at 0x74bc0000
C:\Program Files (x86)\SmarterTools\SmarterMail\Service\RelayServer.dll loaded at 0x74200000
C:\Program Files (x86)\SmarterTools\SmarterMail\Service\TcpServerLib.dll loaded at 0x737c0000
C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Xml\e3b600cdd210758af8cd83f49574012f\System.Xml.ni.dll loaded at 0xf8180000
C:\Windows\system32\NTMARTA.DLL loaded at 0xfca90000
C:\Windows\system32\WLDAP32.dll loaded at 0xff300000
C:\Windows\system32\WS2_32.dll loaded at 0xfdb40000
C:\Windows\system32\NSI.dll loaded at 0xfdeb0000
C:\Windows\system32\PSAPI.DLL loaded at 0x771e0000
C:\Windows\system32\SAMLIB.dll loaded at 0xfd340000
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\perfcounter.dll loaded at 0xfb420000
C:\Windows\system32\OLEAUT32.dll loaded at 0xfddd0000
C:\Windows\system32\pdh.dll loaded at 0xfa1d0000
C:\Windows\system32\MSVCR120_CLR0400.dll loaded at 0xf40d0000
C:\Windows\system32\aspnet_counters.dll loaded at 0xfb510000
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_perf.dll loaded at 0xfb500000
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_perf.dll loaded at 0xfa160000
C:\Windows\system32\Secur32.dll loaded at 0xfd8c0000
C:\Windows\system32\NETAPI32.dll loaded at 0xfd3d0000
C:\Windows\system32\DNSAPI.dll loaded at 0xfd370000
C:\Windows\system32\cryptdll.dll loaded at 0xfd770000
C:\Windows\system32\USERENV.dll loaded at 0xfd8e0000
[9/12/2017 10:45:32 PM]
C:\Windows\system32\wls0wndh.dll loaded at 0xf9920000
C:\Windows\system32\IPHLPAPI.DLL loaded at 0xfd0a0000
C:\Windows\system32\dhcpcsvc.DLL loaded at 0xfd050000
C:\Windows\system32\WINNSI.DLL loaded at 0xfd040000
C:\Windows\system32\dhcpcsvc6.DLL loaded at 0xfd010000
C:\Windows\system32\rasman.dll loaded at 0xfb940000
C:\Windows\system32\CRYPT32.dll loaded at 0xfd170000
C:\Windows\system32\MSASN1.dll loaded at 0xfd320000
C:\Windows\system32\credssp.dll loaded at 0xfcff0000
C:\Windows\system32\schannel.dll loaded at 0xfcb90000
C:\Windows\system32\msv1_0.dll loaded at 0xfce20000
C:\Windows\system32\tapi32.dll loaded at 0xfb690000
C:\Windows\system32\rtutils.dll loaded at 0xfb920000
C:\Windows\system32\WINMM.dll loaded at 0xfb650000
C:\Windows\system32\OLEACC.dll loaded at 0xfb590000
C:\Windows\system32\mswsock.dll loaded at 0xfcdd0000
C:\Windows\System32\wshtcpip.dll loaded at 0xfca40000
C:\Windows\System32\wship6.dll loaded at 0xfcfd0000
C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Configuration\92397ee50a4526bdf23eddcb1df6980e\System.Configuration.ni.dll loaded at 0xf50d0000
C:\Windows\system32\NLAapi.dll loaded at 0xfc850000
C:\Windows\system32\napinsp.dll loaded at 0xf8b30000
C:\Windows\System32\winrnr.dll loaded at 0xf8cd0000
C:\Windows\system32\rasadhlp.dll loaded at 0xf8ba0000
C:\Program Files (x86)\SmarterTools\SmarterMail\Service\SmarterTools.Events.dll loaded at 0x741e0000
C:\Windows\assembly\NativeImages_v2.0.50727_64\System.DirectorySer#\7fd0e6e243170eb58cf3b963d2c49555\System.DirectoryServices.ni.dll loaded at 0xee9e0000
C:\Windows\system32\activeds.dll loaded at 0xfaab0000
C:\Windows\system32\adsldpc.dll loaded at 0xfa800000
C:\Windows\system32\credui.dll loaded at 0xfa7c0000
C:\Windows\system32\ATL.DLL loaded at 0xfc7f0000
C:\Windows\system32\CLBCatQ.DLL loaded at 0xfe1f0000
C:\Windows\system32\adsldp.dll loaded at 0xf9c70000
C:\Windows\system32\SXS.DLL loaded at 0xfd6e0000
C:\Windows\system32\cscapi.dll loaded at 0xfa570000
C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Web.Services\5ee65e3d7a94412923d860e18807fbae\System.Web.Services.ni.dll loaded at 0xedfa0000
C:\Program Files (x86)\SmarterTools\SmarterMail\Service\SmarterTools.DNS.dll loaded at 0x74bb0000
C:\Windows\system32\rsaenh.dll loaded at 0xfcb40000
C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Runtime.Remo#\8bee5eaefcaba23cee113b869b7a5c9d\System.Runtime.Remoting.ni.dll loaded at 0xf1dc0000
C:\Program Files (x86)\SmarterTools\SmarterMail\Service\RemoteInterface.dll loaded at 0x74100000
C:\Program Files (x86)\SmarterTools\SmarterMail\Service\SmtpClient.dll loaded at 0x74860000
C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Web\27d67ef765046682a57eab06282829aa\System.Web.ni.dll loaded at 0xf2bb0000
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\webengine.dll loaded at 0xf5cd0000
C:\Windows\system32\rasapi32.dll loaded at 0xfb730000
C:\Windows\system32\winhttp.dll loaded at 0xfae90000
C:\Program Files (x86)\SmarterTools\SmarterMail\Service\DomainKeys.dll loaded at 0x741d0000
C:\Windows\system32\apphelp.dll loaded at 0xfd800000
C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Management\7b4a057b3d879caa88fe35def671061b\System.Management.ni.dll loaded at 0xee870000
C:\Windows\system32\cryptnet.dll loaded at 0xfb700000
[9/12/2017 10:45:33 PM]
C:\Windows\system32\SensApi.dll loaded at 0xfb9d0000
C:\Windows\system32\security.dll loaded at 0x73db0000
C:\Windows\system32\dssenh.dll loaded at 0xfb260000
C:\Windows\system32\ncrypt.dll loaded at 0xfcf70000
C:\Windows\system32\bcrypt.dll loaded at 0xfcf20000
C:\Windows\system32\GPAPI.dll loaded at 0xfcb00000
C:\Windows\system32\slc.dll loaded at 0xfd140000
C:\Program Files (x86)\SmarterTools\SmarterMail\Service\Nevron.System.dll loaded at 0x73540000
C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Drawing\54544452ca8d60a6092d2bcdd1394538\System.Drawing.ni.dll loaded at 0xedd60000
C:\Windows\system32\perfproc.dll loaded at 0xfb530000
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\wminet_utils.dll loaded at 0xf9c40000
C:\Windows\system32\wbem\wmiutils.dll loaded at 0xf6530000
C:\Windows\system32\wbemcomn.dll loaded at 0xf8bd0000
C:\Windows\system32\wbem\wbemprox.dll loaded at 0xf8140000
C:\Windows\system32\wbem\wbemsvc.dll loaded at 0xf6560000
C:\Windows\system32\wbem\fastprox.dll loaded at 0xf6590000
C:\Windows\system32\NTDSAPI.dll loaded at 0xfd2f0000
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\perfcounter.dll loaded at 0xfa140000
Thread created. New thread - System ID: 6568
Initializing control script
Clearing any existing breakpoints

Current Breakpoint List(BL)
[9/12/2017 10:45:34 PM]
Thread exited. Exiting thread - System ID: 6568. Exit code - 0x00000000
Thread created. New thread - System ID: 8400
[9/12/2017 10:45:51 PM]
Thread exited. Exiting thread - System ID: 8400. Exit code - 0x00000000
[9/12/2017 10:46:19 PM]
Thread exited. Exiting thread - System ID: 7520. Exit code - 0x00000000
[9/12/2017 10:46:37 PM]
Thread created. New thread - System ID: 7600
[9/12/2017 10:46:53 PM]
Thread created. New thread - System ID: 9164
[9/12/2017 10:46:57 PM]
Thread exited. Exiting thread - System ID: 7600. Exit code - 0x00000000
[9/12/2017 10:47:04 PM]
Thread created. New thread - System ID: 8076
[9/12/2017 10:47:08 PM]
Thread exited. Exiting thread - System ID: 9164. Exit code - 0x00000000
[9/12/2017 10:47:34 PM]
Thread exited. Exiting thread - System ID: 8076. Exit code - 0x00000000
[9/12/2017 10:47:43 PM]
Thread created. New thread - System ID: 6648
[9/12/2017 10:47:51 PM]
Thread created. New thread - System ID: 7968
[9/12/2017 10:48:00 PM]
Thread created. New thread - System ID: 8132
[9/12/2017 10:48:02 PM]
System.Exception on thread 8132. DetailID = 1
[9/12/2017 10:48:04 PM]
System.Byte[] on thread 8132. DetailID = 2
Thread exited. Exiting thread - System ID: 8132. Exit code - 0x00000000
[9/12/2017 10:48:06 PM]
Thread exited. Exiting thread - System ID: 7968. Exit code - 0x00000000
[9/12/2017 10:48:25 PM]
Thread exited. Exiting thread - System ID: 4336. Exit code - 0x00000000
[9/12/2017 10:48:26 PM]
Thread created. New thread - System ID: 7096
Thread created. New thread - System ID: 488
[9/12/2017 10:48:27 PM]
System.ObjectDisposedException on thread 7096. DetailID = 3
System.ObjectDisposedException on thread 2024. DetailID = 3
System.ObjectDisposedException on thread 488. DetailID = 3
System.ObjectDisposedException on thread 7096. DetailID = 4
System.ObjectDisposedException on thread 2024. DetailID = 4
System.ObjectDisposedException on thread 488. DetailID = 4
[9/12/2017 10:48:28 PM]
System.ObjectDisposedException on thread 2884. DetailID = 5
System.ObjectDisposedException on thread 6440. DetailID = 5
System.ObjectDisposedException on thread 4836. DetailID = 5
Thread created. New thread - System ID: 7216
System.ObjectDisposedException on thread 2884. DetailID = 6
System.ObjectDisposedException on thread 2884. DetailID = 7
System.ObjectDisposedException on thread 2884. DetailID = 7
System.ObjectDisposedException on thread 2884. DetailID = 7
System.ObjectDisposedException on thread 4836. DetailID = 7
System.ObjectDisposedException on thread 2884. DetailID = 7
System.ObjectDisposedException on thread 6440. DetailID = 7
Thread exited. Exiting thread - System ID: 8344. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 3548. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 7804. Exit code - 0x00000000
[9/12/2017 10:48:29 PM]
Thread exited. Exiting thread - System ID: 3860. Exit code - 0x00000000
[9/12/2017 10:48:30 PM]
Thread exited. Exiting thread - System ID: 7444. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 4420. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 5504. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 1752. Exit code - 0x00000000
[9/12/2017 10:48:38 PM]
Thread exited. Exiting thread - System ID: 6648. Exit code - 0x00000000
[9/12/2017 10:48:39 PM]
Thread exited. Exiting thread - System ID: 8900. Exit code - 0x00000000
[9/12/2017 10:48:40 PM]
C:\Windows\system32\perfproc.dll Unloaded from 0xfb530000
Thread exited. Exiting thread - System ID: 4152. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 2024. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 6036. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 5948. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 3404. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 6936. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 6024. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 3964. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 3084. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 2884. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 8672. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 4836. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 3388. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 6440. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 8032. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 8120. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 2300. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 7096. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 488. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 7216. Exit code - 0x00000000
Thread exited. Exiting thread - System ID: 8940. Exit code - 0x00000000
[9/12/2017 10:48:43 PM]
Process exited. Exit code - 0x00000000

***********************
* EXCEPTION DETAILS *
***********************

DetailID = 1
Count: 1
Type: System.Exception
Message: Spf check failed due to null sender's domain
Stack:
Module load completed but symbols could not be loaded for C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\0f7b33b7db5dd844076f0338e8541da6\mscorlib.ni.dll
RetAddr Call Site
SmarterTools.SmarterMail.MailStore.Spam1.SpamChecks.DoSPFCheck(System.String, System.String, System.String)
SmarterTools.SmarterMail.MailStore.Spam1.SpamChecks.RunChecks(System.String[], SmarterTools.SmarterMail.MailStore.Spam1.SpamCheckArgs)
SmarterTools.SmarterMail.RelayServer.SpamCheckSession.Check()
SmarterTools.SmarterMail.RelayServer.SpamCheckQueueWorkSession.DoSpamChecks()
SmarterTools.SmarterMail.RelayServer.SpamCheckQueueWorkSession.DoChecks()
System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
System.Threading.ThreadHelper.ThreadStart()

DetailID = 2
Count: 1
Type: System.Byte[]
Message: NOT_FOUND
Type: NOT_FOUND
Message: NOT_FOUND
Stack:
SmarterTools.DNS.DNSLib.DnsAnswer.Parse()
SmarterTools.DNS.DNSLib.DnsAnswer.get_Answers()
SmarterTools.DNS.DNSLib.DnsAnswer.GetTxtRecords()
SmarterTools.DNS.TXTLookupSmarterTools.GetTxtRecords(System.String)
SmarterTools.DNS.TXTLookup.Lookup(System.String)
SmarterTools.SmarterMail.DomainKeys.DNSEntry.buildFromDns(System.String, Boolean)
SmarterTools.SmarterMail.DomainKeys.MailAnalyzer.SignatureVerify(System.String ByRef)
SmarterTools.SmarterMail.MailStore.Spam1.SpamChecks.RunChecks(System.String[], SmarterTools.SmarterMail.MailStore.Spam1.SpamCheckArgs)
SmarterTools.SmarterMail.RelayServer.SpamCheckSession.Check()
SmarterTools.SmarterMail.RelayServer.SpamCheckQueueWorkSession.DoSpamChecks()
SmarterTools.SmarterMail.RelayServer.SpamCheckQueueWorkSession.DoChecks()
System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
System.Threading.ThreadHelper.ThreadStart()

DetailID = 3
Count: 3
Type: System.ObjectDisposedException
Message: Cannot access a disposed object.
Stack:
System.Net.Sockets.Socket.EndAccept(System.IAsyncResult)
TcpServerLib.Pooled.PooledTcpServer.AcceptConnection(System.IAsyncResult)
System.Net.LazyAsyncResult.Complete(IntPtr)
System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
System.Net.ContextAwareResult.Complete(IntPtr)
System.Net.LazyAsyncResult.ProtectedInvokeCallback(System.Object, IntPtr)
System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

DetailID = 4
Count: 3
Type: System.ObjectDisposedException
Message: Cannot access a disposed object.
Stack:
System.Net.Sockets.Socket.BeginAccept(System.Net.Sockets.Socket, Int32, System.AsyncCallback, System.Object)
System.Net.Sockets.Socket.BeginAccept(System.AsyncCallback, System.Object)
TcpServerLib.Pooled.PooledTcpServer.AcceptConnection(System.IAsyncResult)
TcpServerLib.Pooled.PooledTcpServer.AcceptConnection(System.IAsyncResult)
System.Net.LazyAsyncResult.Complete(IntPtr)
System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
System.Net.ContextAwareResult.Complete(IntPtr)
System.Net.LazyAsyncResult.ProtectedInvokeCallback(System.Object, IntPtr)
System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

DetailID = 5
Count: 3
Type: System.ObjectDisposedException
Message: Cannot access a disposed object.
Stack:
System.Net.Sockets.Socket.EndAccept(System.IAsyncResult)
TcpServerLib.Pooled.PooledTcpServer.AcceptConnection(System.IAsyncResult)
System.Net.LazyAsyncResult.Complete(IntPtr)
System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
System.Net.ContextAwareResult.Complete(IntPtr)
System.Net.LazyAsyncResult.ProtectedInvokeCallback(System.Object, IntPtr)
System.Net.Sockets.Socket.CompleteAcceptResults(System.Object)
System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(System.Threading._ThreadPoolWaitCallback)
System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(System.Object)

DetailID = 6
Count: 1
Type: System.ObjectDisposedException
Message: Cannot access a disposed object.
Stack:
System.Net.Sockets.Socket.BeginAccept(System.Net.Sockets.Socket, Int32, System.AsyncCallback, System.Object)
System.Net.Sockets.Socket.BeginAccept(System.AsyncCallback, System.Object)
TcpServerLib.Pooled.PooledTcpServer.AcceptConnection(System.IAsyncResult)
TcpServerLib.Pooled.PooledTcpServer.AcceptConnection(System.IAsyncResult)
System.Net.LazyAsyncResult.Complete(IntPtr)
System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
System.Net.ContextAwareResult.Complete(IntPtr)
System.Net.LazyAsyncResult.ProtectedInvokeCallback(System.Object, IntPtr)
System.Net.Sockets.Socket.CompleteAcceptResults(System.Object)
System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(System.Threading._ThreadPoolWaitCallback)
System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(System.Object)

DetailID = 7
Count: 6
Type: System.ObjectDisposedException
Message: Cannot access a disposed object.
Stack:
(omitted)

***********************
* EXCEPTION SUMMARY *
***********************

|----------------------------------------|
| Count | Exception |
|----------------------------------------|
| 16 | System.ObjectDisposedException |
| 1 | System.Byte[] |
| 1 | System.Exception |
|----------------------------------------|

**** Some exception details were omitted due to the following reasons
The maximum number of stacks (MAX_CLR_EXCEPTION_STACKS_PER_EXCEPTION_TYPE = 10) for this CLR exception type have been collected: 'System.ObjectDisposedException'

Debugging Overhead Cost:
Total Elapsed Ticks = 194969 (100%)
Total Ticks Spent in Debugger Engine = 2766 (1%)
Total Ticks Spent in Crash Rule Script = 6313 (3%)
0
Von-Austin See Replied
Employee Post
Astrailis, the exceptions you posted do not appear to be critical. I would suggest opening up a support ticket so we can verify the behavior you're encountering within SmarterMail and compare it to the crash dumps you have obtained if you're running into any issues with Smartermail's stability.
Von See
Technical Support Supervisor
SmarterTools Inc.
(877) 357-6278
www.smartertools.com

Reply to Thread