The search request was unable to connect to the search service
AdminLibrary.dll:MakeRemoteRequestToWorker - Unable to complete request to sam worker node
AdminLibrary.dll:Resuscitate - Unable to get LastCommittedTransactionId
On remote servers, this can result if Firewall rules were not set up successfully when reconfiguring the cluster with additional servers, or because the Firewall was not enabled during the Post-Configuration Wizard, as noted in the software requirements for FAST Search Server installation. Running through the deployment reconfiguration steps with Firewall enabled is sufficient to address this scenario.
On a single server, where the samadmin and samworker processeses are both local, this scenario can result from the authentication loopback check security feature of Windows Server 2008. The feature prevents man-in-the-middle authentication attacks, but also prevents the internal communication between the two FAST processes. The loopback check can be avoided by registering the Service Principal Names (SPN) for the FAST Search Server and FAST Search service account as per the steps below:
setspn -A HTTP/fastmachine DOMAIN\fastuser
setspn -A HTTP/fastmachine.domain.extension DOMAIN\fastuser
Raksta ID: 2534337. Pēdējo reizi pārskatīts: 2011. gada 22. jūl.. Pārskatījums: 1