Wednesday, September 1, 2010

SharePoint Gatherer Event ID 2442 and 2444

I have these days a problem with my SharePoint. To be specific, the search module is no more indexing documents that are added to the WSS 3.0 document libraries. To make myself clear, the serach module ("C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN\mssearch.exe" ) is properly working but recently added docs are not being returned.

I have had a look to the Event Viewer on the Sharepoint server and, filtering for source Windows SharePoint Services 3 Search and Category Gatherer, I’ve found that I have two kind of events:


Event Type: Warning
Event Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 2442
User: N/A
Computer: xxxxx
Description: The index was paused.
Context: Application 'Search', Catalog 'index file on the search server Search'

&

Event Type: Information
Event Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 2444
User: N/A
Computer: xxxxx
Description: The gatherer index resumed.
Context: Application 'Search', Catalog 'index file on the search server Search'

These events are recurring, which means that the indexing of the document stops (eventid 2444) and starts (eventid 2442) all the time.


The problem is that the last time I have had a event 2444, it was never followed by an event 2442.

The problems seems to be due to a bug on Symantec Backup Exec:

http://seer.entsupport.symantec.com/docs/294181.htm

As Symantec states, during the backup of Microsoft Office SharePoint Server (MOSS) 2007 or Windows SharePoint Services (WSS) 3.0, the content index is paused and does not resume. As the result the content index does not get updated after the backup completes.

The workaround proposed by Symantec is to reboot the server hosting WSS. Which is, let me say, inadmissible.

I tried running the commands recommended by Microsoft to force the system to run a full crawl, but I was unsuccessful, because old document where still unindexed.

stsadm -o spsearch -action fullcrawlstop

&

stsadm -o spsearch -action fullcrawlstart

The two commands returned “Operation completed successfully.” but nothing changed. New documents were still not returned.

So I tried to restart the Search service by issuing these commands at the command prompt:

net stop "Windows SharePoint Services Search"
The Windows SharePoint Services Search service is stopping.
The Windows SharePoint Services Search service was stopped successfully.

&

net start "Windows SharePoint Services Search"
The Windows SharePoint Services Search service is starting.
The Windows SharePoint Services Search service was started successfully.

Once I did this, multiple mssdmn.exe instances appeared in task manager, which meant thaat SharePoint was trying to re-index everything.


A few minutes after, two events appeared in the Application event log:

Event Type: Information
Event Source: Windows SharePoint Services 3 Search
Event Category: Content index server
Event ID: 4164
User: N/A
Computer: xxxxx
Description:
Component: 2fc071d0-75a0-404f-9527-970bf424b264
Catalog: Search. A master merge was started due to an external request.

&

Event Type: Information
Event Source: Windows SharePoint Services 3 Search
Event Category: Content index server
Event ID: 4103
User: N/A
Computer: xxxxx
Description:
Component: 2fc071d0-75a0-404f-9527-970bf424b264
A master merge has completed for catalog Search.

This has solved my problem. The new documents appeared in the results.

So I am planning to schedule a batch containing a net stop "Windows SharePoint Services Search" && net start "Windows SharePoint Services Search" everyday at night to be sure that new documents are properly indexed.

I hope this will help you if you have the same issue.

2 comments:

  1. This fixed my problem too ! Thanks

    ReplyDelete
  2. I have this problem right before my backup fails, my backup is not always failing just intermittantly. Very frustrating not sure how these two things are linked yet. Think it has something to do with volume shadow copy service. I will try these steps and see if this resolves anything.

    ReplyDelete

Related Posts Plugin for WordPress, Blogger...