I
spent considerable time last week trying to build 2-node FAST cluster for SharePoint
2010 implementation. it was my very first FAST cluster implementation, so cut me some slack people, will you.
Creating the setup.xml file and building the admin FAST
node was the easy part, but trying to connect the non-admin node is what took up
most of my time.
(The
default FAST installation creates 3 example files under C:\FASTSearch\etc
directory, they are named deployment.sample.single.xml,
deployment.sample.multi1(2).xml. Most of the time you can tweak them to suit
your needs instead of trying to create on from scratch.)
When
running the configuration wizard, the error I kept getting was:
{drive}:\FASTSearch\bin\MonitoringServiceConfig.exe”
Output – Error: The file ‘{drive}:\FASTSearch\etc\middleware.cfg’ was not
found.
I
searched through the blogs for quite some time, and I should here thank all the
bloggers out there which provided useful information (including our very own
David Sobiecki), links provided at the bottom here.This is the summary of things I did or checked for all in one place:
- Issue ncrtl status on the FAST admin node: we need to make sure all services show status running
- Try running setfastsearchipsec -create on the non-admin FAST node: this will prompt connection to the FAST admin node and parsing the setup.xml file. Depending on the error reported it's usually either connectivity issue to the FAST admin node, or incorrect setup.xml formatting
- Recreate the setup.xml file using notepad: apparently fancier XML editors add invisible characters that FAST configuration wizard doesn't like, so to be safe you should paste content on notepad and quickly proofread for any characters that are not supposed to be there
- Disable firewall on the FAST Admin node: now I know this is not best practice, but in my case it worked. FAST configuration wizard will complain if the firewall is disabled, so I tried many combinations. Having the firewall enabled on the non-admin node and disabled on the admin node is what worked for me
- Finally, unselect browser proxy settings (automatically detect settings, use proxy server etc.) on the non-admin node
Hope this summary
will help other people who run into similar issue.
Happy FASTing people!
If you feel inclined to read
more, here is a list of blogs I used:
No comments:
Post a Comment