locked
People search (by GUID) giving 'User not found' RRS feed

  • Question

  • When I go to the people search off of our landing page, put in an account name, it returns the proper person and when you hit that link for the person, the resulting page gives 'User not found'. Specifically:

    http://mysites.etc.com/Person.aspx?guid=xxxxx-xxxx-xxxx-xxxx-xxxxxx

    However, if you go to an item that has that exact same person in it (for instance to a list item and click on their 'Created By Joe Shmoe' link) it comes up just fine. Specifically:

    http://mysites.etc.com/Person.aspx?accountname=Domain%5Cjoe%2Eshmoe&Source=....

    So, when using the GUID, it doesn't show up and when using the account name for the Person.aspx page it works fine. When I go to the SSP hosting the mysites.etc.com and view the profiles, I can extract a proper GUID directly from the profile, replace it, and it works like a charm.

    I've tried to do a detach and reattach of both the landing site and the MySite databases with no avail. Also note that I've done full imports of both the people search and the profiles across all SSP's and there is only one search crawl with the sps3://etc protocol.

    Farm and setup info

    Farm consists of 5 SSP's for different searches and data that needs to be separated, and one of these SSP's consists solely of the MySite data for all of the SSP's. This is a very large farm, and alot of custom work has been done on the host site SSP (but not the MySite SSP), so deleting the SSP it without trying to figure it out is only my final option. I migrated about 10 months ago, and my migration strategy for the MySites was simply to do an SQL restore of the database (including preparetomove, etc).

    Any help is greatly appreciated!

    -Andrew

    Monday, November 1, 2010 5:19 PM

All replies

  • Additional information...

    So SSP#1 hosts the main site and SSP#2 hosts the mysite data. The table within Userprofile_Full within SSP#1 is the one holding onto the improper GUID that gives 'User not found' and in the same table within SSP#2, the table gives the proper GUID that works.

    Monday, November 1, 2010 5:32 PM
  • Looks like you have a customized Search Results web part which is rendering the bad link. You can easily modify the rendering results and would have the ability to have custom URL. When the search results are returned they include the Username which you can use to build the search results web parts with custom links.


    Sameer Dhoot
    My Blog : http://sharemypoint.in/

    Did I answer your question? If YES, Mark as Answer. If NO, reply with details to continue dialogue.

    Tuesday, November 2, 2010 5:42 AM
  • Sameer, thanks for the reply, but in my troubleshooting i've created a completely OOB web app with a basic team site and the default People search is still using the GUID for the search results...so i think this is the OOB method for the People search to return results.

    I can see exactly where the issue is coming from, and it stems from the 'Userprofile_Full' tables between the two SSP's not having the same GUID's. Although I'm not sure if they are supposed to have the same GUID, which is where I'm lost...how should the People search in one SSP return results from an SSP which is hosting the MySites if the GUID's aren't consistent between the two?

    Tuesday, November 2, 2010 3:54 PM
  • Well, the final 'work-around' that I have in order to get this fixed is to modify the XSLT for the search results pages. Note that it is the OOB results pages giving the error, and i've only modified it thereafter I couldn't find a solid solution.

    If anyone happens to find a more direct solution than this, please post it!

    Thursday, November 4, 2010 6:50 PM
  • Your search index is unsynchronized with user profiles. Just do the full crawl on user profiles.
    Thursday, February 10, 2011 6:56 AM