Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Office Server Search error (eventid 4127)

Posted on 2010-09-20
9
Medium Priority
?
1,743 Views
Last Modified: 2012-05-10
Hi all,

This error comes up very frequently in de Application Log of one of our WFE:
Content index on AnchorProject could not be initialized. Error The content index is corrupt.   0xc0041800.Component: e16deedc-e6aa-4f04-9a87-a453de6887fc

Our SharePoint environment exists of 2 WFE's, 1 index server, 1 SQL server. All servers are Windows Server 2003 Ent Edition SP2 32-it, exept for the SQL server. That is 64-bit.

I've already tried to rebuild the index, but the error keeps coming up.

Any ideas?

thanks.
0
Comment
Question by:exchangeexpertsdelijn
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
9 Comments
 

Author Comment

by:exchangeexpertsdelijn
ID: 33722894
Increased the point value to 500...
0
 
LVL 15

Expert Comment

by:sharepointguru14
ID: 33725226
I'm assuming this is MOSS 2007 and that you want AnchorProject to be indexed.
I have resolved this error a few times before following these steps.
Open SharePoint Central Administration.
click Application Management.
On the Application Management page, click Create or configure this farm’s shared services.
On the Manage this Farms Shared Services page, click the SSP whoes administration page you want to open.
On the Shared Services Administration Home page, click Search settings in the Search section.
On the Configure Search Settings page, click Reset all crawled content in the Crawl Settings section.
By default, the Deactivate search alerts during reset check box is selected on the Reset Crawled Content page. This option prevents users who have search alerts configured from being sent unnecessary e-mail messages when the crawled content is reset. Click to clear this check box if you do not want to disable alerts during the reset operation.
Click Reset Now.
In the message box, click OK to confirm that you want to reset the search content index.
Go back to the Shared Services Administration Home page, click Search settings in the Search section.
Click Content sources and crawl schedules.
Drop the menu down for the Source you want to crawl, click Start Full Crawl.
0
 

Author Comment

by:exchangeexpertsdelijn
ID: 33732528
Hi,
yes, this is MOSS 2007. I'm a real noob, when it comes to MOSS so any help is appreciated. I don't know what this "AnchorProject" is and neither if it needs to be indexed or not. I just want the error to go away and know why it only appears on one of the WFE.

When i got to "central administration" -> Application Management -> Manage Search service
at the bottom i see:
Shared Service Providers with Search Enabled
 
  SSP name: SharedServices
  Crawling Status: Crawling - De Lijn Sharepoint | Computing ranking
  Items in index: 491356
  Propagation status: Query server not responding (WFE servername)  
Is this issue related?

@Sharepointguru14:
thanks for your input. As mentioned in the first post, i already tried rebuilding the indexes. Anyhow i will try this again. Since this is a timeconsuming procedure i am obliged to run these steps over the weekend. so please be patient for some feedback.
0
Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

 
LVL 15

Expert Comment

by:sharepointguru14
ID: 33734057
yes the query server error is probably related especially if you are only having the error on the one front end. Try restarting the query server services.
Can you tell me the services that you have running on each of the front ends as well as the services on the index server?
0
 

Author Comment

by:exchangeexpertsdelijn
ID: 33742150
hi,
on both WFE's i have these (MOSS-related) services running:
- Office SharePoint Server Search
- Windows SharePoint Services Administration
- Windows SharePoint Services Timer
- Windows SharePoint Services Tracing

on the index server:
- Office SharePoint Server Search
- Windows SharePoint Services Administration
- Windows SharePoint Services Search
- Windows SharePoint Services Timer
- Windows SharePoint Services Tracing

How do i restart the query server services?

thanks.
0
 
LVL 15

Expert Comment

by:sharepointguru14
ID: 33745379
Open up the properties for the Office SharePoint Server Search on each server and let me know what roles you have assigned to what machines
0
 

Author Comment

by:exchangeexpertsdelijn
ID: 33760797
Hi,

I tried to reset the crawled content yesterday evening. then i tried to go back to the search settings (as instrucetd by you) but i keep getting this error message:
"The search service is currently offline. Visit the Services on Server page in SharePoint Central Administration to verify whether the service is enabled. This might also be because an indexer move is in progress. " 
It's been telling me this for the past 15 hours. I tried to restart the Office Search Service but that doesn't help much. Rebooting the WFE's neither.
Do i need to panic now? :/
0
 

Author Comment

by:exchangeexpertsdelijn
ID: 33767919
Hi,
I was able to fix the error. I don't know what happend there. I've rebuilt the indexes, but the error keeps on coming in the application log of the WFE. When i check the Search Setting on the SharedServices website, on the "crawl setting" section the propagation status is still: "Query server not responding"
Where can i check which roles is assigned to what machines?
0
 
LVL 15

Accepted Solution

by:
sharepointguru14 earned 2000 total points
ID: 33770907
that will be in the search server service settings. Rather then click on start or stop click on the name and it will tell you if it has index role or query role.

If you are running Query role on the index server this is likely the cause of your problem as the index will not propagate out to any other query servers
0

Featured Post

Three Reasons Why Backup is Strategic

Backup is strategic to your business because your data is strategic to your business. Without backup, your business will fail. This white paper explains why it is vital for you to design and immediately execute a backup strategy to protect 100 percent of your data.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

These days socially coordinated efforts have turned into a critical requirement for enterprises.
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
This course is ideal for IT System Administrators working with VMware vSphere and its associated products in their company infrastructure. This course teaches you how to install and maintain this virtualization technology to store data, prevent vuln…
Do you want to know how to make a graph with Microsoft Access? First, create a query with the data for the chart. Then make a blank form and add a chart control. This video also shows how to change what data is displayed on the graph as well as form…

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question