After configuring User Profile Synchronization, I found that SharePoint People Search could still not work as the the content source for the user profiles was being denied access.
With some good research, I came to learn that the Default Content Access Account I had set from my search service application was being denied access to crawl and index the sps3://my.intranet.com repository. To resolve this, I granted the default content access account administrative rights on the User Profile Service application as "Retrieve People Data for Search Crawlers" as seen below.
After the above, I did a full crawl, and when again attempted to perform a people search, I was hit by an error on the results as "Property doesn’t exist or is used in a manner inconsistent with schema settings". I went into more research, and I found out that if I edited the People Core Results webpart and under Core Results section, I expand the Display Properties, I checked the "Use Location Virtualization", as seen below, it finally sorted the issue.
Good luck.
With some good research, I came to learn that the Default Content Access Account I had set from my search service application was being denied access to crawl and index the sps3://my.intranet.com repository. To resolve this, I granted the default content access account administrative rights on the User Profile Service application as "Retrieve People Data for Search Crawlers" as seen below.
After the above, I did a full crawl, and when again attempted to perform a people search, I was hit by an error on the results as "Property doesn’t exist or is used in a manner inconsistent with schema settings". I went into more research, and I found out that if I edited the People Core Results webpart and under Core Results section, I expand the Display Properties, I checked the "Use Location Virtualization", as seen below, it finally sorted the issue.
Good luck.
No comments:
Post a Comment