Event 2436 returns no search results

All of a sudden the search stopped working on a MOSS 2007 server. Looked into Event Viewer and found the error message:

Event Type: Warning
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 2436
Date: 24-04-2009Time: 13:29:31
User: N/A
Computer: DKxxx001
Description:The start address <http://xxx> cannot be crawled.
Context: Application ‘SharedServices1’, Catalog ‘Portal_Content’
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)

No changes have been made to the server, no accounts have been locked out or password has changed. First thing I did was to restart the Office Sharepoint Search Service. Did not help. Re entered the password for the Default Content Access Account. Did not help. Googled it. Found an article on Microsoft that you should enter the following in your registry:

1) Click Start, click Run, type regedit, and then click OK.
2) In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsa3)
3) Right-click Lsa, point to New, and then click DWORD Value
4) Type DisableLoopbackCheck, and then press ENTER
5) Right-click DisableLoopbackCheck, and then click Modify
6) In the Value data box, type 1, and then click OK
7) Quit Registry Editor, and then restart your computer (now that I did not have to do! It worked immediately)

That helped!! Now the full crawl is crawling and all is well. Now I can really enjoy todays after work in the sun :=)

Leave a Reply

6 Comments on "Event 2436 returns no search results"

avatar
  Subscribe  
newest oldest most voted
Notify of
Lise
Guest

Hi Angelica!

Thanks for posting, great to hear that it helped=)
Take care,
Lise

Angelica
Guest

Thx a lot, it solved a search-problem on a customers intranet!!!

Lise
Guest

Hi Doug,
Great to hear!!
Yeah I know how it is to spend all those hours troubleshooting….
Thanks for posting,
Take care
Lise

Doug
Guest

Hey Lise, thank you so much for the post…this did the job. I actually spent hours and hours on this, primarily because in the Application event logs, Event Id 2424 came up following Event Id 2436. Therefore I followed all the fix suggestions for 2424 and not 2436…There are a zillion posts in forums and blogs about this happening… for us it was because of installing WSS 3.0 Service Pack 2. Thanks again!

Doug
Guest

This comment has been removed by the author.