No, this time I won’t write a full step-by-step install guide of FAST Search Server for SharePoint 2010. If you’d like to get a detailed install guide, please go to the Microsoft Download Center and download the B2FASTSearchDeploy.xps from there. This is a very detailed, 59 pages long guide. Ohhhhhhh, is it too long and would you like to get some shorter summary? – Yes, you can find some shorter summary around the blogosphere. BUT, please, be careful as generally they miss some very important steps, so finally the result will be not really what you expect. Or if you made a FAST Search Server for SharePoint 2010 installation and configuration by some of them, verify it by the official guide.
So, the only one install guide with 100% success is the detailed, 59 pages long: this one from Microsoft. I know, it’s not to easy to follow all these steps and don’t make any mistake. I also did. And I was suffering because of web part errors and empty result sets as well. I was going to become crazy. I was going to destroy all of the computers around me and getting some new job without bits on a deserted island. Yes, I was really upset. I think you can imagine that…
Finally, I’ve got some idea and help from the Microsoft FAST Team. Here are some steps you should check if you have some errors or unexpected symptops after the installation:
  • Check FAST Query SSA server URLs, port numbers and protocols.
  • FAST Query SSA should be set as default for your webapp.
  • Check %FASTSearch%varlogsyslog for logs, especially qrproxy.log if exists.
  • Try a local query on the FAST Search Server 2010 Query node (http://localhost:13280)
  • The command nctrl status checks if all required processes are running.
To be honest, in my case all of these steps were passed, without any error. Finally, I recognized the command New-FASTSearchSecurityClaimsUserStore -id win didn’t run but gave this error for me:
New-FASTSearchSecurityClaimsUserStore : Unable to create new Claims content: Could not connect to net.tcp://localhost:13278/ConfigManager. The connection attempt lasted for a time span of 00:00:02.0252610. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:13278.
In the Event log, I found this:
Log Name:     FAST Search Source:        FAST Search QRServer Date:         12/8/2009 11:37:11 AM Event ID:     1000 Task Category: None Level:         Error Keywords:     Classic User:         N/A Computer:     SP2010.demo2010.local Description: Admin error occurred during loading of keyword data. The keyword cache may be stale. Exception Message:Failed to communicate with the WCF service.
Ok, let’s check if all of the required services are running, even IIS Application Pools (eg. SharePoint Web Service).
If they are also running, check the following folders are created:
  • data
  • datadata_security
  • datadata_securityadmin
  • datadata_securityworker
In my case, these folders were missing. Yes, they should be created manually, but unfortunately I’ve missed this step during the configuration. What could I do? I stopped the SAMAdmin and SAMWorker services, created the required folders, then restart these services again.
And voila, everything became working!
The world is nice and good again… More posts about FAST Search are coming soon, stay tuned!