unable to update users with SQL DB intergration
Hello,
we are using devolutions with SQL DB integration.
we have added a few users with the options of integrated security & the SQL user creation.
the issue that we are having is the users affected have had the names of the AD accounts updated. (ie Joseph to Joey) but when this user tries to connect it throws an error.
we then tried to update the users name, but get a SQL error about a duplicate SPN.
we then removed the user, & tried to re-add them, but still get the same error.
what is the proper way to update users/remove then add them back
All Comments (5)
Hi,
When you remove the user, it is removed from the DB, but the login stays behind.
We do not support renaming a user account, therefore you would need to delete both the user from the db, and the login from the server, and re-create the user. That means you would loose your personal settings though.
If you want to preserve all of the personal settings and private vault, we will have to work on a script for you, but since we are in Houston a the moment for the TechEd conference, it would have to wait until next Tuesday (Monday is a civic holiday for us).
Maurice
we have removed the user from the devolutions administration > users section , as well as removed them from the DB under the security section. However when we try to add them back in , is when we get the cannot add a duplicate SPN error.
is there anywhere else (in a table) that i could/should remove the user from so i can re-add them/>
You must make sure that the "3 users" gets deleted (RDM user, SQL user & SQL login).
In SSMS (SQL Server Management Studio) check in both nodes.
Once deleted the add in RDM should work.
edited by stefane on 5/20/2014
Stéfane Lavergne
5-20-2014 1-01-22 PM.png
unfortunatley i cannot remove the user from the Logins, as the user must have access to the other DB's all the time.
I do not see how the user under the security > Logins has anything to do with your DB.
this user existed there before we rolled out the DB for RDM.
I see what you mean.
Can you post the entire error (Help -> View Application Log). I have a feeling that since the rename it is trying to remap the server login to the DB user but it is have issues with it. The full error (stack and all) might help shed some light on the issue.
Stéfane Lavergne