Hello Marijn,
I see that you've also sent in an email to support, where you mention an error does occur :
"Exception Type: System.Data.SqlClient.SqlException
Errors:
System.Data.SqlClient.SqlErrorCollection
Class: 11
LineNumber:
0
Number: -2
Procedure:
Server: XXXX\SQLSERVER2005
State:
0
Source: .Net SqlClient Data Provider
ErrorCode: -2146232060
Message:
Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding.
Data:
System.Collections.ListDictionaryInternal
TargetSite: Void
OnError(System.Data.SqlClient.SqlException, Boolean)
HelpLink: NULL"
To me, it appears as if this server is losing it's connection to your SQL database on your SQL server, and the Email Services aren't starting up again on there own. The temporary loss of connectivity to the SQL Server can be caused by a variety of things, which I'll leave to you to explore, but I may have a way to make sure you OnTime Services keep checking for new mail.
There is a way to tell Windows to restart the Services if they stop due to loss of connectivity to the SQL database.
First, from the server the Services reside on, go to "Start>Programs>Control Panel>Administrative Tools>Services". Find the 3 OnTime Services, right-click on one of them, and select 'Properties'. From the Properties window, select the "Recovery" tab.
From here you can select actions for Windows to take when the service fails. You'll see you can select "Restart the Service" instead of "Take No Action" for the first, second, and subsequent failures. You can also configure how many minutes to wait after a failure for the Service to restart.
Repeat for the other 2 OnTime Services, and you should be okay from now on if the Service fails.
Let me know if you have any further questions, or if that doesn't resolve your issue.
Thank you,
Tom Harder
Axosoft Support
support@axosoft.com1.800.653.0024 option 3--'Fear the Bug' Podcast--