 Rank: Newbie Medals:  Joined: 3/17/2015(UTC) Posts: 10  Thanks: 4 times Was thanked: 1 time(s) in 1 post(s)
|
Using self-hosted version 6.5.16479.6613. I've upgrade nearly all clients to current release and they are working fine. Just upgraded one Windows 10 client that had been offline and now it repeatedly pops up an error in Windows that "ScreenConnect Client has stopped working". You can close the window and you never actually lose connection (although features are limited), but within one to to two minutes, the error is back. The Windows application log shows the errors below. I thought this was a one-off, but recently had to do a support session and after the user installed the client, I had the same behavior. With the Access client, I have peformed a remote reinstall with no change.
Log Name: Application Source: .NET Runtime Date: 3/28/2018 8:28:03 AM Event ID: 1026 Task Category: None Level: Error Keywords: Classic User: N/A Computer: DESK-026.x.x Description: Application: ScreenConnect.WindowsClient.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.FormatException
and
Log Name: Application Source: Application Error Date: 3/28/2018 8:28:04 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: DESK-026.x.x Description: Faulting application name: ScreenConnect.WindowsClient.exe, version: 6.5.16479.6613, time stamp: 0x5a7cb45f Faulting module name: KERNELBASE.dll, version: 10.0.16299.309, time stamp: 0x90a96867 Exception code: 0xe0434352 Fault offset: 0x0000000000014008 Faulting process id: 0xc08 Faulting application start time: 0x01d3c69037936fa4 Faulting application path: C:\Program Files (x86)\ScreenConnect Client (a03747be52c5030b)\ScreenConnect.WindowsClient.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 8596d6e5-401e-4ca7-99df-225d80b2abc5
|
|
|
|
 Rank: Advanced Member Medals:  Joined: 2/6/2014(UTC) Posts: 314   Thanks: 7 times Was thanked: 31 time(s) in 28 post(s)
|
|
|
|
|
 Rank: Newbie Medals:  Joined: 3/17/2015(UTC) Posts: 10  Thanks: 4 times Was thanked: 1 time(s) in 1 post(s)
|
Interesting. I wouldn't think it would be a disk error, especially on two different machines, but I ran the chkdsk command above on one with no effect. Still getting the error but only on some clients.
|
|
|
|
 Rank: Administration Medals:  Joined: 3/28/2014(UTC) Posts: 2,844  Thanks: 3 times Was thanked: 348 time(s) in 300 post(s)
|
Is there any other information within the Application log in the Event Viewer? Perhaps a stack trace of some kind?
Do these problematic machines have anything in common? Operating system, location, firewall, AV, etc? |
ScreenConnect Team |
|
|
|
 Rank: Guest Joined: 8/29/2018(UTC) Posts: 1  Location: Ohio
|
I am having the same issues since upgrading.
|
|
|
|
 Rank: Administration Medals:  Joined: 8/18/2015(UTC) Posts: 98   Thanks: 9 times Was thanked: 14 time(s) in 12 post(s)
|
Originally Posted by: davidpti2006  I am having the same issues since upgrading. The best thing to do may be to open up a support ticket with us so we can take a look at the client and the machine(s) in question via a remote session to find out what's going on: www.connectwise.com/chator www.screenconnect.com/support |
ConnectWise Control (ScreenConnect) Support Team |
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.