After upgrade, roles disapared from "user and security management"
After upgrade, roles disapared from "user and security management"
I upgraded our RDM from 2019.1.X to 2019.2.18 and lost some of the Roles in the process. Not totally lost since I can find them under directory/item "permissions" properties:
But they are not in "User and Security Management", and the users that where in this groups, does not have access to the folders anymore.
Since it took me some time to tune all of this, is there anyway to "get back" those groups and their membership ?
All Comments (6)
Hello,
What data source type are you using?
If it is Devolutions Password Server, what version are you using?
Before upgrading Remote Desktop Manager, have you made a backup of the database?
Best regards,
Érica Poirier
It is a MS SQL Server data source. I did not particulary backuped it, but we have a daily backup of it, so I can restore it if needed.
Hello,
Thank you for the information.
Can you try to restore the SQL database under a test name and try again the upgrade database process on that restored database to see if you can reproduce this behaviour?
I will ask our QA team to try to reproduce this behaviour as the upgrade process on my test database was successful and still have all roles available.
Best regards,
Érica Poirier
We had the exact same problem this morning after updating from 2019.1.X.0 to 2019.2.18.0. Roles list is empty, but roles are still displayed on repositories.
We did some tests and we have been able to open the "new updated" database with the rollback version of RDM (2019.1.16.0). The roles are there and everyone seems to get their access back. However, we do not trust this in long term, that's why we'll also restore the DB to yesterday.
Hello,
We've identified the cause of the issue. This will be fixed in the next RDM patch which we will release as soon as possible.
This was caused by an error in the SQL query to fetch the roles. It shouldn't have affected the data in your database.
Regards,
Hubert Mireault
Version 2019.2.19 corrected the problem.
Thank you