After upgrading to 2026.2.11.0. Some users fail to login to RDM Azure SQL database (Cannot use 'Authentication=Active Directory Interactive' with 'Password' or 'PWD' connection string keywords)
Some users are not able to use RDMs Azure SQL database after we pushed out version 2026.2.11.0 (old version: V2025.2.29.0). Error message from the "details" button:
System.ArgumentException: Cannot use 'Authentication=Active Directory Interactive' with 'Password' or 'PWD' connection string keywords.
at Microsoft.Data.SqlClient.SqlConnectionString..ctor(String connectionString)
at Microsoft.Data.SqlClient.SqlConnectionFactory.GetConnectionPoolGroup(DbConnectionPoolKey key, DbConnectionPoolGroupOptions poolOptions, DbConnectionOptions& userConnectionOptions)
at Microsoft.Data.SqlClient.SqlConnection.ConnectionString_Set(DbConnectionPoolKey key)
at Microsoft.Data.SqlClient.SqlConnection.set_ConnectionString(String value)
at Microsoft.Data.SqlClient.SqlConnection..ctor(String connectionString)
at Devolutions.RemoteDesktopManager.Business.DataSources.SQLServerConnectionDataSource.CreateDbConnection(String connectionString, Boolean openConnection)
at Devolutions.RemoteDesktopManager.Business.DataSources.SQLServerConnectionDataSource.TestConnection(String userName, String domain, String password)
I have tried:
Affected users on my computer = works.
Downlading binary / zip version of RDM on affected user. = Same problem there
Removing %localappdata%\Devolutions folder and uninstalling / reinstalling the program on affected user = Did not help
We are using login mode "Active Directory Interactive (with MFA support)".
Any advice what to look for from here?
Hi,
Thank you for reporting the issue. This is a regression that was introduced recently. While we work on a fix, a temporary workaround is to uncheck "Allow change username", after which you should be able to connect.
Sorry for the inconvenience.
Best regards,
Stéfane Lavergne
Issue has been resolved and the fix will be available in the next release.
Best regards,
Stéfane Lavergne
Nice. Workaround seems to work. Thanks for quick response.