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!!!!
I’m getting the exact error…however, I think that the site is not finding itself when the crawl happens…changed to http://localhost/ didn’t do any good because we have our IIS blank for default site.
The following apples to MOSS only…
Fist undo what you did, (the localhost setting).
Then download http://links.isaacblum.com/ocmdd SSL Diagnostics Version 1.1 (x86)
run the application, and take note that not all of your ssl certificates are working. if this is true, you can use ssl diag to create a self signed certificate.
Google “selfdiag.exe /self” if you need more info. Let me know if this turns out to be your problem.
Good Luck
Hello Isaac,
I also face the exact error. However, my website is http://.domain.com. I still get the same error. Could you please help? However I have another site on the same server with the url http://:80 and the search works there without any problem. Do you think the search would not work on sites similar to the former url?
Well nothing is coming to mind…
But I’m happy to help. I have a few questions….
What is the server layout of your farm? i.e.: single server or multi server, etc…
MOSS or WSS?
What is the authentication method for this site? What is listed for the default zone?
Thanks
Both the DB and Web site are in separate servers. It is a WSS3.0 based site with DB on SQL 2005. The authentication is “integrated Windows Authentication” The default listed zone is “Intranet”. The search service and the IIS application pool use a common service account which has admin access to the servers.
You must have a zone listed “default”. The possible zones are Default, Intranet, Extranet, Internet, and Custom. If you only have Intranet, then search won’t work correctly. You should extend your application to the default zone. You will need to temporally change the URL of the intranet zone to something else other than what you want your application to respond to, and then create the default zone with the URL you want.
Let me know if you need help with this procedure or if you have any questions with that I’m suggesting. Good Luck!!