Cannot find the login for 'DOMAIN\USERNAME', because it does not exist or you do not have permission
Cannot find the login for 'DOMAIN\USERNAME', because it does not exist or you do not have permission
Hi,
Everytime I'm creating or editing a user, I'm getting the following error:
It's correct that the user doesn't have an user-object on the SQL-server, as the access to the database is granted with an AD-group.
It doesn't matter if I have unchecked "Create SQL Server Login and User" - it still gives this error.
Could this check of the SQL-user be removed somehow? It's ok, if I have to set an general option, where I'm telling that I want to create SQL-logins manually.
Br,
Anders
All Comments (4)
Hi Anders,
This is a known issue with using AD-Groups in SQL with RDM. It is on our todo to improve this process.
If I'm not mistaken, as a workaround, click on cancel (ignore the error). The save should have worked.
Best regards,
Stéfane Lavergne
Any idea when this will be fixed?
While the workaround does allow the changes to be made, it's super annoying when needing to make changes to multiple users, as you need to exit user management and re-open it for every single user account that needs updating because the screen goes completely blank when you click cancel/ignore the error.
This is my next task, so it should be available shortly.
Sorry for the inconvenience.
Best regards,
Stéfane Lavergne
The work to get this fixed has been completed and will be available in the next beta release (v2020.1.x.0)
I've done two improvements for this issue. The first is you can disable all user management on the SQL server side. That is RDM will no longer try to grant/deny any SQL privileges for that user.
The second improvement is when saving users where the grant/deny has not been disabled, any error thrown by SQL while trying to grant/revoke will simply be reported to the admin but not throw an error (no more "go offline" prompt).
Best regards,
Stéfane Lavergne
2020-01-24_11-10-53.png