jeff11

My data source is an Azure SQL Database.

Ok, I uploaded the screenshot as an attachment.

Hi Devolutions,

I am running Enterprise Edition 2019.2.24.

You need to update your documentation on this. I renewed my license this morning and went to look for the procedure to get it into the system for my team and what I found was the old approach using System Settings > Serial Number, which was not available on my version of RDM. Had to do a bunch of googling and wasting of time to find a thread that explains what has happened:

https://forum.devolutions.net/topic32847-getting-the-user-has-not-been-assigned-a-valid-serial-number-on-sql-az.aspx

Here is the original documentation page that I found first and that is no longer applicable:

https://help.remotedesktopmanager.com/installation_registration_enterpriseedition.htm#for-administrators

Even after trying what is in the forum thread, I get this error that doesn't make any sense:

I entered the renewal license key directly from the email I got and it immediately showed the new license being valid for another year and the number of users.

But, when I assigned it to the three users and and then click OK to save the page, it pops up with the License is not valid message.

Yes, I just sent them, Stefane.

I ended up uninstalling VS 2019 on this laptop and installed it on a VM that I can remote into, in order to workaround the problem and keep moving. So, I can't really re-test easily for you if you find a problem and come up with a solution. But, maybe you won't be able to replicate it and it will turn out that it was just a configuration problem with my particular laptop.

Thanks for looking into it so quickly!

Jeff

A little more info -

I ended up uninstalling Visual Studio 2019, and then was able to reinstall Active Directory Authentication Library for SQL Server from the download link RDM provides.

So, it looks like VS 2019 installs a newer version of adalsql.dll that RDM is not compatible with. I could never locate adalsql.dll anywhere on my Windows 10 machine, so I am not sure where VS 2019 installs it. But, it was most certainly there because I could not install the compatible version of it due to the installer recognizing that a newer version existed on my machine.

Look forward to hearing from Devolutions as to when RDM will be compatible with the version of adalsql that VS 2019 installs.

I just installed Visual Studio 2019 and now on my computer I get the "Unable to load adalsql.dll error message on launch of RDM".

Of course, I had been using RDM successfully with my Azure SQL Data Source for some time and had downloaded and installed adalsql.dll a long time ago.

When I try to reinstall the version of adalsql.dll that RDM recommends, I get a message that there is a newer version already on my PC.

In Programs and Features, there is not a seperate line iteam for adalsql anymore. I assume it gets installed with the the Microsoft Azure Libraries for .NET - v2.9 (which actually shows as 3.0.0127.060 in the Version column).

Will RDM support the latest version of adalsql soon? I need RDM and VS 2019 both on my PC.

I just tried disabling RunDll32.exe usage, and that solved the problem with Chrome for me on Windows Version 1809 Build 17763.292. Chrome embedded now works again.

I have not tested with Firefox again. However, I notice that there is not a similar setting in RDM for Firefox.

Jeff

Me too. Just started noticing it today.

If I switch the browser in the session settings to IE, it works fine embedded.

Winver: Version 1809 Build 17763.292

RDM EE 14.1.3.0 64-BIT

Chrome: 72.0.3626.109 (Official build) (64-bit)

Another piece of info -

On a different laptop with Winver = Version 1803 (OS Build 17134.590), Chrome and Firefox work fine in embedded still.

Finally, on the machine with Windows 1809, if I choose to open the session externally, it loads fine in Chrome and Firefox.