J
jimpuls
We have two Microsoft Project Server / Microsoft Office SharePoint 2007
systems, one development and one production. Our issue is with the “Select
People – Webpage Dialog†or People Picker function. Both systems operate in a
simple single AD domain of about 300 users. For test purposes we have put
together a very simple SharePoint list with a title field and a name field.
When we try to add a new item to the list by using the search function for
the name field, the development system returns results in a second or so,
while the production system has become slow, taking about 25 seconds to
return.
The browse display or search function will sometimes find bogus names,
former employees which are as far as I know not in Active Directory at all.
Rather than listing the display name as “last, firstâ€, they are listed as
“last; firstâ€. These names are people who do exist in the Project Server
resource pool and marked inactive. Not all inactive resources are returned by
a search, but the results are consistent: the same names are returned each
time for the same search criteria.
The check name function works a bit differently. A good name will be
verified in a second or so, while a bad name, whether it was returned by the
search function or not, will fail verification after about 25 seconds.
Where is the People Picker looking for names? Could they be coming from the
Project Server resource pool? What might be going wrong? Any suggestions for
diagnosing or fixing the problem would be gratefully received.
Thanks,
Jim
systems, one development and one production. Our issue is with the “Select
People – Webpage Dialog†or People Picker function. Both systems operate in a
simple single AD domain of about 300 users. For test purposes we have put
together a very simple SharePoint list with a title field and a name field.
When we try to add a new item to the list by using the search function for
the name field, the development system returns results in a second or so,
while the production system has become slow, taking about 25 seconds to
return.
The browse display or search function will sometimes find bogus names,
former employees which are as far as I know not in Active Directory at all.
Rather than listing the display name as “last, firstâ€, they are listed as
“last; firstâ€. These names are people who do exist in the Project Server
resource pool and marked inactive. Not all inactive resources are returned by
a search, but the results are consistent: the same names are returned each
time for the same search criteria.
The check name function works a bit differently. A good name will be
verified in a second or so, while a bad name, whether it was returned by the
search function or not, will fail verification after about 25 seconds.
Where is the People Picker looking for names? Could they be coming from the
Project Server resource pool? What might be going wrong? Any suggestions for
diagnosing or fixing the problem would be gratefully received.
Thanks,
Jim