Home > Administration, Sharepoint, WSS 3.0 > Share-point search

Share-point search

A client reported that the search feature is not working on a WSS 3.0 share-point portal. All search queries returned the same following text:

No results matching your search were found.

  1. Check your spelling. Are the words in your query spelled correctly?
  2. Try using synonyms. Maybe what you’re looking for uses slightly different words.
  3. Make your search more general. Try more general terms in place of specific ones.
  4. Try your search in a different scope. Different scopes can have different results.

And an error and a warning kept comming on the server every 5 minutes (after every 5 minutes share-point search service tries to index the share-point sites)

We google the error description but the results did not help – then we google the warning text and were able to find the cause of this problem. Here is the warning that kept on coming every 5 minutes

Event Type:   Warning
Event Source: Windows SharePoint Services 3 Search
Event Category:       Gatherer
Event ID:       2436
Date:            12/26/2007
Time:            3:08:16 AM
User:            N/A
Computer:     AZHAR

Description:
The start address <sts3://dws571210/contentdbid={8a1d4489-b9bd-4ee6-8d24-d8305c6b64f4}> cannot be crawled. 

Context: Application ‘Search index file on the search server’, Catalog ‘Search’

 Details:
          The object was not found.   (0x80041201) 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Following post helped us in finding the cause of this:

WSSv3 Search, Small Business Server & DNS

As per described in the article, when we tried accessing the site from with-in the server, we were not able to access it. As we were not able to access the site using I.E. the crawler was also not able to access the site and hence it was not indexed. The error The object was not found.   (0x80041201) indicates that the site is not found by the crawler.

As a solution to this problem, we mapped a sub-domain http://site1.myserver.com to the existing URL and we verified that the new URL is accessible from with-in the server. Once this is done the site search feature is back up and running

Advertisements
  1. Ray
    August 14, 2009 at 18:54

    The thing that finally fixed this for me was detaching and reattaching the content database for the site.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: