logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
wil  
#1 Posted : Tuesday, July 11, 2017 2:51:07 PM(UTC)
wil


Rank: Member

Joined: 6/10/2015(UTC)
Posts: 21

Was thanked: 1 time(s) in 1 post(s)
Hi,

I seem to have a few clients that have been offline for a while - I had to connect in using a different method and when I tried to reinstall ScreenConnect, I get the following message:

UserPostedImage

I've tried the standard windows diagnostics, rebuilding the installer and more, but, I haven't had much luck.

I thought maybe it was Antivirus related (Symantec .Cloud SMB), but, I have other clients with it and working fine.

Has anyone seen this before/can anyone give any advice?

Thanks

Edited by user Tuesday, July 11, 2017 2:51:40 PM(UTC)  | Reason: Not specified

Scott  
#2 Posted : Monday, July 17, 2017 11:38:14 AM(UTC)
Scott


Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 3/28/2014(UTC)
Posts: 2,518
United States

Thanks: 3 times
Was thanked: 305 time(s) in 262 post(s)
To be clear, do you get this behavior when attempting to execute the EXE or MSI installer? Does it behave differently if you use the other one?

Also, can you generate a msiexec logfile? The syntax should be similar to:

Code:

msiexec /i ScreenConnect.Client.Exe /Lv* install.log
ScreenConnect Team
MannyTC  
#3 Posted : Monday, July 17, 2017 7:47:00 PM(UTC)
MannyTC


Rank: Advanced Member

Medals: Bug Buster Level One: Spoon!Level 3: Shirt off your back! Received 25 Thanks!

Joined: 2/19/2015(UTC)
Posts: 254
United States
Location: AZ

Thanks: 8 times
Was thanked: 49 time(s) in 42 post(s)
Originally Posted by: wil Go to Quoted Post
Hi,

I seem to have a few clients that have been offline for a while - I had to connect in using a different method and when I tried to reinstall ScreenConnect, I get the following message:

UserPostedImage

I've tried the standard windows diagnostics, rebuilding the installer and more, but, I haven't had much luck.

I thought maybe it was Antivirus related (Symantec .Cloud SMB), but, I have other clients with it and working fine.

Has anyone seen this before/can anyone give any advice?

Thanks


At one point we always got that message on clients who had Symantec Endpoint Cloud. Running the installer again would always work. Another thing that worked better was to download the installer and then run it instead of running direct. Sometimes we had to run the installer twice and it would always work the second time around.

The issue seems to have gotten better and I only see it happen a very very small percentage of the time now. I am not sure if it is newer versions of ScreenConnect or if is newer versions of the Cloud and Endpoint agents but the issue has been almost non-existent as of now.

Have you tried downloading and then running it from the downloads folder?
woleg  
#4 Posted : Friday, August 25, 2017 9:02:09 AM(UTC)
woleg


Rank: Guest

Joined: 8/25/2017(UTC)
Posts: 1
Germany
Location: Munich

Hi guys, i have the same issue with all my Windows 10 Pro x64 bit machines. Any workaround for me? Thanks!

Cannot install, with this log:

=== Verbose logging started: 25.08.2017 10:42:22 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (00:D8) [10:42:22:063]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (00:D8) [10:42:22:063]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (00:60) [10:42:22:078]: Resetting cached policy values
MSI (c) (00:60) [10:42:22:078]: Machine policy value 'Debug' is 0
MSI (c) (00:60) [10:42:22:078]: ******* RunEngine:
******* Product: ScreenConnect.Client.Exe
******* Action:
******* CommandLine: **********
MSI (c) (00:60) [10:42:22:094]: Note: 1: 2203 2: ScreenConnect.Client.Exe 3: -2147287038
MSI (c) (00:60) [10:42:22:094]: MainEngineThread is returning 2
=== Verbose logging stopped: 25.08.2017 10:42:22 ===
MannyTC  
#5 Posted : Sunday, August 27, 2017 8:23:10 PM(UTC)
MannyTC


Rank: Advanced Member

Medals: Bug Buster Level One: Spoon!Level 3: Shirt off your back! Received 25 Thanks!

Joined: 2/19/2015(UTC)
Posts: 254
United States
Location: AZ

Thanks: 8 times
Was thanked: 49 time(s) in 42 post(s)
I ran into this on a Win 10 Pro system recently. No matter what I did I was unsuccessful in getting the Access client to install. What I was able to do to get around it in a pinch was to start a Support Session and then use the Install Access option. Not sure why that worked but it did.
Scott  
#6 Posted : Monday, August 28, 2017 11:58:32 AM(UTC)
Scott


Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 3/28/2014(UTC)
Posts: 2,518
United States

Thanks: 3 times
Was thanked: 305 time(s) in 262 post(s)
It's hard to say why, typically we need to see a logfile to get some more information.

In the future, you can create a logfile with the following command:

Code:

msiexec /i ScreenConnect.ClientSetup.exe /Lv* install.log
ScreenConnect Team
Users browsing this topic
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.