Devolutions ForumDevolutions Forum

Entries cannot be saved on DVLS with PowerShell 7.2

Entries cannot be saved on DVLS with PowerShell 7.2

avatar
ascheipner

Hi,
since we've updated to PowerShell 7.2.0 Final, we cannot save existing or new entries anymore on our Devolutions Server.
Reading objects with Get-RDMSession work fine in PowerShell 7.2.0, but Set-RDMSession fails all the time (see error below in output).
The same commands work most of the time in PowerShell 5.1. However also in PS 5.1 we have this error sporadically, but not always.

We use of course the latest available Module version as of today. Here's some sample output of the problem.

PS C:\RDM> gmo RemoteDesktopManager |select Version

Version
-------
2021.2.0.30

PS C:\RDM> Get-RDMCurrentDataSource |ft

ID                                   IsConnected IsOffline Name    Type
--                                   ----------- --------- ----    ----
141d21d7-070a-47b3-8883-17b3a8874f8b        True     False dps-aut RDMS

PS C:\RDM> Get-RDMCurrentVault

Description ID                                   IsAllowedOffline Name
----------- --                                   ---------------- ----
            f4f5ccef-27bc-43cd-be09-eb0c84697fff             True Cloud Operations AT

PS C:\RDM> $SessionFolder = New-RDMSession -Name 'PS72Test' -Type 'Group' -Group 'OPS Public\Web'
PS C:\RDM> $SessionFolder.Name
PS72Test
PS C:\RDM> Set-RDMSession -Session $SessionFolder -Debug
WARNING: Unable to save the entry; invalid data sent

Property Name value cannot be empty
PS C:\RDM> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.2.0
PSEdition                      Core
GitCommitId                    7.2.0
OS                             Microsoft Windows 10.0.19043
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0


Please help!

Thanks and best regards,
Alex

All Comments (6)

avatar
Jonathan Lafontaine

Hi Alex,

I'll look into it right away.

Regards

Jonathan Lafontaine

avatar
Erica Poirier

Hello,

What DVLS version are you using?

I can't reproduce this behaviour with the latest DVLS version.

Best regards,

Érica Poirier

avatar
ascheipner

Hi Erica, hi Jonathan,

I was using 2021.2.8.0 with a SQL-Fix from your Support for the Empty-Root-Problem.
Now I just updated to the latest 2021.2.10.0, but the problem still persists.

What I forgot to mention and might be important/related, we are using MFA, so I'm connected with using:

Set-RDMDatasourceProperty $TargetDataSource -Property "ScriptingTenantID" -Value $AppId
Set-RDMDatasourceProperty $TargetDataSource -Property "ScriptingApplicationPassword" -Value $RDMPassword
Set-RDMDatasource $TargetDatasource

That can be the issue, as we've had also issues in the past with it, can you please check if it's reproducable for you?

Thanks and best regards,
Alex

avatar
Erica Poirier

Hi Alex,

I'm still unable to reproduce your issue with an application key.

Could you please send an email to ticket@devolutions.net to create a support ticket? Please add a reference to this thread and I will send you a link to book a support session.

Best regards,

Érica Poirier

avatar
ascheipner

Hi Erica,

sure, done!

Thanks and best regards,
Alex

avatar
Jonathan Lafontaine

Hi Alex,

Next PowerShell module release (2021.2.0.32) might have a fix for your issue. As we were not able to produce locally, I cannot guarantee it is but I'm hopeful.

Regards

Jonathan Lafontaine