Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Index Propogation

  Asked By: Sade    Date: Sep 19    Category: Sharepoint    Views: 2783

I've setup my 2 servers in my Production environment but I'm having
issues with indexing. My WFE/Query server is not responding according
to my Propogation Status. I get a "Propogation Status: Query server
not responding (Servername)" message when looking on the Configure
Search Settings page.

Any thoughts from any of you? I really need to get this squared away
and I'm banging my head against the wall on this.

Share: 

 

8 Answers Found

 
Answer #1    Answered By: Trinity Scott     Answered On: Sep 19

Assuming MOSS2007, Why not put the query  role on the same server  as the
indexer?

That way the index  does not need to be copied to the WFE.

 
Answer #2    Answered By: Constance Guerrero     Answered On: Sep 19

Is this the recommended way of doing it in a Medium Farm? Everything I've read
suggests to have the WFE also do the Search role, while keeping the indexing  by
itself on a server. Evidently this increases performance on the WFE for
querying because it only has to do local queries against the index  files since
they're propogated from the Index server  to the query  server.

 
Answer #3    Answered By: Chandrabhan Konwar     Answered On: Sep 19

I'm not sure on that point of what is recommended for a medium farm,
I'll bow to other experts on this.

( we are only working out our architecture ATM, so nothing in production
yet).

The one downside I can see to having the query  on the WFE is it will
require enough disk space to keep another copy of the index.

(though disk space is cheap..right?).

One comment I would have about the index  server is that it is not always
crawling so depending on your crawl schedule that server  could be idle
for a fair chunk of the time, especially if you do a full crawl to start
with then only do incrementals from then on.

The only thing I've heard about performance being improved with query
being out front on the WFE's is in the case of large farms with many
WFE's out front all load balanced.

 
Answer #4    Answered By: Vinay Thakur     Answered On: Sep 19

In a 2 x 1 medium farm - 2 WFE servers  load balanced with query  role. 1 App
server with Index, ECS, Doc Conv, etc.
It is a best practice to have the query service on both WFEs - for search
results and disaster recovery. Since a copy of the index  is stored on both WFEs,
then the index(app) server  can crash and searches still work. They will get
stale, however. Your issue may be
caused by 1. Incorrect permissions (all app pools are local admins on all
servers) 2. Incorrect permissions on the propagation share (you let CentralAdmin
create it, right) 3. restriction of NetBIOS ports between Central Admin, Index,
and Query servers. 4. Stopping the Windows SharePoint Services Web Application
service on the
Index server 5. Changing the Office Server Web IIS Virtual server, or modifying
it

 
Answer #5    Answered By: Tiana Whitaker     Answered On: Sep 19

Are you getting any errors in the event logs on the index  server or
the WFEs?

 
Answer #6    Answered By: Alice Chandler     Answered On: Sep 19

Right now we only have 1 WFE, with the intention of adding another later. I
wanted to split off the Query role from the Indexing machine but I've been
having a time of it.

1. Permissions seem Ok. I have added 2 of the 3 Service accounts as local
admins, but not the Service account that is running the App Pools
(srv_moss_ssp). Is that necessary?
2. I let CA create the searchindexpropogration share and I see the share and the
securities seem Ok.
3. Not sure what you mean here.
4. Should the WSS Web App service be stopped on the index  server? It is
currently running on both the WFE and the Index box.
5. Haven't touched it.

I thought the installation and other configs would make the necessary changes.
Is there documentation out there which steps through any manual configs?

For now, I have both the Index and Query services running on the one server,
with the other serving acting as the WFE.

Any help/insight is greatly appreciated.

Here are some error logs from the Event Log on the WFE:

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office server  Shared Services
Event ID: 6482
Date: 2/26/2007
Time: 8:55:29 AM
User: N/A
Computer: SACF216A
Description:
Application Server Administration job failed for service instance
Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(7d4a2ae2-c0c7-452f-bd65-5e9e916e6ac5).

Reason: Object c86725eb-6751-49e9-a001-52a8c22b18a6 not found.

Techinal Support Details:
System.Collections.Generic.KeyNotFoundException: Object
c86725eb-6751-49e9-a001-52a8c22b18a6 not found.
at Microsoft.Office.Server.Search.Administration.SearchApi.get_App()
at
Microsoft.Office.Server.Search.Administration.SearchApi.SetUsersPermittedToQuery\
(String[] userNames, Boolean force)
at
Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize(\
)
at
Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalShared\
ServiceInstances(Boolean isAdministrationServiceJob)

 
Answer #7    Answered By: Lynette Sawyer     Answered On: Sep 19

All application pool identities must be local administrators on every box in
the farm. If this does not fix your problem, I would removoe the app server  from
the farm and re-add using the SP&T Configuration Wizard. You could also
verify DNS is working correctly between all members of the farm and that your
hosts file, if used, is correct.It really looks like a network issue - are you
using IPSec or is a firwall between them?

 
Answer #8    Answered By: Shelton Dickson     Answered On: Sep 19

How would I go about removing the App Server from the farm and then re-adding
it? I will make the App Pool identities local admins on all the boxes.

 
Didn't find what you were looking for? Find more on Index Propogation Or get search suggestion and latest updates.




Tagged: