I cannot seem to get WSS 3.0 Search working. I have the service started, but
I keep getting this error in the even log:
Event Type: Error
Event Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 2424
Date: 1/23/2007
Time: 10:46:25 AM
User: N/A
Computer: IIS-IN01
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.
I have looked at this KB article:
http://support.microsoft.com/default.aspx/kb/927012. ; It still does not help.
I am running WSS 3.0 in a farm (single server) because the SQL server is on
another machine. I have created a domain user for use with the service. The
domain user has access to the SQL server. I have even tried my account. I set up the application pool and the search service with my domain account. My account is a local admin on the SharePoint site and a SQL admin on the SQL server.
Any help would be appreciated. Thanks.

WSS 3.0 Search Error
DrJazz
Hi,
Yes, I have made the account an administrator (for testing purposes) on the Front End server, the Database Server and SQL itself.
THanks,
Shannon
Jorne
Have you specified the server's name containing the database system here
Central Administration / Application Management / Content Databases / click on the database name (typically WSS_Content).
Halfway down there is a "Search Server" section which must contain the server name.
Mike Walsh
charret
Hey I have the same problem. Can you post the article where you found your solution
Thanks
Steve
todd_bulky
Does the user you have specified to run in the search have access to the content databases
Dave
Davids Learning
Has anyone seen any good documentation on setting up WSS search If the Service Account and the Content Access Account are supposed to be the same, that is fine, but I'd really like to see more details. It clearly states beside the Content Access Account configuration "For proper search functionality and information security, do not use an administrator account, and do not use accounts that can modify content." Yet, by definition, the Service Account is going to require some level of elevated permissions. I took a quick peek at an MS online virtual lab, which used Administrator for both accounts. That seems inappropriate to me. If anyone has better information, I'd appreciate it.
Thanks!
Utkarsh Shigihalli
Information about Service accounts including Search can be found in this article:
http://technet2.microsoft.com/windowsserver/WSS/en/library/89e4c579-5720-45e0-917e-abeb95266c3e1033.mspx mfr=true
Please let us know if this helps.
Tone Southerland
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 ) cheersCathie 64
It was actually a thread on microsoft.public.sharepoint.setup_and_administration via google groups; I gather the crucial thing is that the Sharepoint Search Service needs the same account for the service and content access account. When you go to the configurations page the two accounts need to be the same. with enough permissions to access both the Index DB and the sharepoint content:
http://groups.google.com/group/microsoft.public.sharepoint.setup_and_administration/browse_thread/thread/5e98da1d2b7860b5/1681956bd832c1a3 lnk=st&q=The+update+cannot+be+started+because+the+content+sources+cannot+be+accesse&rnum=7#1681956bd832c1a3