Fixing event 2424 after installing WSS 3.0

Fixing event 2424 after installing WSS 3.0

Are you getting error messages like this?

Event Type: Error
Event Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 2424
Date: 7/10/2007
Time: 7:25:47 AM
User: N/A
Computer: SBS
Description:
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

Context: Application ‘Search’, Catalog ‘index file on the search server Search’

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

If so, here’s how to fix it.

Update: One minor problem — the fix doesn’t seem to work. I’m still getting the errors, along with several others. More information to follow once I’ve got it figured out ….

Posted in All, SBS, SharePoint, Software, Technology on Jul 11th, 2007, 10:56 am by David Schrag   

5 Responses

  1. shannonr
    August 14th, 2007 | 11:15 pm

    Hi, did you manage to find a fix for this? I get this error message regardless of whether I do a stand alone install or install the database to a different SQL server, and it seems to be stopping the search service from functioning.

    Any insight would be greatly appreciated.

    Thanks,
    Shannon

  2. August 21st, 2007 | 10:31 am

    Any updates to this? I have this same exact issue that has come up on 1 server that I can’t resolve. I can force the error to happen on another server and fix it by a permissions problem, but that doesn’t work.

    I’ve even tried to use the main Sharepoint Admin account (which the app pool uses) as the search service account, which DOES have access to the DB server, or it wouldn’t be able to make the site even!!

    I’m totally lost with this one particular server.

  3. jackinthegreen
    August 23rd, 2007 | 12:45 pm

    Me three;

    I tested it with my own LAN account since I’m admin on all the servers involved and still no go. This really sucks, something as major as loss of search on a wss 3.0 business intrsnet site and MS is typically out to lunch with their solution. Oh well, my own fault for adopting wss as the “solution” for our intranet, I guess; thanks in advance for any info(!!) in any case..

  4. jackinthegreen
    August 23rd, 2007 | 1:45 pm

    OK, found an obscure post on a list where the guy found that using the same account for both the search service and the content browser service (both updatable on the same config page) worked, and that worked for me as well; halleluyah (spelling?) cheers

  5. January 18th, 2009 | 1:06 pm

    […] a week on this and finally have a fix…(not really what i want to do but it works) thanks to this http://davidschrag.com/schlog/168/fi…talling-wss-30 I used the admin account for both and i was instanly in business! "eastcoasttech" […]

Leave a reply