locked
people picker slow no AD Problems RRS feed

  • Question

  • In people fields when I use people picker to select users and group it's very slow. It returns results in 5 or 8 minutes. I'm having testing and researching many options.

    I've used Message Analyzer and TCPView to make traces and connections with domain controller are ok. I've tested it with peoplepicker and with a little windows console application that user DirectoryServices and go ok.

    I've done traces with SQL Profiler and there are calls to stored procedures explained here:

    https://msdn.microsoft.com/en-us/library/dd357076.aspx

    Peoplepicker continues very slow. It's a nightmare. I'm thinking that it's a version problem. Any ideas please?????

    Friday, July 10, 2015 1:06 PM

Answers

  • The users are coming from both domains?

    If not you can limit peoplepicker to one domain. Check the parameters of this command:

    stsadm –o setproperty –pn peoplepicker-searchadforests

    https://technet.microsoft.com/en-us/library/cc263460(v=office.12).aspx


    MCITP|MCTS SharePoint| SharePoint Performance blog

    Monday, July 13, 2015 12:16 PM

All replies

  • On the server where the SharePoint is installed create a folder on the desktop, access the security tab  and search for the same user from AD.

    Are you having the same issue?

    Are you having only one forest? 


    MCITP|MCTS SharePoint| SharePoint Performance blog


    Saturday, July 11, 2015 3:30 PM
  • here you have a complete guide to troubleshoot this issue:

    http://www.sharepointboco.com/sharepoint-2007-people-picker-performance-issues/


    MCITP|MCTS SharePoint| SharePoint Performance blog

    Sunday, July 12, 2015 2:26 PM
  • No I haven't it. I search the same user and it gets it quickly.

    I know a little of AD's deployment, but I think that is the same forest. I have 2 domains:

    mycompany.local, netbios name MYCOMPANY

    valladolid.mycompany.local, netbios name VALLADOLID

    Monday, July 13, 2015 11:52 AM
  • The users are coming from both domains?

    If not you can limit peoplepicker to one domain. Check the parameters of this command:

    stsadm –o setproperty –pn peoplepicker-searchadforests

    https://technet.microsoft.com/en-us/library/cc263460(v=office.12).aspx


    MCITP|MCTS SharePoint| SharePoint Performance blog

    Monday, July 13, 2015 12:16 PM
  • Yes, users are coming from both domains. LDAP query seems to be fine. I did same traces and goes well (less than second).
    Tuesday, July 14, 2015 12:12 PM
  • you can execute the following command by specifying both domains and check if your issue is still present:
    STSADM.exe -o setproperty -pn peoplepicker-searchadforests -pv "domain:a.local;domain:b.local" -url http://webappurl

    Remark:
    there is no space between the two domains
    the command is not valid for one way trust

    MCITP|MCTS SharePoint| SharePoint Performance blog

    Tuesday, July 14, 2015 1:15 PM
  • It not solves it. Peoplepicker searches so slowly again. To test it, i created new webapplication with another pool with admin farm credentials. I configured "searchadforests" and no solution.

    I've 6126, 6127 and 6060 events with FimSyncornizationService while profile application incremental syncronization. Could it to be the problem? I don't understand why but I don't know. User profiles have not relation with peoplepicker search.

    Thursday, July 16, 2015 8:51 AM
  • Is it possible to put the logs in verbose mode, reproduce the issue and paste the info here?

    Once you have the logs search for the user name in order to filter the data.

    In this article you can find some useful information: 

    http://blogs.technet.com/b/steve_chen/archive/2011/02/07/poor-performance-on-people-picker-search-in-sps2010.aspx


    MCITP|MCTS SharePoint| SharePoint Performance blog

    Thursday, July 16, 2015 7:34 PM
  • Ok. After some weeks I've tried it again. I have put logs in verbose mode and I saw queries to unknow domains. I used:

    stsadm –o setproperty –pn peoplepicker-searchadforests

    For only one forest and people search goes faster.

    Thanks.

    Monday, August 10, 2015 10:52 AM