Event ID 2436 Source Windows SharePoint Services 3 Search
| Event ID | 2436 |
| Source | Windows SharePoint Services 3 Search |
| Type | Warning |
| Description | The start address <address> cannot be crawled. Context: Application "Search index file on the search server" Catalog "Search" Details: <error> <error code>. |
| English, please! | This information is only available to subscribers. An example of English, please! |
| Comments |
Miguel Cervantes
Error: Access is denied (code 0x80041205). This may be recorded in certain conditions (specific hotfixes are applied) because Windows Server 2003 Service Pack 1 (SP1) includes a loopback check security feature that is designed to help prevent reflection attacks on your computer. M971382 provides information on registry changes that have to be made on all Web Front End servers and any Index server configured to crawl itself in order to workaround this problem. Anonymous I was having a similar issue - getting access denied messages and to check the default content access account. After trying nearly everything possible, I finally narrowed down the culprit to a Microsoft Security Patch - MS06-068 (M957097). We have 2 web frontends and a dedicated app server for search and the local authentication was failing after installing this patch. Just turned off the loopback check on the app/search server, rebooted, and search was back in action. Anonymous In my case, I came across a blog entry which led to the solution of my problem. See the link to "SharePoint 2007 Search" to read it. Anonymous In my case, the Authentication Methods was set to Basic. Once changed to Integrated Windows authentication, the search began working. Anonymous In our particular instance, we had configured two front end web servers with a third dedicated search server for content and indexing. At some point, the MOSS Website was disabled on the search server which caused events 2436 to be displayed in the event log. Enabling the website on the same port as the primary web servers allowed content to crawl as expected. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! Anonymous From a newsgroup post: "I changed the internal URL for our site to something more user friendy than the computer name and then my eventlog was full of the message 'The start address <sts3://intranet/contentdbid={8ad03df4-8d1f-4344-86df-6ebe0bc9a057}> cannot be crawled' Context: Application 'Search index file on the search server', Catalog 'Search' Details: Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. (0x80041205) The error was fixed by putting the old name back and adding the new name to a different section in alternate accessing." Ionut Marin From a newsgroup post: "There are some particulars that are not documented very well when setting up your search settings. The search engine will only crawl on a site that is the default zone. If the default zone is secured (https), search will not return any results and you will see this error in the application log. To fix this, create and extend the current web application with a new site. The default settings will suffice for everything except the zone. Change the “Zone” to Internet or Custom. This new site will be the site the search service uses to index. Bear in mind the site uses the same content as your public SharePoint site. After creating the site, go to Operations > Alternate Access Mappings and change the “Alternate Access Mapping Collection to your main SharePoint site collection. Then click “Edit Public URLs” and swap the URLs in the fields such that the Default zone is the new “unsecured” SharePoint site. The secure site can be in any zone except the default zone. Now when the search indexer runs, it will use the default zone site (the new unsecured site) to crawl. That’s it". See the link to "www.kevincornwell.com - Windows SharePoint Services (WSS) 3.0 Search Setup Notes" for the original thread. See the link to "WSSv3 Search, Small Business Server & DNS" for a different situation regarding this event. Anonymous See the link to "Google Thread" for an interesting new post on this issue. |
| Links | Google Thread, www.kevincornwell.com - Windows SharePoint Services (WSS) 3.0 Search Setup Notes, WSSv3 Search, Small Business Server & DNS, SharePoint 2007 Search, M957097, M971382 |
| Search | Google Web - Microsoft Support - Bing - EventID.Net Queue - More links... |
| Custom search | The custom search information is available to subscribers only. |
| Feedback | Send comments - Notify me when updated |
| Print version |