Event Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 2436
Date: 6/2/2009
Time: 1:15:04 PM
User: N/A
Computer: XXXXX
Description:
The start address <sts3://XXXXX:2000/contentdbid={5e4c7cac-eb31-42a6-b88d-6596d285532e}> cannot be crawled.
Context: Application ‘Search index file on the search server’, Catalog ‘Search’
Details:
The object was not found. (0×80041201)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
OR
Source: Windows SharePoint Services 3 Search
Category: Gatherer
Event ID: 2436
Description:
The start address <sts3://[site url]/contentdbid={[GUID]}> cannot be crawled.
Context: Application ‘Search index file on the search server’, Catalog ‘Search’
Details:
The object was not found. (0×80041201)
For this error I found many different posts regarding this issue, and none really solved my problem. Example posts: http://www.sharepointblogs.com/mcotw/archive/2007/01/20/wssv3-search-small-business-server-amp-dns.aspx or http://www.thesug.org/Blogs/annw/Lists/Posts/ViewPost.aspx?ID=2 Both great resources for information usably.
My issue ended up being with the alternate access mappings. Changed the mapping from the http://computername:2000/ to http://localhost:2000/, solved the issue. Now I wouldn’t say this would be acceptable in most cases but it worked for this client. I would of recommended something like http://ssp.domain.com/. Anyway I would check your mappings first before trying the other solutions.
Need help?? Shoot me a line!!!!
