locked
Adding to a task list - User does not exist or is not unique RRS feed

  • Question

  • We have SharePoint 2010 with a single web server front end and another server as the SQL server.  When trying to add a task to a list or an announcement to a page, users are getting the error, "The user does not exist or is not unique."

    I have searched diligently for an answer, but cannot find anything about this with regards to users getting the error. 

    Thank you in advance for your assistance.

    Thursday, May 26, 2011 9:17 PM

Answers

  • I haven't figured out a solution yet, but I do have a better idea about what the problem is.  The diplay name of the majority of our users is in the format "lastname, firstname", for any of these users I receive the error.  For any accounts that the display name did not have a comma, the error didn't occur.


    Microsoft has now informed us that they have received other reports of this, so this is a known issue.  They have told me that they are working on a fix, but do not know when that will be released.

    So in case anyone wants to know for reference.

    There is an issue when using a list in the gantt view if you use the People Picker and the AD user has a comma in their display name.  This will display "The User does not exist or is not unique"

    There might be other causes, but that one is known for sure.

    Wednesday, August 10, 2011 7:35 PM

All replies

  • try putting a user in using there login id. Not all formats for the name are accepted.

     

    ie "John Doe" may not work because the name in AD might be "Doe, John" but his login of "jdoe" works fine regardless. You can also use the search tool to find the user.


    My CodePlex - My Blog - My Twitter
    • Proposed as answer by Lanny Sutton Friday, June 19, 2015 8:15 PM
    Thursday, May 26, 2011 10:32 PM
  • Hi,

     

    Please make sure the user account that you type in the people and group field is valid.


    Xue-Mei Chang
    Tuesday, May 31, 2011 9:04 AM
  • Thank you for your response.  The user is correct.  I've tried as many different users and they can all do most things except for add to these lists and a few other things. Even the administrator for SharePoint has trouble.  In fact, I tried to go in and add a something to a profile today and it gave me the same error.

    Thanks for your continued assistance.

    Tuesday, May 31, 2011 8:20 PM
  • I have verified this as well.  See my above response to MaartenSundman.

    Thank you so much.

    Tuesday, May 31, 2011 8:22 PM
  • Is the profile sync service running properly? Is this a claims or classic auth app?
    My CodePlex - My Blog - My Twitter
    Wednesday, June 1, 2011 4:07 AM
  • I am also having this issue, specifically when trying to add a person in the Assigned To field of a Project Task list. When I use the People Pciker to add people, I receive the error "The user does not exist or is not unique" after SharePoint attempts to save the changes to the row. It seems to be only the Assigned To field that causes the error, as any values I enter in other fields are saved just fine.

    If I do not use the people picker and instead use the username from AD, it seems to resolve the issue.

    This is a very inconvenient workaround, however, as my company uses several formats for the username. Having to go look up somebody's username in AD when I could just be using the people picker seems to be a waste of time. Any ideas what would be causing this?

    Thanks!

    Thursday, June 2, 2011 10:10 PM
  • As an update to my previous post, while I am able to add names to a Project Task List using the username instead of the People Picker, other admins are not and are continuing to receive the same does not exist error.
    Thursday, June 2, 2011 10:17 PM
  • I've tried to reply to this post, but failed - hoping it submits this time.  The profile sync appears to be working properly.  We are using classic authentication.  I've having no luck yet.

    Thanks.

    Thursday, June 16, 2011 5:42 PM
  • I have this same issue, I am trying to add users to a project list in gantt view and get the "The user does not exist or is not unique." error.

    If I add users via the "new item" button in list view it works fine, but inthe gantt view... error :(

    anyone got a workaround or a fix?

    Wednesday, June 29, 2011 12:03 PM
  • I believe we are experiencing the same problem.  The same error occurs when we try to add a user via People Picker in the Project Tasks view.  If we enter the name directly in the form domain\username this works fine.

    We have experienced this in our production environment which is running Sharepoint Server 2010 with the February 2011 Cumulative Update.  We have also duplicated this in our development environment with the February 2011 Cumulative Update, the SP1 Update, and the June 2011 Cumulative Updates.

    In our development environment we have only tested with Classic Authentication, but in the production environment we have tested with both.

    Monday, August 8, 2011 7:46 PM
  • I haven't figured out a solution yet, but I do have a better idea about what the problem is.  The diplay name of the majority of our users is in the format "lastname, firstname", for any of these users I receive the error.  For any accounts that the display name did not have a comma, the error didn't occur.
    Tuesday, August 9, 2011 6:09 PM
  • I haven't figured out a solution yet, but I do have a better idea about what the problem is.  The diplay name of the majority of our users is in the format "lastname, firstname", for any of these users I receive the error.  For any accounts that the display name did not have a comma, the error didn't occur.


    Microsoft has now informed us that they have received other reports of this, so this is a known issue.  They have told me that they are working on a fix, but do not know when that will be released.

    So in case anyone wants to know for reference.

    There is an issue when using a list in the gantt view if you use the People Picker and the AD user has a comma in their display name.  This will display "The User does not exist or is not unique"

    There might be other causes, but that one is known for sure.

    Wednesday, August 10, 2011 7:35 PM
  • I'm running into the same problem, when Microsoft gets back to you please update this thread.
    Monday, February 13, 2012 9:00 PM
  • hello,

    i have faced your problem few minutes ago. when i was trying to solve another problem

    --->> (Object Cache: The super user account utilized by the cache is not configured) --> my current problem

    i have found at search results the below PS command to configure super user and super reader.

    $w = Get-SPWebApplication http://webapplicationlink
    $w.Properties["portalsuperuseraccount"] = "domain account"
    $w.Properties["portalsuperreaderaccount"] = "domain account"
    $w.Update()

    but it caused me another problem which you are facing right now.

    ---> ( Error:  The user does not exist or is not unique) while adding any item to any list specially lists

    then i have tried to rollback by doing the below PS command and it worked and solved it.

    $w = Get-SPWebApplication http://webapplicationlink
    $w.Properties["portalsuperuseraccount"] = ""
    $w.Properties["portalsuperreaderaccount"] = ""
    $w.Update()

    after that check for the super user and super reader by

    Get-SPWebApplication | %{Write-Host "Web Application: " $_.url "`nSuper user: " $_.properties["portalsuperuseraccount"] "`nSuper reader: " $_.properties["portalsuperreaderaccount"] "`n"}

    This is the output for the above command should be like this.

    Web Application:  http://webapplicationlink

    Super user:
    Super reader:

    ---

    hope that it helps :)


    Karim El Zarka,Senior IT Specialist Commercial International Bank, MCTS Sharepoint

    • Proposed as answer by Shankar Gurav Monday, February 4, 2013 12:02 PM
    Tuesday, May 22, 2012 11:53 AM
  • Thanks a lot, it saved my day. Only change I have to do is pass valid account not empty one.
    Monday, February 4, 2013 12:02 PM
  • Did you get any feedback from microsoft in regards to this bugfix, we're on the december 2012 CU and are still experiencing this bug.

    Kind regards,

    Friday, April 12, 2013 7:18 AM
  • This solved the problem for me, simply changing to Firstname.Lastname (i.e. the login ID)

    Thank you :)

    Thursday, December 19, 2013 12:23 AM
  • "try putting a user in using there login id. Not all formats for the name are accepted.

    ie "John Doe" may not work because the name in AD might be "Doe, John" but his login of "jdoe" works fine regardless. You can also use the search tool to find the user."

    This worked for me...thank you!

    • Edited by COTWebMgr Friday, June 20, 2014 1:07 PM
    Friday, June 20, 2014 1:06 PM