SharePoint Search Stops Working with Event ID 2436

My Search Server does not like me… search has stopped working *again*.  Another mysterious error in the event log each time a search is attempted (either incremental or full):

Event Type: Warning
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 2436
Date:  29/07/2008
Time:  2:19:11 PM
User:  N/A
Computer: [deleted]
The start address <http://deleted> cannot be crawled.

Context: Application ‘SharedServicesProvider’, Catalog ‘Portal_Content’

 The parameter is incorrect.   (0x80070057)

For more information, see Help and Support Center at


Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 2424
Date:  29/07/2008
Time:  2:19:11 PM
User:  N/A
Computer: [deleted]
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

Context: Application ‘SharedServicesProvider’, Catalog ‘Portal_Content’

For more information, see Help and Support Center at

I tried the following:

  1. Start a full crawl on the content source – FAIL
  2. Ensure the search services for Windows SharePoint Services Search and Office SharePoint Server Search used the same search account using Central Admin/Operations/Services on Server (they didn’t before) then start a full crawl – FAIL
  3. Reset all crawled content via Search Admin and full crawl – FAIL
  4. Stop and start the Office SharePoint Server Search service – SUCCESS

This seems to have fixed the issue for now, but I’m concerned that I will just keep having the same problem ever couple of days.  My automated full crawl happens every night at 3am, so I’ll just have to keep an eye on the search logs I guess…

UPDATE: Unfortunately, Search Server has failed again 😦  I have received the same problem and the same error.  Some more info: the catalog size is about 60,000 documents, and it does seem to occur on my nightly crawl at 3am.  As soon as that happens, subsequent crawls fail and after 3 days, all content disappears.  Guess I’ll have to open a support incident.


UPDATE2: At last!  After some exhaustive work with an MS Support Engineer, it seems that Search Server Express 2008 is having problems when more than one crawl is occurring on different content sources.  We have two sharepoint sites, and search server is set up to crawl both.  My main site is crawled every 10 minutes, and the second site every 30 minutes on incremental crawls.  Therefore they overlapped, and the second site was always failing its crawl.  I have since turned off the incremental (not needed – now only has once per day at midnight) and the errors dried up.  Hopefully this is the end of it!

According to the MS doco, you “may experience problems” if you server hardware is not powerful enough to support multiple content crawls at the same time.  Problem experienced – check!  I am not sure if this is a bug in Microsoft Search Server Express 2008, but I haven’t got any event log errors at all since turning off the secondary site content crawl.  Let’s hope that the end of it!

The Engineer is doing some additional research to try and find out why this causes Search Server to drop out its content.  My  hunch is that there is some randomness for which content crawl occurs first.  For example – if the secondary site crawl occurs first, it would stop the first crawl from working.  If that happened a couple of times, then search server might think the primary site is gone, and happily delete all the indexed content.  Just a guess though…


2 Responses to “SharePoint Search Stops Working with Event ID 2436”

  1. Search Administration Completed Crawls Shows Zero Success « Back in Hack Says:

    […] Completed Crawls Shows Zero Success This is partly related to a previous post on “Sharepoint Search Stops Working With Event Id 2436“.  If you are diagnosing why no results are being returned, one place to check is the Shared […]

  2. suraj Says:

    One of the main reasons for this error is not enough permission to access the search database. If you have experienced that suddenly your wss site stopped searching and gave no results, you need to check one thing before changing any settings to your wss services.
    Most people including myself forget to check what updates have been made to the windows server since last service failure.
    Windows 2003 tighten the security with every security patches and service packs to eliminate possible attacks to the server. This can cause problems to existing services as well. With service packs windows 2003 restricts loopback attacks.
    To solve this problem disable loopback restriction. Read OR just download the application fix and run it on the server. I believe this very common problem and doing so will fix many situations like this.

Leave a Reply

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

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

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s

%d bloggers like this: