SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to create a "Search for Users" function that is supposed to hit the SharePoint User Profile Store (running SP2010 Enterprise). However, that function takes up to a Minute to search, which is WAY too long. I found a weird 50-Step Process flow diagram that doesn't make much sense since I'm not using Foundation but the full server, in which case searching should be a simple SELECT against the Profile Database and return in a few ms?

share|improve this question
I am not clear why, but I have found the same, also using the Enterprise version of SharePoint. – Andy Burns May 9 '11 at 15:20
Where is your Domain Controller located? – SPDoctor May 16 '11 at 13:02

My guess is that it is the link to Active Directory that is the problem, particularly if your Domain Controller is not near (in the sense of network latency) to your SharePoint server(s).

share|improve this answer
That's interesting. Yes, some domain controllers are not near (multiple domains in the forest), but I don't understand why it hits AD at all when there is the user profile database right there for sharepoint to query in a millisecond or two? – Michael Stum May 16 '11 at 17:47
I think in essence the profile is holding attributes of the user but it is still relying on AD (or other authentication provider) to supply the identity, and I assume this is what the API you are calling is iterating over. The way user profiles work is a bit of a mystery. – SPDoctor May 16 '11 at 18:50

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.