0

20.2.29488 System.ServiceModel.FaultException

Ben Delville 3 weeks ago updated 1 week 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

Hey all,

We're aware of this issue and have something registered internally for it. One of our engineers determined a way to set up better logging and it would help us if you could do the following and report back the stack traces you see if you encounter this error again:

Under the <system.serviceModel> tag in the web.config, add the following:

<behaviors>
  <serviceBehaviors>
    <behavior name="debug">
      <serviceDebug includeExceptionDetailInFaults="true" />
    </behavior>
  </serviceBehaviors>
</behaviors>

I.e, your web.config's system.serviceModel section should look similar to this:

<system.serviceModel>
  ...other stuff
  <behaviors>
    <serviceBehaviors>
      <behavior name="debug">
        <serviceDebug includeExceptionDetailInFaults="true" />
      </behavior>
    </serviceBehaviors>
  </behaviors>
</system.serviceModel>

Next, find <service name="ScreenConnect.SessionManager"> and change it to <service name="ScreenConnect.SessionManager" behaviorConfiguration="debug">.

Finally, start the service in debug mode by running "sudo /etc/init.d/screenconnect debug > ~/Desktop/monoDebugLogs.txt 2>&1". You don't need to stop the service explicitly before this.

Thanks Timmothy. Just went to add this, but CreenConnect is acting up, again. Will have to wait and do it next weekend as this is so time consuming each time it goes down daily.