When using ServiceControl Management Utility on a network with limited outbound network access, this error will occur every time the tool is started. This was reported by a customer.
System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 52.216.143.182:443
at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
This is due to the update check code which is not wrapped with a try…catch. There is currently no way to disable this check.
This is poor user experience. The exception should be caught and, at worst, a non-blocking alert (i.e. a red label, not a modal dialog) should notify the user that the update check could not be performed because the network host could not be reached. That way the user is still given a hint to help them keep ServiceControl up to date without an in-your-face error every time the tool is launched.
When using ServiceControl Management Utility on a network with limited outbound network access, this error will occur every time the tool is started. This was reported by a customer.
This is due to the update check code which is not wrapped with a try…catch. There is currently no way to disable this check.
This is poor user experience. The exception should be caught and, at worst, a non-blocking alert (i.e. a red label, not a modal dialog) should notify the user that the update check could not be performed because the network host could not be reached. That way the user is still given a hint to help them keep ServiceControl up to date without an in-your-face error every time the tool is launched.