locked
"No exact match was found." when searching user for adding to the site collection RRS feed

  • Question

  • Hi everyone - hope you can help me with this problem.
    In our company we have MOSS 2007 and on separate server active directory with all the users.
    Let say that we have company domain named domain.abc and sharepoint server on sharepoint (full path is sharepoint.domain.abc, but it is everywhere written just sharepoint for location). The server with AD is on users.domain.abc.
    It's a simple setup. We successfully connected the users.domain.abc with our sharepoint server- and in SSP1 the profile import is working (we can get all the people and new ones are regularly added), importing is working with no errors or warnings in logs.
    The problem is that when we want to add users in the sharepoint site- there is an error saying: No exact match was found. But existing users on the site can be found in this search box- just cannot add new ones.

    Ofcourse we google it- and checked also on this forum for the solutions, and the only thing that we found was with various solutions with Stsadm operations:

    • Setsiteuseraccountdirectorypath - we tried with: stsadm -o setsiteuseraccountdirectorypath -path "DC=sharepoint,DC=domain.abc,DC=local" –url http://sharepoint and it did not worked
    • Then with peoplepicker:
          stsadm -o setproperty -url http://sharepoint -pn peoplepicker-searchadforests -pv "forest:domain.abc,domain:sharepoint.domain.abc,domain\username,password"
          or
          stsadm -o setproperty -url http://sharepoint -pn peoplepicker-searchadforests -pv "forest:domain.abc,domain:sharepoint,domain\username,password"
          or
          stsadm -o setproperty -url http://sharepoint -pn peoplepicker-searchadforests -pv "domain:sharepoint,domain\username,password"
          or
          stsadm -o setproperty -url http://sharepoint -pn peoplepicker-searchadforests -pv "domain:sharepoint.domain.abc,domain\username,password"
          they all did not worked

      Kindly appreciate for your help. Cheers
    • Edited by Mike Walsh FIN Thursday, March 24, 2011 12:39 PM Moderator not on not posting to forums if you are in a hurry added. Sentence with urgently removed
    • Moved by Mike Walsh FIN Thursday, March 24, 2011 12:40 PM admin q (From:SharePoint - General Question and Answers and Discussion (pre-SharePoint 2010))
    • Edited by Riot7seven Thursday, March 24, 2011 3:51 PM
    Thursday, March 24, 2011 12:18 PM

Answers

  • Problem solved!

    What was the issue?

     1. I enabled (during all the tries to solve the problem) setsiteuseraccountdirectorypath.
     2. Then our forrest has only one domain (so the forrest and domain have same address).
     3. The users don't add to the site by itself if you don't push the site.

    Solution:

     1. stsadm -o setsiteuseraccountdirectorypath -path "" -url http://sharepoint
     2. stsadm -o setproperty -pn peoplepicker-searchadforests -pv "forest:domain.abc,domain\username,password;domain:domain.abc,domain\username,password" -url http://sharepoint
     3. It helps (!) if the user tries to connect to the site before he is added or anything. Once that happens - you can search for the user in the people-picker.
     4. Important: iisreset /noforce

    Well it helped for me- hope it will help you.

    Cheers

    • Marked as answer by Riot7seven Saturday, March 26, 2011 9:05 AM
    Saturday, March 26, 2011 9:04 AM

All replies

  • (In reply to a now deleted post)

    Microsoft Community Contributors are - like other people without MSFT or Microsoft in their names or after their names - not paid (or even payed) support.

    All questions posted to forums from people throughout the world have equal value and therefore attempts to make one post more important than another are not acceptable. Hence the suggestion that I probably made (deleted by you in that case) that if you are in a hurry you should contact MS Customer Support Services, where by paying for support you will be guaranteed quick support. Here you post; wait; and hope that your question interests someone.

    Moderator (pre-SP 2010 forums)


    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters
    Thursday, March 24, 2011 5:10 PM
  • Incredible! - you really took your time (again) to wrote (another) reply to something that has nothing to do with the problem or theme of this forum or post in that matter!
    I do not know - what's has (the fact that you are not paid) to do with anything. If you are unpaid volunteer with a lot of posts to moderate -> please stop wasting my time (and yours in that fact). I did not force anyone to reply - or said that my problem is more important that the other users problems.

    What  I did- was post a question and I also replied to other users question. At least I shared my knowledge and tried to help.

    I just cannot believe with what kind of things I have to deal - instead of receiving some (volunteered) support. I was prepared for reply in a month, even no reply- but not this!

    Thursday, March 24, 2011 6:15 PM
  • Hi Riot7seven,

     

    Let’s return to the issue.

     

    Cause of your issue is that you are using PeoplePicker to add users across domains. If you want to get the people picker working, you need to configure following commands on SharePoint server:

    1.       stsadm.exe -o setapppassword -password <somekey> - this command is use as encrypt\decrypt key.

    2.       stsadm.exe –o setproperty –pn peoplepicker-searchadforests –pv <list of forests or domains> -url <webapp> - this command is use to set the property for a specific web application.

     

    After running both commands above,  run IISRESET to see if it will work.

     

    Tips: Mike’s intention is to maintain a good order of this forum. If someone say that his/her problem is urgent, this will bring pressures to the people in this forum, and your problem will be more attention, this is not fair and not what we want to see. So, “urgent”, “as soon as possible” and others among this kind of words is not allowed to use here. Hope you can give more understanding.

     

    Thanks & Regards,

    Peng Lei

    Friday, March 25, 2011 9:38 AM
  • Hi Peng Lei,

    thank you for your help and advices. The solutions you provided (password creation + people-picker + iisreset) I already tried. Just now, I have also repeat it again, but the result is the same. My commands were:

    1. stsadm.exe -o setapppassword -password somekey
    2. stsadm.exe –o setproperty –pn peoplepicker-searchadforests –pv "domain:domain.abc,domain\someuser,Upassword" -url http://sharepoint
    3. iisreset

    I also replace the step 2 with

    • stsadm.exe –o setproperty –pn peoplepicker-searchadforests –pv "domain:domain.abc" -url http://sharepoint

    and the problem remained in both cases.

    You said that this issue is because I use: "... peoplePicker to add users across domains". Is there alternative? Also the users are actually in same domain:

    • server with users is in users.domain.abc
    • sharepoint is in sharepoint.domain.abc

    What are my options? Thanks in advance!

    (p.s. The issue that was not part of original post should is unimportant, jet I would like to point out that my intention was not to prioritize my issue or in anyway push anyone to help me. I understand and appreciate the effort of all volunteers and other users here - I plan to continue using this forum and helping others.)

    Friday, March 25, 2011 11:14 AM
  • Problem solved!

    What was the issue?

     1. I enabled (during all the tries to solve the problem) setsiteuseraccountdirectorypath.
     2. Then our forrest has only one domain (so the forrest and domain have same address).
     3. The users don't add to the site by itself if you don't push the site.

    Solution:

     1. stsadm -o setsiteuseraccountdirectorypath -path "" -url http://sharepoint
     2. stsadm -o setproperty -pn peoplepicker-searchadforests -pv "forest:domain.abc,domain\username,password;domain:domain.abc,domain\username,password" -url http://sharepoint
     3. It helps (!) if the user tries to connect to the site before he is added or anything. Once that happens - you can search for the user in the people-picker.
     4. Important: iisreset /noforce

    Well it helped for me- hope it will help you.

    Cheers

    • Marked as answer by Riot7seven Saturday, March 26, 2011 9:05 AM
    Saturday, March 26, 2011 9:04 AM
  • For me, the third step solved the problem.

    thanks

    Monday, March 11, 2013 10:53 AM