
ScreenConnect 20.1.26625.7338_Debug Services crash with ASP errors
After upgrading from 19.1 release version to the new 20.1 debug version, the services won't stay running and crash with the following in the event viewer:
Faulting application name: ScreenConnect.Service.exe, version: 20.1.26625.7338, time stamp: 0xae238f10
Faulting module name: KERNELBASE.dll, version: 6.1.7601.24545, time stamp: 0x5e0eb6bd
Exception code: 0xe0434352
Fault offset: 0x000000000000b87d
Faulting process id: 0x1160
Faulting application start time: 0x01d5dc91ef4a2e55
Faulting application path: C:\Program Files (x86)\ScreenConnect\Bin\ScreenConnect.Service.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 37d738bb-4885-11ea-a4fd-005056b0cd40
Application: ScreenConnect.Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.TimeoutException
Server stack trace:
at ScreenConnect.ObjectPool`1.BorrowEntry()
at ScreenConnect.ObjectPool`1.DemuxProxy.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 ScreenConnect.ISessionManager.CreateSession(System.Guid, System.String, System.String[])
at ScreenConnect.ProcessHandshakeMessagesAction.ProcessInitiateSessionMessage(ScreenConnect.Relay, ScreenConnect.InitiateSessionMessage, ScreenConnect.ActionBase ByRef)
at ScreenConnect.ProcessHandshakeMessagesAction.ProcessHandshakeMessage(ScreenConnect.Relay, System.Object, ScreenConnect.ActionBase ByRef)
at ScreenConnect.ProcessHandshakeMessagesAction.Run(ScreenConnect.Relay)
at ScreenConnect.ActionThreadPool.Run()
at ScreenConnect.ThreadPool.RunThread(System.Object)
at ScreenConnect.Extensions+<>c__DisplayClass332_0`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].b__2(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.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart(System.Object)
An unhandled exception occurred and the process was terminated.
Application ID: Relay-0002
Process ID: 4448
Exception: System.TimeoutException
Message: The operation has timed out.
StackTrace:
Server stack trace:
at ScreenConnect.ObjectPool`1.BorrowEntry() in C:\Build\builds\74a5e79d\0\cwcontrol\cwcontrol\Product\Server\ObjectPool.cs:line 55
at ScreenConnect.ObjectPool`1.DemuxProxy.Invoke(IMessage message) in C:\Build\builds\74a5e79d\0\cwcontrol\cwcontrol\Product\Server\ObjectPool.cs:line 264
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 ScreenConnect.ISessionManager.CreateSession(Guid sessionID, String name, String[] customPropertyValues)
at ScreenConnect.ProcessHandshakeMessagesAction.ProcessInitiateSessionMessage(Relay relay, InitiateSessionMessage initiateSessionMessage, ActionBase& endOfHandshakeAction) in C:\Build\builds\74a5e79d\0\cwcontrol\cwcontrol\Product\Relay\Actions.cs:line 457
at ScreenConnect.ProcessHandshakeMessagesAction.ProcessHandshakeMessage(Relay relay, Object message, ActionBase& endOfHandshakeAction) in C:\Build\builds\74a5e79d\0\cwcontrol\cwcontrol\Product\Relay\Actions.cs:line 431
at ScreenConnect.ProcessHandshakeMessagesAction.Run(Relay relay) in C:\Build\builds\74a5e79d\0\cwcontrol\cwcontrol\Product\Relay\Actions.cs:line 356
at ScreenConnect.ActionThreadPool.Run() in C:\Build\builds\74a5e79d\0\cwcontrol\cwcontrol\Product\Relay\ThreadPool.cs:line 154
at ScreenConnect.ThreadPool.RunThread(Object state) in C:\Build\builds\74a5e79d\0\cwcontrol\cwcontrol\Product\Relay\ThreadPool.cs:line 51
at ScreenConnect.Extensions.<>c__DisplayClass332_0`1.b__2(Object ) in C:\Build\builds\74a5e79d\0\cwcontrol\cwcontrol\Product\Core\Extensions.cs:line 2979
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.Threading.ThreadHelper.ThreadStart(Object obj)
Customer support service by UserEcho
Rolled back my server and updated to ScreenConnect_19.6.26659.7340_Release followed by updating to ScreenConnect_20.1.26774.7346_Debug when it became available and the upgrade was fine and the services remained running. It appears the issue was squashed with one of the 20.1 debug updates.
-William
I let a nasty bug slip by, but the affected installers have been taken down.
Thanks for the help. please note that since 20.1, adding a new client with a customproperty2 isn't being properly added to the support group based on customproperty2.
-William
If you're talking about subgroups, that bug is still a work in progress.
That's the one thanks! I'll await a fix. :)