Tell me more ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.
up vote 1 down vote favorite

Here's the situation:

  • Single Sharepoint web front end server in domain A.
  • Site is also used by members of domain M.
  • There is a one-way trust from domain A to M.
  • The people picker has been set up to search in both domains using the peoplepicker-searchadforests property and works fine.

Here's the problem:

  • When trying to assign a task in a sharepoint task list, the people picker can be successfully used to pick a user that is in domain M and populates the field with their username. However, when saving the task, the error "The user does not exist or is not unique." is thrown, and the tasks assignment doesn't change.
  • This only happens with users that are in domain M AND do not already have a corresponding sharepoint user account. They only have permission to access the site by virtue of being a member of a domain security group that is in a sharepoint group.
  • If I explicitly add the users domain account to a sharepoint group, the task assignment works fine.

What might the problem be?

share|improve this question
A couple of questions. Are you using MOSS or WSS? Are you using user profiles for the users who are in both domains or only in Domain A? What is your sync schedule for that if you are? – Lori May 18 '10 at 15:26
MOSS. I'm not sure about the other questions, how can I check? – maxpower47 May 18 '10 at 16:15

closed as too localized by Anders Rask♦ Jun 2 '11 at 17:07

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, see the FAQ.