Hi,
We have encountered some triggers being deactivated due to a connection issue. This was during our monthly Windows patching. Initially VisualCron appears to be retrying the attempts as expected, however further down the line the connection fails and trigger is disabled (it does not state attempt 10/10). Could you advise why this occurred so we can mitigate it going forward?

Here are the appropriate sections of the log including the stack trace:

9/29/2019 6:00:56 PM Err Could not connect to net.tcp://MACHINE1/. The connection attempt lasted for a time span of 00:00:09.0056781. TCP error code 10061: No connection could be made because the target machine actively refused it 10.1.21.131:16444.
9/29/2019 6:01:06 PM Info Retrying to connect (retries left: 2 out of 10)

___________________________________________________________________________________________________

9/29/2019 8:21:09 PM Err API->ConnectionError: Failed to connect to server.
9/29/2019 8:21:09 PM Err Trigger error: Connection to VisualCron server failed in Trigger connected to Job 'ServerUnitTest 3', error: System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://MACHINE1/. The connection attempt lasted for a time span of 00:00:01.0322377. TCP error code 10061: No connection could be made because the target machine actively refused it 10.1.21.131:16444. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.1.21.131:16444
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
--- End of inner exception stack trace ---

Server stack trace:
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

Exception rethrown at [0]:
at VisualCronAPI.Client.Connect(Connection conn, Boolean SynchronizeServerObjects, Boolean bolInternal) in C:\git\code\VisualCronAPI\Client\Client.vb:line 1058
at VisualCronService.EventVisualCron.StartWatcher() in C:\git\code\VisualCronService\Triggers\Events\VisualCron\clsEventVisualCron.vb:line 228
9/29/2019 8:21:09 PM Debug Trigger was expired and inactivated

Have you checked the Event log on the target server?

This line looks a little strange:
9/29/2019 6:00:31 PM Debug ConnectionManager_ConnectionRemoved->Connection removed (Server Event): uuid:c47e0fa7-84f1-4cbc-a8ef-10b31a35d6d0;id=1

Other than that I can only see this occurrence that might influence it:
9/29/2019 8:20:07 PM Info JobAPI->Save->Saving Jobs (25) - in shut down: True

Could it be that the target machine was shutting down and so the connection was denied?

Continuing this troubleshooting via email.

---