Powershell command Get-RDMSecurityGroup

Hi David,

I'm not able to reproduce this bug. Can I know what kind of datasource you use, this command only work with an advanced datasource.
Are you administrator in this datasource?
Are you able to create a new security group with the command New-RDMSecurityGroup?
PS C:\> $securityGroup = New-RDMSecurityGroup -Name "New SecurityGroup Name" ;Set-RDMSecurityGroup $securityGroup

Can you also try the commands Get-RDMUser and Get-RDMRole to know if all these kind of commands get the same error or only SecurityGroup.

Regards,

Olivier,

We are using Remote Desktop Manager Server v2.2.12.0 on a local server which connects to a SQL server backend database integrated with AD.

I'm wondering if maybe my RDMS version needs to be updated or if something wasn't updated in the backend SQL database the last time we updated RDMS.

I spent a little more time on this and attempted to run the following command:

$securityGroup = New-RDMSecurityGroup -Name "Test"

This was the response I got back:

New-RDMSecurityGroup : Column 'DataSourceID' does not belong to table Table.
At line:1 char:18
+ $securityGroup = New-RDMSecurityGroup -Name "Test"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [New-RDMSecurityGroup], ArgumentException
+ FullyQualifiedErrorId : System.ArgumentException,Devolutions.RemoteDesktopManager.Business.PS.Commands.NewRDMSecurityGroupCommand


I've tried this from multiple computers both joined to the domain and unjoined and I get the same result no matter what I do.

If you have any other suggestions - I'm open to any idea...

Thanks,
Dave

Hi David,

If possible can you update RDMS to v2.2.21.0? You can find how to do it at this address: http://help.remotedesktopmanagerserver.com/index.html?upgrade_rdms.htm

What version of SQL Server do you use?

Also can you create a security group directly with RDM?

Regards,

Hi David,
I suspect that maybe your database is not up to date. You could try to update the database before updating RDMS. Just make sure to backup the database before.

David,

I updated my database to version v1.93 per the Data Source Information (It was v1.91 prior)... I also updated my RDMS to v2.2.21.0...

Tried again and still getting the same message (FYI - tried standard stuff too like rebooting closing app, etc etc etc)...

Any other ideas...

Hi David,

I've been able to reproduce the error. I will work on it.

A fixed for both errors will be available in the next release.

Regards,

Thank you Olivier

One quick question - any idea when next release which would include this fix will be available?

Hi David,

Pretty soon, today or tomorrow.

I tested 10.0.9.0 and it appeared to be fixed in that version. Thank you!!