SharePoint Blogs / SharePoint University
SharePoint Blogs and SharePoint University - all in one place!
Need SharePoint Training? Attend a SharePoint Bootcamp!

Please delete cookies related to sharepointblogs.com and sharepointu.com to resolve login issues!

MOSS 2007 People Search Issues

Issue:

Unable to search for People within MOSS 2007.  Specifically, the People Scope within your SSP Search Settings shows 0 people after successfully importing User Profiles from your LDAP service. I finally resolved the people search issue I have encountered since I first installed SharePoint, so I have decided to document it for someone else that might have the same issue. The main issue was that I could not search for people from SharePoint sites, however, there were no issues in importing User Profiles as indicated by over 3000 user profiles in the User Profiles of my shared service.  When I went into the Search Settings, and viewed the Scopes of my SSP, I realized that I had 0 People included in my People Scope. I found several posts where people deleted and recreated the People scope, but that didn’t work for me. So, in an over simplification of what is going on, I tried to think about what SharePoint is doing: 
  1. Importing User Profiles into user profile database
  2. Indexing the User Profiles to make them searchable 
Okay, so it’s not an issue with the import, so SharePoint isn’t indexing the content properly; why? 
  1. Did I have a domain account that didn't have the correct permissions to the database where the user profiles were imported? (Big Disclaimer:  My friend Milan Gross recommended looking at  permissions as a likely culprit, and while I don’t believe this was ultimately my issue, I would like to say that I have been diligent in following the SharePoint Administrator’s Companion)
  2. Did I configure something incorrectly?
  3. Did SharePoint configure something incorrectly?
  4. Is SharePoint broken? 
The clue I found that pointed me in the right direction was in the crawl logs for the Local Office SharePoint Server sites under search settings.  I found the following error message: sps3://servername:port#
Error in PortalCrawl Web Service A similar message was also in the windows application event log. This led me to a few posts online including this one by Sheetal Jain:http://office12.blogspot.com/2007/05/people-search-and-my-site-ssp.html While the post itself didn't solve me problem, it pointed me in the right direction, in that it mentioned the need to create a dummy site collection at the mysite root.  As Sheetal put it, not having a site collection at the my site web application root caused a “stomach ache for SharePoint Indexer.” As a lessons learned, here are a few things I tried to modify based on different threads I found; none of which worked.  After I made each setting change I re-imported all profiles, and performed a full crawl on Local Office SharePoint Server sites. 
  1. Modified “sps3://servername:port#/”  in Shared Services Administration: Shared Services > Search Settings > Content Sources > Edit Content Source of Local Office SharePoint Server Sites to “sps3://servername:port#/mysite”.
  2. Create Site Collection on the MySite web application root “/” managed path as a MySite Host under the Enterprise Tab of the Site Collecction Templates.
    • This seems to be what Sheetal was referring to, but I seemed to have an issue with it in that I got a permission error when creating a site collection on the root of the web application.  After the error I could not repeat the step of creating a My Site Host site collection on the root.  I even went to delete the site collection on the root, but it wasn’t in the site collection list to delete, and the only kind of site collection SharePoint would let me create now was a site collection under the sites or personal managed paths. Oy! 
  3. Delete the MySite “mysite” managed path. This did nothing, as expected, but was a last resort.
  4. Undid step 1.
  5. Changed MySite Personal Site Services provider location in SSP. a.       I changed it from http://servername:port#/mysite/ to http://servername:port#/, as “mysite” is the Relative URL I entered when I created the SSP.  
After none of these steps worked I started creating new Shared Service Providers, just to see what would happen.  I haven’t played with SharePoint 2007 Administration too much and I was still a little reluctant to create a bunch of SSPs.  DON’T BE!  It is super easy to create them change web site associations, and delete them.  It was almost fun ;-).   When creating my first alternate SSP I left everything as the default setting, imported the user profiles, crawled the Local sites, and poof, User Profiles were indexed.  I figured there was  probably a permissions issue when I initially configured SharePoint, so I deleted the MySite under the new SSP and moved all the web applications from the old SSP to the new SSP, and poof, my indexed profiles were gone!  Hm…  What is happening?  Several more SSPs later I narrowed it down to one setting, that appears to be throwing something off on SSP creation, which is the relative URL for the My Sites. Every time I created a SSP with a relative URL for the MySite web application the Indexer was not able to index the User Profiles.  I was then  unable to figure out what settings needed to be changed to get it to start working again.  

So, it appears that ultimately I had the same problem as Sheetal where the SharePoint indexer is not able to index the imported User Profiles because it is not able to access sps3://servername:port#, however, I resolved it is very different.

Resolution:

1.       I created a Brand new SSP

2.       As always, I created a separate Web Application for the SSP Web Application and the My Site Location.

