Welcome to the ConnectWise Control Bug Report Portal
If you do not have an account, click "Sign in/ Sign up" to get started.
- Search for an existing bug report before adding your own. This helps us prevent duplicate entries and improve bug tracking.
- If you find a matching bug report, give it a thumbs up and throw in a comment with more details about the problem.
- If you can't find a request for an item you need, create your own bug report. Provide as many details as you can, especially:
- Software version of the server, host client, and guest client
- Operating systems affected
- Any error messages
- No spam, advertising, or self-promotion.
- No offensive posts, links, or images.
- Only one request per post.
- Administrators have the ability to moderate the forums, including editing, deleting, and moving posts. Posts may be deleted for any reason, with or without notification.
Thank you for sharing your thoughts with us!
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
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.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.Extensions+<>c__DisplayClass332_0`1[[System.__Canon, mscorlib, Version=220.127.116.11, 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)
An unhandled exception occurred and the process was terminated.
Application ID: Relay-0002
Process ID: 4448
Message: The operation has timed out.
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 :
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)
Since upgrade to 19.5 when i open a client session the session Window is tiny and i have to resize it larger to make it usable. When i close the session and re-open it opens tiny again, it does this no matter what computer i click on and start a session. Nothing has changed on my computer. Wasn't doing this before upgrade to 19.5
I updated my cloud instance to 19.6.26188.7290.
On the Configuration page, when I click on any of the four links under 'Web Configuration', I get the following error message: "Object reference not set to an instance of an object."
This isn't the case with the links under 'Application Configuration' or 'Disable Host Client Menu Items'. They're working just fine.
The blue dot to indicate a waiting chat / message notification does not clear even after the messaging window is accessed. This worked correctly up until 19.0
We added a delay to the clearing, which defaults to 10 minutes.
We'll have updates to the Advanced Configuration Editor and Edit Web.config AppSettings extensions shortly, but if you're on-prem and don't want to wait, look for AcknowledgeMessageDelaySeconds in web.config.
|Not sure if it affects mac's as a whole but the cases I have seen it is on MacBook pros.
There is a constant pop up message of 'Operation 'RebootReconnectMessage' Not supported'
this appears with no prompt from the user
the feature does work as I am able to reboot the mac from the remote session control panel
the pop up continues to arise after the service is forced to quit as the service then automatically starts up again
When first remoting into a system, it does not recognize the status of your keyboard's caps lock. Thus, the Caps lock on the remote system may be inverted.
For example, if I remote into a system with my CAPS on (and that system, the caps is off), it does not recognize that my caps is on.
When I try to upgrade 19.4.25759.7247 to 19.6.26659.7340 on a CentOS 7 server , screenconnect web interface fails to start with this error in the log :
Event (2020/02/12 23:10:10.445 +02:00, ScreenConnect Web Server, Information): Starting service...
mono_w32socket_convert_error: no translation into winsock error for (126) "Required key not available"
Tryied removing all extensions , restarting the server , same error
If a scrolling action is occurring (via holding down left mouse button) and the mouse cursor moves outside of the host client window, the session locks up. It becomes unresponsive (as though the entire client window has lost focus) until the window receives a mouse click to bring back "focus", at which point normal interaction can then resume. This can be quite annoying especially since the scroll bar in a full screen window will always be right at the very edge of the client window making it difficult to not move the cursor out of the client window.
In addition, when the cursor leaves the client window while scrolling a "generic" icon appears in the task bar coinciding with the unresponsiveness, and this icon disappears when the window receives a mouse click that restores normal behavior.
This occurs in v6.6.18120.6697 (as well as all previous versions going back at least several years). I'm happy to provide any additional information requested.
Customer support service by UserEcho