First a "shout out" to Steven Dove from ScreenConnect Support in Florida. He pointed me in the direction of this post in order to solve an issue I had brought to his attention. He was very helpful and was willing to spend the time necessary to assist with implementing this resolution in our environment. Great customer service... made me feel like the success of our business is important to the team at ScreenConnect!
Anyway, we ran into an issue this past weekend where all of the ScreenConnect services (including the new ScreenConnect Router service) terminated unexpectedly and did not restart. Thus... nothing was able to reach our ScreenConnect until the services were restarted.
After poking around through the Event Logs it appeared that the cause of the services shutdown was related to the ScreenConnect Router service. I contacted Steven through our earlier ticket to request assistance.
It turns out that Steven experienced the same thing on one of his "test" systems within a 1/2 hour of when our installation shut down:
Quote:Thanks for the reply. Looking at the server I setup, I had the same thing happen this weekend about 20 minutes before yours. I'm going to create a new ticket and send that up to our development team to get more insight on what might have caused the problem. Please let us know if it happens again!
So... since this hidden feature was introduced here on the forum, the development team asked that I post the issue on the forum in order that it might be supported. Ok... no problem, here goes:
Anyway, this past Sunday morning I was unable to connect to our ScreenConnect portal. So, I logged into the ScreenConnect server and found that all of the ScreenConnect services were not running. It appears as if they were all terminated at 4:51am…
Here is a screenshot of an applicable section of the Application log from Event Viewer:

Event 1325 mentions a problem that contains the “Elsinore.ScreenConnect.Router”...
Quote:Log Name: Application
Source: ASP.NET 4.0.30319.0
Date: 4/19/2015 4:51:30 AM
Event ID: 1325
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SCREENCONNECT
Description:
The description for Event ID 1325 from source ASP.NET 4.0.30319.0 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
An unhandled exception occurred and the process was terminated.
Application ID: ConfigurationRouter-0003
Process ID: 1304
Exception: System.UriFormatException
Message: Invalid URI: The hostname could not be parsed.
StackTrace: at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
at System.Uri..ctor(String uriString)
at System.UriBuilder.get_Uri()
at Elsinore.ScreenConnect.Router.HttpHandshakeProcessor.ProcessHandshakeData(IPEndPoint localEndPoint, IPEndPoint remoteEndPoint, ArraySegment`1 mutableHandshakeData)
at Elsinore.ScreenConnect.Router.<>c__DisplayClass1d.<ProcessHandshakeAsync>b__1a(HandshakeProcessor hp)
at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source)
at Elsinore.ScreenConnect.Router.ProcessHandshakeAsync(IPEndPoint localEndPoint, IPEndPoint remoteEndPoint, ArraySegment`1 mutableHandshakeData, Proc`2 proc)
at Elsinore.ScreenConnect.Router.<>c__DisplayClass24.<ProcessAcceptedSocket>b__20()
at Elsinore.ScreenConnect.SocketAsyncExecutor.<.ctor>b__0(Object , SocketAsyncEventArgs )
at System.Net.Sockets.SocketAsyncEventArgs.OnCompleted(SocketAsyncEventArgs e)
at System.Net.Sockets.SocketAsyncEventArgs.ExecutionCallback(Object ignored)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.Sockets.SocketAsyncEventArgs.FinishOperationSuccess(SocketError socketError, Int32 bytesTransferred, SocketFlags flags)
at System.Net.Sockets.SocketAsyncEventArgs.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
Also, the System log shows:
So, since it looks like the shutdown of our SC services may have had something to do with the ScreenConnect Router service I have attached the details of the above events in two .txt files in the reply to the ticket that Steven worked on for your viewing pleasure… It should be on file in the SC ticketing system.
This is the first time that this has happened, but… I just want to make sure that if something is misconfigured or there is a glitch in the “router” that we are able to resolve it so that it doesn’t happen again.
Let me know if you need any further info. Thanks for your help!