3.       I left the Relative URL BLANK!

4.       I made the new SSP the default SSP.

5.       I moved all my existing Web Applications to the new SSP EXCEPT the old SSP Administration site host and the old MySite web application, as I could not resolve the issues with the old MySite web application.

This worked well for me because I was still testing a SharePoint installation and there were only two personal sites created; mine and one other user’s.  This is probably not the best solution for someone that has already implemented SharePoint across an enterprise.

If anyone else knows of a better or simpler solution, I would love to know about it!

As this is my first MOSS 2007 Blog post, I can’t wait to look back on it a year from now and laugh at my MOSS naivety.


Posted 07-13-2007 11:02 AM by mdcamp00

Comments

Ramesh Jeyabal wrote re: MOSS 2007 People Search Issues
on 07-16-2007 6:51 AM

Hi Camper,

here is my solution or view about your porblem:

Problem:

Search in people search still doesn’t work even after crawling

Assumption:

* User Profile imported successfully with some user  profiles.

* "People" scope is present in the Search settings

Cause:

By default, the SSP will use "Sharepoint - 80" as the "My Site" web application.

(Shared Services Administration: SharedServices1 > My Site Settings )

This "Sharepoint - 80" web site may not be started since "Default Web Site" web site also uses port 80.

Resolution:

* Run inetmgr.exe

* Expand "Web Site"

* Stop the "Default Web Site" which is using port 80

* Start the "Sharepoint -80" which is used as My Site web application by the SSP

* Start crawling

Once the crawling is over, people search will show results.

Hope this may help you...

Gavin Guinane wrote re: MOSS 2007 People Search Issues
on 07-23-2007 9:48 AM

Super, this last option worked for me thanks.

effendi wrote re: MOSS 2007 People Search Issues
on 07-25-2007 2:25 PM

Hello,

i have the same problem with the people scope. The solution explained by gavin will not work in our landscape. My site is running on port 80.

I have the same problem on other scopes.

For example:

In the administration i defined a content-source which was successfully crawed (in crawl logs they are moren than 500000 entries.

But if i look into the scopes i found only 80 items!!!!

On the other had a look to the search site. In the assigned scopes from the central administration i see 22000 items was available for the same scope?

Dave wrote re: MOSS 2007 People Search Issues
on 07-26-2007 9:52 PM

Hmm, similar issue. No errors in logs, but the people scope is showing a 0.

Mysites is running under port 81.

Sharepoint is running under port 80.

I have deleted and recreated the scope, but still the same.

HELP

Dave wrote re: MOSS 2007 People Search Issues
on 07-26-2007 10:50 PM

ok, I found my issue. I had inadvertently removed the SPS3:// search item. Put that back in, did a full crawl and now all OK!

Didier wrote re: MOSS 2007 People Search Issues
on 08-08-2007 7:58 AM

Hi Dave, I've been the same problem... and I've do the same procedure .. AND WORKING !!! Thank's !

Russell wrote re: MOSS 2007 People Search Issues
on 09-09-2007 1:21 PM

Does anyone know how to delete all imported user profiles in MOSS 2007 all at once?  My company has over 100,000 user profiles available in the LDAP directory services.  I accidently imported all of them before I did my research on this!!!  

I want to delete all of them and start over with a more defined search base in LDAP that SharePoint will only grab the profiles in a particular sub organization.  I now have the defined search base more defined although i just need help with deleting them all in bulk so i dont have to do it one by one.  

Any ideas??  Thanks :)

M Fry wrote re: MOSS 2007 People Search Issues
on 09-11-2007 3:45 PM

Dave,

what do you mean by "I had inadvertently removed the SPS3:// search item. Put that back in, did a full crawl and now all OK!"?

How do i do that?

Aaru wrote re: MOSS 2007 People Search Issues
on 10-04-2007 2:50 PM

Hi,

Actualy My problem is I have imported successfuly from LDAP all the User profiles into MOSS.Before that I have some My site user profile also.If i try to view the user profile,Iam able to view both(LDAP & My site user profile)

But If I try to do people search its indexing only my site profile not the LDAP profile.

Any idea why LDAP profile is not indexing in my people search?

Thanks in advance for any insight,

Aaru

Lola Flippo wrote re: MOSS 2007 People Search Issues
on 11-07-2007 9:34 AM

Great Site! This worked. Thanks!

Anonymous wrote re: MOSS 2007 People Search Issues
on 04-30-2008 9:56 AM

Might want to mention that this approach will remove all audiences also.

Cole DeWitt wrote re: MOSS 2007 People Search Issues
on 08-27-2008 11:56 AM

I spend the money and contacted Microsoft on this one and found that if you have the primary web app set to SSL (443) then to search people content you must set the search start address to

