Search working, but only returning results from a month ago
- 0WSS 3.0 installed on a single box using SQL Server 2005.
Search works, mssearch.exe running on box, Search service shows as started in Central Admin panel.
However, new content after 9/10/07 is not being returned using search, only content added up to 9/10.
From checking the application event log, it appears that on 9/10/07 the index was paused (event id 2442) but not restarted (event id 2444). Previously, all 2442 events were always followed within a minute or two by a 2444 event.
2442 text:
Type: Warning
Source: Windows SharePoint Services 3 Search
Category: Gatherer
The index was paused.
Context: Application 'Search', Catalog 'index file on the search server Search'
2444 text:
Type: Information
Source: Windows SharePoint Services 3 Search
Category: Gatherer
The gatherer index resumed.
Context: Application 'Search', Catalog 'index file on the search server Search'
I don't think this is coincidence, but I'm not sure how it might be connected: our network guy installed Symantec Backup Exec on the box a few days before this.
What steps might I take to un-pause the index and crawl all the new stuff added since 9/10 (over 5GB of docs)?
Thanks.
All Replies
- 0
Just ran into the same problem - nothing past 10/4 was showing up, but search results for old files that had been deleted were. The solution for me was that I had started using granular permissions from the top level down about that time and was unaware that by default this trims (hides) everything with non-inherited permissions from the search crawler.
If you go into Site Settings and hit Search Visibility under the Site Administration column you get the options to expose the site back to the crawler. Caveat being that now those items will show up in a search regardless of the user's permission level, although I don't think they can access it from the link.
Otherwise, when I was researching it a few other things came up:
- Restart your server.
- A permissions problem on the spsearch service seemed to be a common solution. This may have also been a problem with me as well, but we had jacked up the Windows SharePoint Services Search's permissions before I found the granular permission thing.
- Someone noted that their content DB had become detached from the spsearch service -- you can see both the account the service is using and the attached content dbs with "stsadm.exe -o spsearch -action list"
To go ahead and reset the search index, run
"stsadm.exe -o spsearch -action fullcrawlstop" and then
"stsadm.exe -o spsearch -action fullcrawlstart"Good luck.
