We've been using VC for 2 years now without an issue. As soon as we upgraded to 8.2.3, the service crashes every day at the same time.javascript:insertsmiley('🤬 ','/Images/Emoticons/msp_cursing.gif')
In the Windows server event viewer, I've typically seen the following series or events:
JobAPI->Save->Saving Jobs (158) - in shut down: False
Then:
Application: VisualCronService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at VisualCronService.ConnectionHandlerClass.DEFEEIBMCGKIAODKPFIAKCDLAAPGIHPCPKJL()
at VisualCronService.ConnectionHandlerClass.GPJOGLCMJEILAIECEIHKANLKGEFMADHEEANG(System.Object)
at SBSimpleSftp.TElSimpleSFTPClient.DoCloseConnection(System.Object)
at SBSSHCommon.TElSSHClass.DoCloseConnection()
at SBSSHClient.TElSSHClient.SSH2ParseServerDisconnect(Byte[], Int32)
at SBSSHClient.TElSSHClient.SSH2ParseOnTransportLayer(Byte[], Int32)
at SBSSHClient.TElSSHClient.AnalyseBuffer()
at SBSSHClient.TElSSHClient.DataAvailable()
at SBSimpleSftp.TElSimpleSFTPClient.DataAvailable()
at SBSimpleSftp.TElSimpleSFTPClient.DoMessageLoop()
at SBSimpleSftp.TElSimpleSFTPClient.HandleSftpMessageLoop()
at SBSftpCommon.TSBSftpMessageLoopEvent.Invoke()
at SBSftp.TElSftpClient.RequestAbsolutePath(System.String)
at SBSftp.TElSftpClient.RequestAbsolutePathSync(System.String)
at SBSimpleSftp.TElSimpleSFTPClient.RequestAbsolutePath(System.String)
at SBSimpleSftp.TElSimpleSFTPClient.DoSendKeepAlive(System.Object)
at SBTimer.TElTimer.HandleTimerEvent(System.Object)
at SBTimer.TTimerThread.DoTimer()
at SBTimer.TTimerThread.Execute()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()
Then:
Faulting application name: VisualCronService.exe, version: 8.2.3.36558, time stamp: 0x58543e10
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff8322d7f31
Faulting process id: 0x25ec
Faulting application start time: 0x01d286cc72c47023
Faulting application path: C:\Program Files (x86)\VisualCron\VisualCronService.exe
Faulting module path: unknown
Report Id: dfe28d8e-f43f-11e6-80fa-00155d503508
Faulting package full name:
Faulting package-relative application ID:
And the service shuts off. We've since changed the service to recover by having Windows restart it. I'm trying to figure out the root cause so we don't have to worry about a possible recovery scenario. Are there any internal settings to check to identify why it's breaking at the same time? Or some possible combinations of server settings that could conflict?
Thanks.