• State Verified Answer
  • Replies 7 replies
  • Subscribers 47 subscribers
  • Views 1911 views
  • Users 0 members are here
Options
Related

Cannot add Windows user

Simon Bratina

Hi, 

As this has happed so many times on different installations and in the end is preventing GroupShare client to use Windows Authentication, I would like to check with the community if anybody of you has experienced the same manifestation and symptoms. 

The scenario and the test case is the following. 

1. GroupShare Administrator imports Windows users from AD into GroupShare (Import Windows User).

2. Using GroupShare Web console, GroupShare Administrator creates new GroupShare (as Windows user) and give this user appropriate rights.
    The newly created user is able to work with GroupShare.

3. In  GroupShare Web console, Administrator deletes the previously created (GroupShare Windows user).  The user is removed from GroupShare users. (this is expected behavior)

Now, the Administrator realized that the removing user was mistake and want to get the user back. So he follows the "Create New User" 

But get the following error: Cannot add user DOMAIN\username. A user with that name already exists.

My problem is that I don't know for a method that would allow the client to again add the previously deleted Windows user.

Does anybody knows for a generally usable solution in such cases.

BTW, this issue was seen with Gropushare 2017 and is stil present in GroupShare 2020

Simon
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Hi - I am not able to reproduce this but it's possible that I am missing something. I have a few questions for you:

    1. In the first screenshot you say you're trying to add a Windows user but the User Type is "SDL" then you use Username in the format DOMAIN\username - why is that? If you want to add a Windows user you should select User Type: Windows

    2. Depending on the size of the server, the number of users on it and the exact GroupShare version, deleting a user from the Web UI can take up to a few seconds - sometimes 5,6. What happens though is you delete the user and it is immediately removed from the list, making you think it was deleted, but if you click on the Refresh button, it appears again. Keep clicking on the Refresh button until it no longer appears.

    3. When the error "... user alread exists" - did you check in the database? In the SDLSystem database , table name is: sts.User - all users are stored there.

    4. Lastly, for the last screenshot you sent, sometimes there are indeed some errors in the tables in the SDLSystem database and it helps to run the Configurator.exe executable - from here: C:\ProgramData\Package Cache\SDL\SDLTradosGroupShare2020/2017

    So with the information above, please try to reproduce the behaviour and see if indeed you can do that and you can consistently get the error - provide us detailed steps and if indeed it is a defect, we are happy to report to Development and have it addressed.

    Thank you

    Adrian
Reply
  • 0

    Hi - I am not able to reproduce this but it's possible that I am missing something. I have a few questions for you:

    1. In the first screenshot you say you're trying to add a Windows user but the User Type is "SDL" then you use Username in the format DOMAIN\username - why is that? If you want to add a Windows user you should select User Type: Windows

    2. Depending on the size of the server, the number of users on it and the exact GroupShare version, deleting a user from the Web UI can take up to a few seconds - sometimes 5,6. What happens though is you delete the user and it is immediately removed from the list, making you think it was deleted, but if you click on the Refresh button, it appears again. Keep clicking on the Refresh button until it no longer appears.

    3. When the error "... user alread exists" - did you check in the database? In the SDLSystem database , table name is: sts.User - all users are stored there.

    4. Lastly, for the last screenshot you sent, sometimes there are indeed some errors in the tables in the SDLSystem database and it helps to run the Configurator.exe executable - from here: C:\ProgramData\Package Cache\SDL\SDLTradosGroupShare2020/2017

    So with the information above, please try to reproduce the behaviour and see if indeed you can do that and you can consistently get the error - provide us detailed steps and if indeed it is a defect, we are happy to report to Development and have it addressed.

    Thank you

    Adrian
Children