Sign In
|
Home
|
Find a Member
|
Find a Group
|
Help
Community Search
SharePoint Blogs
Discussions
Groups
Mossasaurus
Book Reviews
History
|
Incoming Links
Recent Changes
Content Types
Record
Edit Control Block
SharePointAds.com
Microsoft FAST ESP Search
View All Pages
A
A
A
Font Size
Print This
Email This
Report This
Event Id 2424
Many of you may see the recurring error with Event id 2424 in your event viewer logs. If you have the error, it will appear as frequently as you have the Windows SharePoint Server Search configured to run in Central Admin/Operations/Services on Server. Sometimes you can get away with stopping and restarting the service (with a different database name when restarting) and it goes away. If that doesn't work for you, keep reading.
I found that this issue occurs when you attach a database from a different location, or upgrade it. To resolve the error you may have to go to SQL Server and manually update the permissions of that database. For example if your content database is WSS_Content_MyApp and your farm search service account is mydomain\searchservice, go to the mydomain\searchservice login in SQL Server and then to usermappings. Grant that user dbreader access to WSS_Content_MyApp. You may also need to go to Central Admin/Application Management/Content Databases and select each of the content databases for each web application and make sure they have an indexer assigned to them.
The details of the error are below:
Event Type: Error
Event Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 2424
Date: 1/10/2008
Time: 5:48:03 PM
User: N/A
Computer: SPWEB02
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'
Any comments feel free to post them on
my blog
.
Good luck.
-ann wallinger
Related Document
Last modified at 4/15/2009 7:40 AM by System Account