FAST Component is not responding RRS feed

  • Question

  • I have installed and configured FAST Farm (admin and non-admin server) successfully.

    On One Server (Admin) i have deployed Admin and all other component and on Second Server (non-admin) I have Deployed only Query and Search Engine component. When I check the log from the admin server, I have found following warning:

    (1) Module (Search engine) <Second Server Name> is not responding.

    (2) Module (Search Dispatcher) <Second Server Name> is not responding.

    (3) Module (Node Control) <Second Server Name> is not responding.

    Please tell me how can i resolve these warning

    Also How can i identify Query and Search Engine Component is working fine on the FAST Server admin and non-admin server.

    Is There any problem with my configuration. Below is the sample of Deployment XML which i was using during configuration.

    Deployment XML:

    <host name= Admin Server Name>

    <admin />

    <indexing-dispatcher />

    <content-distributor />

    <webanalyzer server="true" link-processing="true" lookup-db="true" />

    <document-processor processes="4" />

    <searchengine row="0" column="0" />

    <query />


    <host name= Non-Admin Server Name>

    <searchengine row="1" column="0" />

    <query />



    <row id="0" index="primary" search="true" />

    <row id="1" index="none" search="true" />


    Please give the reply on this asap. it will be very helpful to me.

    Tuesday, January 11, 2011 10:42 AM

All replies

  • Have you install the SSL Certificates successfully on the secondary server?
    Ameet Phadnis (e Tek Global Inc.)
    Tuesday, January 11, 2011 12:45 PM
  • Thanks for your response.

    Yes I have install the SSL Certificates succesfully on the secondasry server. I have checked it. I am not abel to remove above mentioned errors.

    Also Please review above mentioned deployment.xml section , any correction is required or it is right as per my scenario.

    Tuesday, January 11, 2011 1:15 PM
  • Hi,

    Do an infotool report and open the logs folders.  There will be a file called "all.log"   Check that file and see what the actual errors are it should help give you some more valuable clues.

    Regards, Savoeurn Va Microsoft Online Community Support
    Thursday, March 10, 2011 2:46 PM