Issue accessing User Vault after SQL migration and authentication migration (DVLS 2026.1.11)
Issue accessing User Vault after SQL migration and authentication migration (DVLS 2026.1.11)
Hello,
I’m currently working on a migration to Devolutions Server (version 2026.1.11) and I’m encountering an issue with user vaults after the process.
Context
- Source: SQL data source used with Remote Desktop Manager
- Target: Devolutions Server (DVLS 2026.1.11)
- Migration steps:
- Full SQL database backup and restore to the new server
- Data source migration using the DVLS console (SQL migration tool)
- User authentication migration using the Authentication Migration tool (converted a SQL user to a domain user)
Current behavior
- I can successfully log in with my migrated domain account
- I have access to the Default vault and can see all entries without issues
- However, when I try to access my User Vault, I get the following error:
Unable to load the data. Root is empty ConnectionNavigationManager.GetConnectionsTree
TypeError: Cannot read properties of undefined (reading 'tree')
Questions
- Is it expected that user vaults are not migrated when using the SQL migration + DVLS migration tool?
- Should user vaults be automatically recreated after authentication migration, or is an additional step required?
- Is there a supported way to recover or migrate user vault data from the original data source?
At this point, I’m trying to determine whether:
- the user vault data was never stored in SQL (e.g., local storage), or
- it exists but was not properly mapped/recreated in DVLS
Any guidance or recommended approach would be greatly appreciated.
Thank you.
All Comments (3)
Hello,
Thank you for reaching out.
What you are experiencing is a known issue affecting SQL-to-Devolutions Server migrations performed with Devolutions Server Console 2026.1.11.0.
In this scenario, User Vault entries are not decrypted correctly during the migration, which can lead to errors such as:
- Unable to load the data. Root is empty
- Cannot read properties of undefined (reading 'tree')
This issue affects User Vaults only. Shared vaults are not affected.
To answer your questions:
- No, this is not expected behaviour.
- No, this does not mean User Vaults are unsupported for migration.
- This is not caused by the authentication migration step itself.
- The recommended approach is to restore the original SQL database from backup and rerun the migration using a fixed version of the Devolutions Server Console, such as 2026.1.12.0.
Based on your description, the problem is not that the User Vault data was stored only locally or that an additional mapping step was missed. Rather, the migration performed with Console 2026.1.11.0 did not process the User Vault data correctly.
Best regards,
It works well in version with Devolutions Server Console 2026.1.12.0.
Thank you very much !
Hello,
Thank you for the confirmation. I will mark this thread as resolved.
Please don't hesitate to reach out if you have any questions.
Best regards,