https://sitename

sps3s://sitename

Sean wrote re: MOSS 2007 People Search Issues
on 09-11-2008 1:04 PM

Thanks Cole that helped.

Kurt K wrote re: MOSS 2007 People Search Issues
on 10-20-2008 6:22 PM

Well, heres what fixed it for me. I deleted and recreated the SSP, imported the users from AD...still didnt work.CRAP!  I then logged into my portal site as a farm admin, decided to create a mysites page (mysites is disabled for my  particular farm, but that doesnt stop admins), I then re-ran the import and the crawl...POOF!...looked in the scopes page in Search administration and there they all were.

I thought this may have been a fluke, but it also fixed my DEV farm as well. Go figure. Just create at least 1 mysites site and that may be all you have to do!

Pradeepti wrote re: MOSS 2007 People Search Issues
on 11-11-2008 4:09 AM

Hi,

Need help in customizing people search.

We have imoprted profiles from our Active Directory and are able to search people based on email,name,department.

We do not have data for Skills and Responsibilities in our Active Directory profiles.

We have updated profiles for Skills and Responsibilties at Sharepoint using MyProfile option at MySite.

What customization we have to perform in order to include the data for Skills in the search.

H

Jakob Flygare wrote re: MOSS 2007 People Search Issues
on 11-24-2008 8:40 AM

Hi,

We have the same issue:

We need to customize the User Profiles datasource to include skills and responsibilities as well as other parameters such as telephonenumber and initials,

so that these fields are searchable within the people-scope. We are not using My Site but AD and other external datasources.

How can we do that?

Any ideas on how to customize the People search WebPart or references?

rosen wrote re: MOSS 2007 People Search Issues
on 01-08-2009 6:44 AM

Hi All,

I was having the same issue with indexing the User Profiles to make them searchable in Sharepoint and I could not search for people/users from any SharePoint sites.

Scenario:  You tried to search for Users using the People tab on your Intranet/Portal/Site Search Page and nothing is returned.  Then you tried to run the full (or incremental) crawl process for "Local Office SharePoint Server" but it  failed to index the host site that hosts all your users personal sites or it simply failed to crawled the My Sites site.

I was able to fix this problem by doing the following steps on my Sharepoint Test Environment:

- Created a new web application for My Sites (this could be any name you want) and used port 80 and a Host Header (e.g "mysites") . Sharepoint created my new web application as "http://mysites/">http://mysites/"">http://mysites/">http://mysites/"

I noticed in "My Site Setting" page, by default that SSP is using "Port 80" for the Preferred Search Center (ex. servername/.../Pages), that is why I used Port 80 for My Sites web application above.  

- Then, created the Top-Level Root Site for the new web application  (http://mysites/">http://mysites/) above, but here's the catch, when filling out the "Create Site Collection" page, in the "Web Site Address" section, the URL I used was "http://mysites/">http://mysites/"">http://mysites/">http://mysites/" that is the root level of the site collection, didn't select .../sites/, then I selected the "My Site Host" template for the site template, and selected "Personal Site" for Quota Template

- While waiting for the new Site Collection creation to complete, open the file "hosts" which is located in "C:\WINDOWS\system32\drivers\etc" ,  this file contains the mappings of IP addresses to host names in your farm.  I mapped the new top site (mysites) created above by adding a new entry in this file, you will need your IP address and host name, then save the file with your changes.

- After the new empty top-level site was created successfully, I went  to "My Site Settings" in Shared Services Administration, in the "Personal Site Services" section, Personal site provider, I entered "http://mysites:80/"">http://mysites:80/" to designate the URL of the site to host personal sites that users will create within the site collection.  Then, in the "Personal Site Location" section, in the Location box, I entered or used "personal" (this can be any location name you like) which was eventually added in "Defined Managed Paths" in SCA Application Management for my new web application (http://mysites/">http://mysites/) above.

- Browsed the new site (http://mysites), and on the default page, I clicked "Set as My Site host"

- Started a full crawl again and the process didn't have any errors and successfully indexed all users profiles and data, and when I searched for people using the People Tab, it eventually returned some results.

I hope the preceding procedures will give you some help or tips.  (the above set of steps may be just one of the resolutions to solve the issue on People search and indexing)

Cheers!

rosen wrote re: MOSS 2007 People Search Issues
on 01-09-2009 12:13 AM

errata for my above message, the following texts:

"http://mysites/">http://mysites/"">http://mysites/">http://mysites/"">mysites/.../"  are typos.

It should only be read as "http://mysites/

Add a Comment

(required)  
(optional)
(required)  
Remember Me?
Need SharePoint Training? Attend a SharePoint Bootcamp!
Posts (c) their respective authors. Everything else (c) 2009 SharePoint Experts, Inc.