We've been having a couple issues with the visualcron process crashing and users getting disconnected or jobs failing.
It looks like event ID 1026 is logged with two variations.

There haven't been able to find any jobs that are always failing or that seem to be causing the service to crash.

Users get disconnected with this is logged:
Application: VisualCronService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at SBSimpleSSH.TElSimpleSSHClient.GetActive()
at SBSimpleSSH.TElSimpleSSHClient.get_Active()
at VisualCronService.ConnectionHandlerClass.SendKeepAlive(System.Object)
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.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()


Jobs fail when this is logged:
Application: SSISDBExecute.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ServiceModel.CommunicationObjectFaultedException

Server stack trace:
at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposedOrNotOpen()
at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessage)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(System.Runtime.Remoting.Proxies.MessageData ByRef, Int32)
at VisualCron.ITaskService.ProcessTaskResult(Int32, VisualCron.ProcessTaskResult)
at SSISDBExecute.Main.Main(System.String[])

Hi,

it can be solved two ways:

1. Set Keep Alive on the SFTP/SSH Connection to 0
2. upgrade to the latest version

---

All of our SSH connections already have keep alive set to 0 in the extra settings section. Do we also need to check the box for 'SendKeepAlive every' inside each job and set that to 0?

I've attached a screenshot of that setting.

Please upgrade to the latest. This has been resolved.

---

We've scheduled the upgrade for tomorrow morning. Should have an idea of whether that addresses the issue by Monday or Tuesday.

We are seeing the following error. Restarting the service at the OS level did solve the issue somewhat, but we would like to not have the issue.
We are using 8.3.4 currently

Unhandled Exception: System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

Server stack trace:
at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposedOrNotOpen()
at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at VisualCron.ITaskService.ProcessLog(Int32 VCTaskPId, String strExecutable, Boolean bolIsError, String strMessage)
at e7SGddj42tSYNVkxTd.QuKmifVsqyvSQLHd2b.st5XnK06u(Boolean , String )
at NETExecute40.ProcessTaskService.CreateService(String uniqueAddress)
at e7SGddj42tSYNVkxTd.QuKmifVsqyvSQLHd2b.eZYq7lgQG(String[] )
Exception in Task: Non zero exit code
Exception in Task: Non zero exit code

Hi,

this seems related to the .NET Execute Task. Can you reproduce this with that Task? Does it crash the whole service?

We are seeing the following error. Restarting the service at the OS level did solve the issue somewhat, but we would like to not have the issue.
We are using 8.3.4 currently

Unhandled Exception: System.ServiceModel.CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

Server stack trace:
at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposedOrNotOpen()
at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at VisualCron.ITaskService.ProcessLog(Int32 VCTaskPId, String strExecutable, Boolean bolIsError, String strMessage)
at e7SGddj42tSYNVkxTd.QuKmifVsqyvSQLHd2b.st5XnK06u(Boolean , String )
at NETExecute40.ProcessTaskService.CreateService(String uniqueAddress)
at e7SGddj42tSYNVkxTd.QuKmifVsqyvSQLHd2b.eZYq7lgQG(String[] )
Exception in Task: Non zero exit code
Exception in Task: Non zero exit code

---

Yes this occurred on a job with a Execute Task. Other jobs with only SQL tasks were not effected.

For the job(s) that have the Execute Task they failed consistently until we restarted the service. I suspect something with the server and domain controller where something is expired and Visual Cron doesn't see that.