RDM Team 2022.3.x - Far more bugs than I could begin to describe
Seems like I am unable to pull a license despite having one correctly associated with my account. Bottom ribbon says "no license found".
Dozens of errors resulting in a complete failure to add Password Hub for Business. Attempts to add or refresh ANY datasource just yield dozens of errors similar to "an error occurred when sending this request"
I completely deleted my appdata devolutions folder and reinstalled with identical symptoms. I have tried several PCs on various networks. All users in my org have identical symptoms on 2022.3.x and worked *fine prior
Am I and my team special, or is this version hot garbage?
Hello,
I can see that you also opened a case with us, we will troubleshoot your different issues via this case!
Best Regards,
Etienne Lord
@alexmarsaudon,
Sorry for any frustration this update has caused for you and your team.
The version 2022.3.16 should fix any licensing problem regarding the license migration and should be automatically transported to the Hub server. If that was your main issue this would be solved.
Regarding the other issues, if you could give us a better description of the behavior you're encountering, I'd be happy to troubleshoot it with you.
Regards,
Alexandre Roy
Some copy-paste action here:
-----------------------------------------------------------
-The licensing changes. I did have an RDM key added to my
user account, but apparently I also needed to activate the RDM enterprise key
against my enterprise and assign one of said licenses to my user account. I got
this corrected.
-Correcting the above was incredibly erratic due to whatever
issue you were experiencing with your cloud platform most of yesterday. I
received probably 100 instances of the an error occurred when sending this
request" message I had described in my forum post. Every time that popped
up, the application would glitch out extremely hard, taking 2-5 minutes to
recover each time. This error popped up when the application launched,
attempted to refresh my datasource, attempted to log in to the RDM application
itself to pull a license, during the pulling a license, etc etc. Note I did try
from at least 3 different networks, on multiple PCs, with and without antivirus
active, etc etc.
It also appears that 2022.2.x à
2022.3.x didn’t gracefully handle my requirement for Windows Hello on launch. I
was forced to nuke my entire %AppData%\Devolutions folder to remove that, then
relaunch and wade through the mountain of errors again.
2 of my 3 devices now seem to be working as expected on
2022.3.x, including 1 PC and one Mac.
These changes have me nervous though, can the application still be launched
without internet access / in offline mode?
---------------------------------
I am not experiencing the same licensing nags, but definitely am an advocate of it providing a useful error message vs a hard-crash if you attempt to launch without a license.
I believe my only lingering issue at this point is the fact that the application tanks entirely if I attempt to flip from my Password Hub for Business datasource to my Devolutions Online Drive datasource. This occurs on both PC and Mac RDM clients. RDM hangs indefinitely as soon as you attempt the switch, never provides any output explaining the indefinite timeout. I left it for over an hour and it never recovered.
Hello,
We have been in beta for more than a month but it seems that some cases were missed. Our goal is to provide some clear indications of what's missing. For most people the workaround is to save the licenses into the database and assign them to the users. I will ask our QA to test the Windows Hello issue.
I have no explanation why the application hang and we might be able to investigate with a trace.
Regards
David Hervieux