+1
Waiting for information

Unhandled exception

DaMtechMatt 3 years ago updated by Ben Burner 3 years ago 4

I have started to recieve popups telling me an Unhandled exception has occurred.




ConnectWise Control Version:
19.1
Server Affected:
Host Client Affected:
Guest Client Affected:

I've taken a copy of the details:


See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.



************** Exception Text **************
System.InvalidOperationException: Operation is not valid due to the current state of the object.



Server stack trace:
at ScreenConnect.Extensions.First2[T](IEnumerable`1 items, Predicate`1 predicate)
at ScreenConnect.HelperControlPanel.UpdateHelperText(String text)
at ScreenConnect.Client.UpdateHelperText(String query)
at ScreenConnect.Client.<>c__DisplayClass192_1.<ScreenConnect.IMessageProcessor<System.Object>.ProcessMessage>b__1()
at ScreenConnect.WindowsClientExtensions.<>c__DisplayClass99_0.<Post>b__0(Object <state>)



Exception rethrown at [0]:
at ScreenConnect.WindowsClientExtensions.<>c__DisplayClass99_0.<Post>b__0(Object <state>)




************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1637.0 built by: NETFXREL3STAGE
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
ScreenConnect.WindowsClient
Assembly Version: 6.1.12292.6236
Win32 Version: 6.1.12292.6236
CodeBase: file:///C:/Program%20Files%20(x86)/ScreenConnect%20Client%20(d350397927d233f3)/ScreenConnect.WindowsClient.exe
----------------------------------------
ScreenConnect.Core
Assembly Version: 6.1.12292.6236
Win32 Version: 6.1.12292.6236
CodeBase: file:///C:/Program%20Files%20(x86)/ScreenConnect%20Client%20(d350397927d233f3)/ScreenConnect.Core.DLL
----------------------------------------
ScreenConnect.Windows
Assembly Version: 6.1.12292.6236
Win32 Version: 6.1.12292.6236
CodeBase: file:///C:/Program%20Files%20(x86)/ScreenConnect%20Client%20(d350397927d233f3)/ScreenConnect.Windows.DLL
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1637.0 built by: NETFXREL3STAGE
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
ScreenConnect.Client
Assembly Version: 6.1.12292.6236
Win32 Version: 6.1.12292.6236
CodeBase: file:///C:/Program%20Files%20(x86)/ScreenConnect%20Client%20(d350397927d233f3)/ScreenConnect.Client.DLL
----------------------------------------
System.Deployment
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Deployment/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1638.0 built by: NETFXREL3STAGE
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------



************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.



For example:



<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>



When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


Waiting for information

Good afternoon,


Thank you for reporting this information.


Would you mind providing some additional information to facilitate our attempt to reproduce this behavior:


1) Can you confirm you're seeing this error on your machine when you join a session as a host?

2) What is the host (your) machine's operating system?

3) What is the guest machine's operating system (the machine you're connecting to)?

4) Does the host client crash immediately after joining the session?

5) Around the time the client crashes, is it possible that you or the local user on the guest machine is copying text on the guest machine?


Regards,

Ben

Hi

Unfortunatly I wasn’t at the machine when the error appeared.

It’s a Windows 10 Machine. 64bit

There was no session connected at the time.

Is there a log file I can get for you?

Matt

Good morning,


Thank you for providing an update.


One more question: are there multiple language packs installed on the Windows 10 machine that encountered the error?


Cheers,

Ben