Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

This is an old issue I thought this was a bug in an specific environment after reading a couple of blogs it has made me think again...

The issue is that SharePoint site collections and sites are not correctly picked up by the search index. All the content is indexed but the sites themselves are not associated to the correct contentclass. Prior to SP2 the site collections (SPSite's) are listed in the index under the contentclass:STS_Site and the sites (SPWeb's) are contentclass:STS_Web. The following people seem to have come across this issue and assumed it was just a limitation. I think it was a bug introduced sometime during IU and SP2:

The situation that I have observed to exhibit this 'bug' is:

  1. a site collection or site is based on a publishing template (can be built-in e.g. collaboration portal or custom site template)
  2. SharePoint 2007 with updates post Infrastructure Update - in my situation it was applying SP2 but it might have been one of the culmlative updates after IU
  3. A search pre-SP2 using contentclass:STS_Site as a filter will list all site collections including those based on publishing templates, contentclass:STS_Web will list all sites based on publishing templates
  4. A search post-SP2 using contentclass filtyer as above will return only site collections/sites using non-publishing templates. All other content is availble e.g. documents, lists

Has anyone else come across this?

UPDATE 08/05/10: I have been doing some further testing and initial results look like if you upgrade the problematic site to 2010 then the behavior reverts back to how it should be. i.e. A search with "contentclass:STS_Web" or "contentclass:STS_Site" returns the webs or sites respectively.

UPDATE 02/06/10: As I mentioned above an upgrade to SharePoint 2010 will fix the issue (at least make the STS_Site and STS_Web results appear again) but there is still no fix for 2007. I recently applied the April 2010 CU to a test farm, reset the search index and recrawled and still the results are missing sites and webs from publishing sites. No fix...

Yet another person is also reporting this error in the MSDN forums and the moderator comfirmed the behavior/issue.

UPDATE 17/06/10: I am close to getting a definitive yes from MS support that this is a reproducible bug. Stay tuned...

share|improve this question

5 Answers 5

I am seeing the same issue. A Pulishing Site in SP2 has a contentclass 'STS_ListItem_850' instead of STS_Web (as was in SP1)

share|improve this answer
    
Thanks for confirming you have this behavior. I am very interested to see how many other people have observed this... –  Nick Hadlee Mar 13 '10 at 5:44
up vote 1 down vote accepted

I can confirm that this has been verified as a product bug by Microsoft Support. To quote the final email response on this issue:

Caused by product bug. Resolved with workaround.

Post your best workarounds if you have them...

share|improve this answer
2  
Just to bring this topic back from the dead, this bug appears to have been fixed on installing SP3. –  Mark Jan 20 '12 at 16:08

Just got bitten by this too :(

share|improve this answer
    
This does not really answer the question. If you have a different question, you can ask it by clicking Ask Question. You can also add a bounty to draw more attention to this question once you have enough reputation. –  John Chapman Oct 17 '12 at 14:18

'STS_ListItem_850' does the job

thank you

patrick

http://patricklamber.blogspot.com (SharePoint, ASP.NET, Project)

share|improve this answer
1  
That doesnt account for the change of behavior between SP1 and SP2. STS_ListItem_850 really represents a page in a pages library whereas STS_Web means an SPWeb. The two are not the same thing... –  Nick Hadlee Apr 15 '10 at 10:03

very interesting - we got the same curious appearance when changing our sharepoint farm to windows server 2008 r2 64 bit including cumulate update from february 2010. But what is the workaround mentioned in microsoft's email? Didn't they give you a solution?

Greetings

Steve

share|improve this answer
    
Steve although I said it was caused by SP2, it seems that any cumlative update after SP2 will also cause the issue (I think it is because all the CU's include all updates up to that point including SP2). Unfortunately MS didn't provide any workarounds. It will depend on what you are doing with the search service. I was trying to get a list of sites a user has access to and ended up using the User Profile Service to get a list of site memberships [msdn.microsoft.com/en-us/library/…. –  Nick Hadlee Jul 2 '10 at 21:36

Your Answer

 
discard

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.