Devolutions ForumDevolutions Forum

Microsoft.Data.SqlClient error when setting current RDM DS

Resolved

Microsoft.Data.SqlClient error when setting current RDM DS

avatar
cryorig

Powershell 7.5.1
RDM 2025.1.31
Devolutions.Powershell 2025.1.3
Backend MSSQL 2019
Host OS: Windows Server 2022 (RDS)

Currently in the process of moving some of our scripts to PS7 and have the following Issue with RDM/Devolutions.Powershell

Get-RDMDataSource -Name XYZ | Set-RDMCurrentDataSource
Set-RDMCurrentDataSource: Could not load file or assembly 'Microsoft.Data.SqlClient, Version=6.0.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5'. The located assembly's manifest definition does not match the assembly reference. (0x80131040)

The same happens with Get-RDMCurrentDataSource.

I then updated RDM to 2025.1.34 and Devolutions.Powershell to 2025.1.4, but the Issue stayed the same.

Is there anything that can be done from my side or do i have to wait for a fix/update of the Powershell Module?

BR,
Stefan

All Comments (4)

avatar
Patrick Ouimet

Hello Stepfan,

Thank you for reaching our to the Devolutions support team.

  • Could you execute Get-RDMInstance in PowerShell?
  • Which directory it is pointing at?
  • Is it the same the the one your RDM is installed?
  • Is this directory is under programFiles or programFiles (X86)?
  • Could you check the properties of your Microsoft.Data.SqlClient.dll -> Details and tell me the product version?
  • If this directory is not pointing at your main installation of RDM, could you use the override to point at your 2025.1 path of RDM?


https://docs.devolutions.net/powershell/rdm-powershell/rdm-powershell-core-module/#use-an-override-configuration-portable

Let us know.

Best regards,

Patrick Ouimet

avatar
cryorig

Hi Patrick, 

Get-RDMInstance:
ApplicationVersion OptionFilename
------------------ --------------
2025.1.4.0         C:\Users\myuser\AppData\Roaming\Devolutions\RemoteDesktopManager\RemoteDesktopManager.cfg

RDM is installed here:

C:\Program Files\Devolutions\Remote Desktop Manager

Microsoft.Data.SqlClient.dll exists twice in the RDM Directory, both have the same Version 6.1.25023.1

C:\Program Files\Devolutions\Remote Desktop Manager\Microsoft.Data.SqlClient.dll
C:\Program Files\Devolutions\Remote Desktop Manager\runtimes\win\lib\net9.0\Microsoft.Data.SqlClient.dll


Setting the Override helped!

$override.RemoteDesktopManagerExecutablePath = "C:\Program Files\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe"
$override.OptionFilePath = "C:\Users\myuser\AppData\Roaming\Devolutions\RemoteDesktopManager\RemoteDesktopManager.cfg"

But why is this working? i never had this problem with 2024.X (yes i haven't touched Devolutions.Powershell for quite some time)
Does this mean i have to set this every time i want to use the module?
Or is this a effect of working in an RDS Session?

avatar
Patrick Ouimet

Hello Stefan,

I tried to reproduce this on our RDS environment, but mine works great.
The Get-RDMInstance is also on my roaming profile, and the installation path is also under Program Files.

According to your policies, maybe you will have to do the override every time.
The best way to test it is to log out and log in from your RDS session.

Let us know if there is anything else we could do.

Best regards,

Patrick Ouimet

avatar
cryorig

thanks for the help, for now i can work with this, i will update here if i can find some root cause