RDM 2023.3.24
We have the "Waiting for offline cache write to complete" issue on Windows. There was a thread about this on MacOS 2 months ago. It was solved by a newer version (2023.2.x). Waiting for Offline Cache write to complete (devolutions.net)
We use a custom MSI that includes our data source to a dvls server. The data source uses the variable $USER_PRINCIPAL_NAME$.
I can reproduce it by uninstalling RDM (as admin), deleting the Devolutions folder of all users in %appdata%, and re-installing RDM (as admin). The authentication request appears but afterwards it hangs during "Waiting for offline cache write to complete...". Then you kill the process, start RDM again and it works.
Furthermore, if you also clean out the file "C:\Program Files\Devolutions\Remote Desktop Manager\Default.cfg" that is left after the uninstall, then install RDM, you are presented with the "Create Your Data Source" wizard. The data source that is included in the MSI is just gone. I am not asked to authenticate. That is probably the reason why it does not connect to our data source.
I can go back to version 2023.1.28 and it instantly works. Did you change the authentication process between 2023.1.x and 2023.3.x?
Upgrading from that older version to the current one works, as long as I do NOT delete the user config in %appdata%.
Hello,
For the Waiting for offline cache write to complete issue.
If you can reproduce the issue please try the following:
/profiler 16385
As for the Default.cfg issue, I'm not sure what the issue is. It's not my expertise so I will let some else jump in on that question.
Stéfane Lavergne
Hello,
We believe we've found and resolved this issue with the "Waiting for offline cache".
RDM v2023.3.26.0 is currently being tested by our QA team and should be available for download either end of the week or early next week.
Best regards,
Stéfane Lavergne
Thanks for the update, Stéfane.
The version is now available for download.
https://devolutions.net/remote-desktop-manager/home/downloadenterprise/
Please let us know if the issue is resolved.
Best regards,
Stéfane Lavergne
All good now.