Hi Cubert,
I've already tried these steps multiple times over on multiple machines.
I appreciate this is a client side issue but I just want to keep the ball rolling on fixing this issue.
-kfear
Search found 11 matches
- Thu Jan 17, 2019 10:04 pm
- Forum: Patch Remedy for LabTech (Patch Remedy 4) Retired
- Topic: Odd plugin behaviour after reinstall with complete cleanup
- Replies: 16
- Views: 25941
- Thu Jan 17, 2019 1:49 am
- Forum: Patch Remedy for LabTech (Patch Remedy 4) Retired
- Topic: Odd plugin behaviour after reinstall with complete cleanup
- Replies: 16
- Views: 25941
Re: Odd plugin behaviour after reinstall with complete cleanup
Glad I'm not the only one, however still doesn't get me closer to a fix...
@skyscan, care to share any environmental info to try pinpoint similarities?
Our environment:
--Automate Server
OS: Windows Server 2016 Std
LT Version: 120.473 / 2019.11
DB: MySQL Community Server (GPL) version: 5.6.38 ...
@skyscan, care to share any environmental info to try pinpoint similarities?
Our environment:
--Automate Server
OS: Windows Server 2016 Std
LT Version: 120.473 / 2019.11
DB: MySQL Community Server (GPL) version: 5.6.38 ...
- Mon Jan 14, 2019 2:06 am
- Forum: Patch Remedy for LabTech (Patch Remedy 4) Retired
- Topic: Odd plugin behaviour after reinstall with complete cleanup
- Replies: 16
- Views: 25941
Re: Odd plugin behaviour after reinstall with complete cleanup
Hi Cubert,
Our PR has been down for around 2 months now, which we have still paid per month for the license.
It's been over 2 weeks since my last post requesting a bit of guidance which has fallen on deaf ears.
I would appreciate some guidance here otherwise we will have to cancel our subscription ...
Our PR has been down for around 2 months now, which we have still paid per month for the license.
It's been over 2 weeks since my last post requesting a bit of guidance which has fallen on deaf ears.
I would appreciate some guidance here otherwise we will have to cancel our subscription ...
- Wed Jan 09, 2019 6:07 am
- Forum: Patch Remedy for LabTech (Patch Remedy 4) Retired
- Topic: Fail to Lauch Tool
- Replies: 6
- Views: 10597
Re: Fail to Lauch Tool
@RSCS - Do you have errors under Event Viewer\Custom Views\, the source will be 'Control Center'.
I have also loaded DevExpress v12 on my system and have the DLL's locally.
Here are some examples of mine:
ID:Unhandled thread exception Name:loadSettings MSG:Object reference not set to an instance ...
I have also loaded DevExpress v12 on my system and have the DLL's locally.
Here are some examples of mine:
ID:Unhandled thread exception Name:loadSettings MSG:Object reference not set to an instance ...
- Wed Jan 09, 2019 6:01 am
- Forum: Patch Remedy for LabTech (Patch Remedy 4) Retired
- Topic: Fail to Lauch Tool
- Replies: 6
- Views: 10597
Re: Fail to Lauch Tool
I have a similar experience - If you open another plugin under tools then try to open PatchRemedy does it open ?
@Cubert - Could be the same issue as mine ?
@Cubert - Could be the same issue as mine ?
- Wed Dec 26, 2018 11:00 pm
- Forum: Patch Remedy for LabTech (Patch Remedy 4) Retired
- Topic: Odd plugin behaviour after reinstall with complete cleanup
- Replies: 16
- Views: 25941
Re: Odd plugin behaviour after reinstall with complete cleanup
Hi Cubert,
I tried copying all the DLL's into the system32\ folder but same issues.
Not sure what to do with the .vsix file? Any guidance on this?
Thanks
I tried copying all the DLL's into the system32\ folder but same issues.
Not sure what to do with the .vsix file? Any guidance on this?
Thanks
- Tue Dec 18, 2018 9:32 pm
- Forum: Patch Remedy for LabTech (Patch Remedy 4) Retired
- Topic: Odd plugin behaviour after reinstall with complete cleanup
- Replies: 16
- Views: 25941
Re: Odd plugin behaviour after reinstall with complete cleanup
Hi Cubert,
Any updates?
Thanks
Any updates?
Thanks
- Tue Dec 11, 2018 10:13 pm
- Forum: Patch Remedy for LabTech (Patch Remedy 4) Retired
- Topic: Odd plugin behaviour after reinstall with complete cleanup
- Replies: 16
- Views: 25941
Re: Odd plugin behaviour after reinstall with complete cleanup
Hi Cubert,
I copied the files into the \LabTech Client\ folder and overwrote the files there.
When trying to launch the plugin event viewer shows:
Dispatcher Exception: Could not load file or assembly 'DevExpress.XtraCharts.v12.2, Version=12.2.17.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a ...
I copied the files into the \LabTech Client\ folder and overwrote the files there.
When trying to launch the plugin event viewer shows:
Dispatcher Exception: Could not load file or assembly 'DevExpress.XtraCharts.v12.2, Version=12.2.17.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a ...
- Tue Dec 11, 2018 3:06 am
- Forum: Patch Remedy for LabTech (Patch Remedy 4) Retired
- Topic: Odd plugin behaviour after reinstall with complete cleanup
- Replies: 16
- Views: 25941
Re: Odd plugin behaviour after reinstall with complete cleanup
Hi Cubert,
I've tested this on multiple other machines and we have the same behaviour.
I checked the LT server logs, both provided by the LT Server software and within the LT Server Event Logs.
There is nothing being logged that would be causing this issue in either locations.
I even reached out ...
I've tested this on multiple other machines and we have the same behaviour.
I checked the LT server logs, both provided by the LT Server software and within the LT Server Event Logs.
There is nothing being logged that would be causing this issue in either locations.
I even reached out ...
- Sun Dec 09, 2018 9:18 pm
- Forum: Patch Remedy for LabTech (Patch Remedy 4) Retired
- Topic: Odd plugin behaviour after reinstall with complete cleanup
- Replies: 16
- Views: 25941
Re: Odd plugin behaviour after reinstall with complete cleanup
Hi Cubert,
I've come in this morning and these are the steps and results given:
1. Opened LT fresh (not previously open)
2. Opened PatchRemedy plugin
3. Version # is correct
4. All switches are off
5. No popup, license valid through to 8th Jan 2019
6. Turned ON master switch
7. Closed PatchRemedy ...
I've come in this morning and these are the steps and results given:
1. Opened LT fresh (not previously open)
2. Opened PatchRemedy plugin
3. Version # is correct
4. All switches are off
5. No popup, license valid through to 8th Jan 2019
6. Turned ON master switch
7. Closed PatchRemedy ...