Newest Build for Debian - "no enterprise License"

Hello,

I'm currently trying to reproduce your issue. Could you tell me what type of data source you're using and what type of license the data source uses (platinum, enterprise, single user)?

Regards,

Local Data Source
Free License

But after update i can't use it.

Can the issue be resolved by performing a force refresh (hold down CTRL while clicking on the refresh icon)? Additionally, attempt to create a new local data source to check if the problem can be replicated with that data source.

I have imported my config and after that i get same message "no enterprise license"

So now i have downgraded again to can use the program!

Hello,

I am currently attempting to replicate the issue you're experiencing, but so far, I have not been successful.

Could you please inform me of the version you were using before the update that led to this issue?

Best regards,

2023.2.0.6

All other versions not work - RDP problem when try to connect to windows server! (see other posts)

Hello,

Could we arrange a remote session together? I believe I have found some potential workarounds, but I would prefer to explore them with you during a remote session.

Best regards,

Whats the workaround? Its not possible to get remote session because this is a separated system. So can you explain it to me?

Hello,

The workaround involves resetting RDM to its default settings. This is achieved by renaming the .rdm folder in your home directory to .rdm.backup, which prompts RDM to create a new folder, simulating a fresh installation.
 
Please note, if you're using a local data source, it's crucial to transfer the file connection.db from the old installation to the new one. I recommend caution here, as failing to transfer this file might make your entries appear deleted when they are actually just misplaced.
 
To make this process easier, I've created a script. You can download and try it using the following link:

https://devolutions.sharefile.com/d-sab9970689f474e1ca2b5c788af816786

Best regards,

Hello,

Our most recent release, 2023.3.1.6, includes a potential solution for your issue

Let us know if this solves it.

Regards,

Hey,

i tried newest build. And yes it works to get started, but than i can't get any RDP sessions to windows server again. Same bug as before. (see other posts )

So i can't use this version too.

Regards, Max

Hello,

Could you run RDM via terminal and provide the console output when attempting to connect to one of your RDP sessions?

Also, what is the Windows version of your servers?

Regards,

I don't understand.
Its all Windows Server 2019 or 2022. Same Bug you see in other posts with linux client.

I've tried with Windows Server 2016, 2019 and 2022 but i was unable to reproduce your issue. We'll need more information to go further.

Launch RDM with this command and then run your RDP session:

WLOG_LEVEL="DEBUG" remotedesktopmanager > LogRDM.txt

Afterward, share the content of the LogRDM.txt file here, which will help us determine the cause of this issue.

i try again now and send feedback, sorry for late reply

Newest Version for Debian i can't connect again to any Windows Server....

See the Log in attachment

Hello and thank you for providing your log.

It appears there might be an issue related to a specific library. Could you share me the output of the commands uname -a and ldd --version?

Hey,

here the results:

Linux MGMADMIN06 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux

ldd (Debian GLIBC 2.31-13+deb11u7) 2.31Copyright (C) 2020 Free Software Foundation, Inc.This is free software; see the source for copying conditions. There is Nowarranty; not even for MERcHAnTABiLITY or FItNESS FOR A PARTICUlAR PURPOSE.Written by Roland McGrath and Ulrich Drepper.

Hello,

I was able to find the cause of your issue and we'll work on it eventually in case it happens again.

Meanwhile, here's a workaround:

1. Locate 'librt' on your system (for instance, you can run the command:find /usr/lib/x86_64-linux-gnu/ -name librt*)
2. This should detect at least one of these two files: 'librt-2.31.so' or 'librt.so.1'
3. Create a symbolic link named 'librt.so' at the same location, pointing to one of the two files discovered in the previous step.
4. Start RDM then RDP should works

Hello,

the workaround works. Thank you.

Please tell me when you have fixed it.
Regards, Max

Hello,

I'm reaching out to inform you that the issue should be resolved in the latest version (2024.1.0.6).

You can now safely remove the symbolic link and resume using RDP.

Regards,