Jump to content

Recommended Posts

Afternoon All we just updated to this patch yesterday and now no new Screenconnect control agents will install through labtech support has said it was a creeping up bug was just wondering if anyone found a work around in the mean time.

Share this post


Link to post
Share on other sites

I am having the same issue and worked on it for quite a bit today. I did find that the installs are failing with the following error:
'Failing command since command code is tied to a plugin that does not appear to be loaded. Set lt_IgnorePluginCommandCheck template property to disable this check.'

I am not super great with that, but I did not find that specific property anywhere in the templates.

Share this post


Link to post
Share on other sites

Yeah we have worked alot with support and our ticket has been sent to the developers so they can fix it, it seems it some miss match between labtech and Screenconnect as if you manually install the Screenconnect on a system it checks into the screenconnect server and you can connect there with no issues, but its inaccessible form our labtech with that same error

Share this post


Link to post
Share on other sites

Yeah, I saw the same thing here. Would you mind sharing your ticket number so that I can refer to it when I call support?

Thanks in advance...

Share this post


Link to post
Share on other sites
Posted (edited)

@troms @bigdog09, The plugin problems can be remedied by "updating" the connectwise control remote agent plugin from plugin manager and reloading the dbagent. Just grab the dll from the Automate server plugins folder. 

Edited by johnduprey
  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

Chatted with CW support talked with Wai Wong.  Very nice guy, provided a simple solution and also stated this is a known issue and development is working on it.

Go to CW Control and download the Control Agent installer.  Run this on the computer that needs Control.  Then go back to the Control web interface and find the computer that you just installed the agent on.  When you single click on the computer you will see the URL will change, copy the last part of the URL (SessionGuid)

Also you need your Automate Agent ID (ComputerID) for this machine.

Now log into your Automate server and open up your database.  There is a table, plugin_screenconnect_scinstalled that needs to be updated to get the link in Automate to open up the correct Control connection.  The table layout is       ComputerID, IsSCInstalled, SessionGUID

Add 1 record for the computer with the above information in the table, and of course IsSCInstalled should be a 1.

Share this post


Link to post
Share on other sites
Posted (edited)

Two people on Reddit are saying the latest version of the Control plugin, or reinstalling the Control plugin, fixes this...

 

Edited by SteveYates
  • Like 1

Share this post


Link to post
Share on other sites

Support confirmed for me that updated the Control plugin through Solution Center resolves it.  I completed this and can confirm the issue is resolved. 

However, agents that "missed" their Control install (between the time we deployed 2019.3 and the time we updated the plugin) need to have "Update Plugins" command run against them, which will force Control to install correctly. 

  • Like 3

Share this post


Link to post
Share on other sites

Yes Support was able to correct it for us as Well they had to remove our screenconnect plugin fully then reinstall it, once that was done and we did an update of remote plugins it started to work again, but had a few that had to be fixed but nothing major but it did take a few days for them to track it down.

Share this post


Link to post
Share on other sites

Anyone else had an issue with non super-admins not being able to run scripts while on web version? I opened a chat with support and it got immediately escalated. Known issue?

Share this post


Link to post
Share on other sites

On a ScreenConnect note, does anyone know the difference between "Reinstall" and "Redeploy" for ScreenConnect?

 

Share this post


Link to post
Share on other sites
5 minutes ago, timwiser said:

On a ScreenConnect note, does anyone know the difference between "Reinstall" and "Redeploy" for ScreenConnect?

 

I asked support a while back about SC agents not self-updating.  The answer:

"You can update clients Automatically through the Integration settings. If you go to System>Configuration>Dashboard>Config Tab>Integration Tab>Connectwise Control. Then click on "Control Server Settings" to open the Settings Editor. Then scroll to find the setting "AutoReinstallOldVersionClient" and make sure that check box is selected. Once that's done just click "Save" and the clients should start updating automatically after the Control services restart.

If you want to do it manually the best thing is to use the "Reinstall" command on each client."

From the bottom of page https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/080/020/020/020 it sounds like redeploy is for when someone removes (Ends) it in SC?

Share this post


Link to post
Share on other sites

I too can confirm that updating the plugin, then sending the Update Plugins command fixes the issue. I love sitting in the chat queue for 20 minutes and fixing it before I actually get to talk to someone 😐

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...