Welcome to the ConnectWise Control for Linux  Bug Report Portal

If you do not have an account, click "Sign in/ Sign up" to get started.

Tips

  • 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
    • Screenshots

Rules

  • 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!

+4
Under review

Portal still not responding.

Joshua Zukerman 2 weeks ago 0

Still having the same issue of the portal becoming unresponsive after random periods of uptime. Running version 20.2.29488.7519 on CentOS 6.10 virtual machine, 1 vCPU, 2GB RAM. When the server is running, it is slightly faster, though that may be due to unloading more than half of the clients to a new Windows VM in Azure. I'm keeping this server around due to many offline agents (computers) that don't get powered on frequently. That way I can point them to my new server without having to manually reinstall the client agent.

+1
Under review

XmlDictionaryString ID 13 not defined in the XmlBinaryReaderSession.

Craig Gauss 2 weeks ago updated by J Copeland 3 days ago 2

Got the following upon opening the Control webpage
XmlDictionaryString ID 13 not defined in the XmlBinaryReaderSession.

Error goes away and allows login

Linux version: 20.1.29489.7513

Checked /var/log/screenconnect and nothing was recorded

0

20.2.29488 System.ServiceModel.FaultException

Ben Delville 3 weeks ago updated 2 weeks ago 3

Hi,

Since updating to 20.2.29488 we are experiencing random crashes with the following error:

System.ServiceModel.FaultException: The server was unable to process the request due to an internal error. The server may be able to return exception details (it depends on the server settings). Server stack trace: at System.ServiceModel.MonoInternal.ClientRuntimeChannel.Request (System.ServiceModel.Description.OperationDescription od, System.Boolean isAsync, System.Object[]& parameters, System.ServiceModel.OperationContext context) [0x001e5] in <4b4bc0a3fb7543a5835bd657df724b87>:0 at System.ServiceModel.MonoInternal.ClientRuntimeChannel.DoProcess (System.Reflection.MethodBase method, System.String operationName, System.Boolean isAsync, System.Object[]& parameters, System.ServiceModel.OperationContext context) [0x00031] in <4b4bc0a3fb7543a5835bd657df724b87>:0 at System.ServiceModel.MonoInternal.ClientRuntimeChannel.Process (System.Reflection.MethodBase method, System.String operationName, System.Boolean isAsync, System.Object[]& parameters, System.ServiceModel.OperationContext context) [0x0001e] in <4b4bc0a3fb7543a5835bd657df724b87>:0 at System.ServiceModel.MonoInternal.ClientRuntimeChannel.Process (System.Reflection.MethodBase method, System.String operationName, System.Object[] parameters, System.ServiceModel.OperationContext context) [0x00002] in <4b4bc0a3fb7543a5835bd657df724b87>:0 at System.ServiceModel.ClientRealProxy.DoInvoke (System.Runtime.Remoting.Messaging.IMessage inputMessage) [0x000d5] in <4b4bc0a3fb7543a5835bd657df724b87>:0 at System.ServiceModel.ClientRealProxy.Invoke (System.Runtime.Remoting.Messaging.IMessage inputMessage) [0x00000] in <4b4bc0a3fb7543a5835bd657df724b87>:0 at ScreenConnect.ObjectPool`1[T].InvokeOnInnerProxy (ScreenConnect.ObjectPool`1+Entry[T] entry, System.Runtime.Remoting.Messaging.IMessage message) [0x00004] in <699690eea31b4cd98b738c7766c94592>:0 Exception rethrown at [0]: at (wrapper managed-to-native) System.Object.__icall_wrapper_mono_remoting_wrapper(intptr,intptr) at (wrapper remoting-invoke) ScreenConnect.ISessionManager.GetRootSessionGroupSummaries(ScreenConnect.SessionType,System.Collections.Generic.ICollection`1,System.Collections.Generic.ICollection`1,System.Collections.Generic.Dictionary`2) at ScreenConnect.PageService.GetHostSessionInfo (ScreenConnect.SessionType sessionType, System.String[] sessionGroupPath, System.String filter, System.Nullable`1[T] findSessionID, System.Int32 sessionLimit, System.Int64 version) [0x0020e] in <88d20b90d6504f27b37d03c1e983ee6d>:0 Exception rethrown at [1]: at ScreenConnect.Extensions.PerformUnwrappingInnerException[T] (ScreenConnect.Func`1[TResult] func) [0x00032] in :0 at ScreenConnect.WebServiceReflector+TaskWebMethod.EndInvoke (System.IAsyncResult result) [0x0000e] in <5db6835248974db98c711b0a5f61fe90>:0 at ScreenConnect.WebServiceBase+<>c__DisplayClass22_0.b__3 (System.IAsyncResult _) [0x0000b] in <5db6835248974db98c711b0a5f61fe90>:0 at ScreenConnect.AsyncResult`1+<>c__DisplayClass43_0[T].b__0 (System.IAsyncResult innerResult) [0x00002] in :0 Exception rethrown at [2]: at ScreenConnect.AsyncResult`1[T].End () [0x00062] in :0 at ScreenConnect.WebServiceBase.System.Web.IHttpAsyncHandler.EndProcessRequest (System.IAsyncResult result) [0x000a8] in <5db6835248974db98c711b0a5f61fe90>:0

0
Under review

Sticky key stuck on the guest machine

Moises Gerevini 4 weeks ago 0

Summary: Sticky key stuck on the guest machine

Description: When the guest starts to use the machine, the machine behaves as if some keys were already pressed.