Page 1 of 2

Patch Remedy does not work on automate 19.4

Posted: Mon Apr 29, 2019 7:21 pm
by ccalverley
Patch manager no longer is operational on connectwise automate April 2019 release,
I attempted the .zip file in the patch manager fails to load forum, with no success as well as the
Resetting up the windows enviroment option given in that same forum.

When attempting to open Patch Manager in automate
A box pops up very quickly followed by a complete crash of automate

event log error 1000
Faulting application name: LTClient.exe, version: 190.110.7032.21546, time stamp: 0x5ca4d81c
Faulting module name: mshtml.dll, version: 11.0.17134.677, time stamp: 0x9eb87194
Exception code: 0xc0000602
Fault offset: 0x008caa31
Faulting process id: 0x1c04
Faulting application start time: 0x01d4fe7cfc1a4b66
Faulting application path: C:\Program Files (x86)\LabTech Client\LTClient.exe
Faulting module path: C:\Windows\System32\mshtml.dll
Report Id: bc9208c5-7d82-4dcc-9f72-f0a8152f990e
Faulting package full name:
Faulting package-relative application ID:

ltcErrors.txt

****************************************************************************************************************
2019-04-29 15:03:31.109 -04:00 [Information] APPLICATION_NAME=LTClient APPLICATION_VERSION=v190.110 THREAD_ID=1
"APPLICATION_NAME="LTClient""
"APPLICATION_VERSION="190.110""
"UTC_TIMESTAMP="2019-04-29 19:03:31.109""
"SOURCE="Control Center""
"MESSAGE="Observed unhandled dispatcher exception: PatchRemedy InitializeComponent Could not load file or assembly 'DevExpress.XtraCharts.v12.2, Version=12.2.17.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a' or one of its dependencies. The system cannot find the file specified. Could not load file or assembly 'DevExpress.XtraCharts.v12.2, Version=12.2.17.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a' or one of its dependencies. The system cannot find the file specified.""

Re: Patch Remedy does not work on automate 19.4

Posted: Tue Apr 30, 2019 12:42 pm
by Cubert
The issue your experiencing is a missing DevExpress library that was provided in previous builds missing in your deployment.

Here is the fix for that issue
http://support.plugins4automate.com/vie ... b21b5c32b1

We see this from time to time with new deployments of the LT console. They will fail to include version 12 of the Dev Express Charts library which causes the charts on the plugin to fail to load. This in turn causes plugin to fail to launch (open).

Following the install of the libs you should be able to launch PR.

Re: Patch Remedy does not work on automate 19.4

Posted: Tue Apr 30, 2019 1:30 pm
by ccalverley
I did mention that i tried both options in the suggested post above

Re: Patch Remedy does not work on automate 19.4

Posted: Mon May 06, 2019 2:45 pm
by ccalverley
Is there any update on this?

Re: Patch Remedy does not work on automate 19.4

Posted: Mon May 06, 2019 4:16 pm
by Cubert
Working on trying to reproducing the error. Stand by.

Re: Patch Remedy does not work on automate 19.4

Posted: Thu May 30, 2019 11:21 am
by ccalverley
Were you able to recreate this issue?

Re: Patch Remedy does not work on automate 19.4

Posted: Thu May 30, 2019 2:43 pm
by Cubert
This is the latest platform we have tested with to date.
Capture.PNG
Capture.PNG (81.08 KiB) Viewed 19552 times
What patch are you currently on? post a image of your about section (version info only)

Re: Patch Remedy does not work on automate 19.4

Posted: Thu May 30, 2019 5:23 pm
by ccalverley
We are on 2019.4

Re: Patch Remedy does not work on automate 19.4

Posted: Thu May 30, 2019 6:51 pm
by Cubert
So the answer is we are ahead of you on the updates and it appears to be working fine on our dev platform.


Can you give us some insights as to how old the install of yours is, Are all consoles doing the same thing, console on the server doing it as well?


You also on all effected tech consoles you ran the following installs, rebooted PC and retried?

http://lp.plugins4automate.com/files/DX ... 2.2.17.zip

Re: Patch Remedy does not work on automate 19.4

Posted: Fri May 31, 2019 11:28 am
by ccalverley
I completely removed and readded the plugin and this appears to have fixed the issue