Jack_A_Roe
asked on
Search (FAST?) won't work if user don't choose "All sites"
I'm trying to get FAST Search Server to work with SharePoint Server 2010. I have no idea how well I'm doing since FAST really has no GUI, it seems, and just sits there. Perhaps I'm using Enterprise Search, who knows?
Anyhow, I been following "Deployment guide for FAST Search Server 2010 for SharePoint", after which I've been working several days with troubleshooting.
The most striking problem I'm having right now is that while people search works, site search usually doesn't. Right now, here's what happens:
If I search for a document I get no result (it doesn't matter if I search in the box on top site, or at the FAST template site); if I then click link "All sites", I find what I'm searching for instantly. (The document is in a library at top level.)
Looking around at logs in Central Administration and Event Viewer, indexing and everything seems to work; of course, the site collection I'm using for my tests is crawled.)
Why could this be, that I need to first search, and then click "All sites" to actually get the results?
Anyhow, I been following "Deployment guide for FAST Search Server 2010 for SharePoint", after which I've been working several days with troubleshooting.
The most striking problem I'm having right now is that while people search works, site search usually doesn't. Right now, here's what happens:
If I search for a document I get no result (it doesn't matter if I search in the box on top site, or at the FAST template site); if I then click link "All sites", I find what I'm searching for instantly. (The document is in a library at top level.)
Looking around at logs in Central Administration and Event Viewer, indexing and everything seems to work; of course, the site collection I'm using for my tests is crawled.)
Why could this be, that I need to first search, and then click "All sites" to actually get the results?
ASKER
Thank you very much! - As you can see from my post above, I have a feeling that FAST is not working properly, that that is the culprit. I'm troubleshooting that now explicitly so to speak, and I will make use of your link tomorrow (I need to quit for the day).
I have a multiserver farm, with one SharePoint Server 2010 Enterprise on a Windows Server 2008 R2, a FAST Search Server 2010 on another Windows Server 2008 R2, and a Microsoft SQL Server 2008.
Your intention to put an extra effort into this and get back to me is very much appreciated.
I have a multiserver farm, with one SharePoint Server 2010 Enterprise on a Windows Server 2008 R2, a FAST Search Server 2010 on another Windows Server 2008 R2, and a Microsoft SQL Server 2008.
Your intention to put an extra effort into this and get back to me is very much appreciated.
ASKER
I have gone through the troubleshooting steps at technet.microsoft.com/en-u
ASKER
I would also like to point out that crawling seems to work. The SSA I created, "FAST Query SSA" is crawling successfully regurarly. If I mark it and click "Manage", I have a link on the left side, "FAST Search Administration", which to me hint that this is in fact a successful FAST SSA, and wile I haven't fooled around with them, the links in FAST Search Administration seem live enough.
Also, running Get-FASTSearchContentColle
This should indicate that my test document is fed to the database, and should be searchable. But of course, for some reason I'm not using FAST when searching in my site collection.
Also, running Get-FASTSearchContentColle
Name : sp
Created :
Cleared : 2011-03-15T10:32:18.080524
LastInput : 2011-03-23 15:51:30
DocumentCount : 59
Description : Default collection for SharePoint content
Pipeline : Office14 (webcluster)
Created :
Cleared : 2011-03-15T10:32:18.080524
LastInput : 2011-03-23 15:51:30
DocumentCount : 59
Description : Default collection for SharePoint content
Pipeline : Office14 (webcluster)
This should indicate that my test document is fed to the database, and should be searchable. But of course, for some reason I'm not using FAST when searching in my site collection.
Just to be sure, you created the two service applications for Fast?
ASKER
Yes, I've followed MS whitepaper "Deployment guide for FAST Search Server 2010 for SharePoint" and ended up with service applications "FAST Query SSA" and "FASTContent" (names obviously unimportant in themselves, but they indicate function) and I haven't had any problem with neither, as far as I can see.
---
The only error I got in any log (Event Viewer Application and System) on SharePoint or FAST is Event 22, Microsoft.ResourceManageme
According to the MIIS client on the SharePoint server the profile synchronization works like a charm; I can work with my profiles in Central Administration also.
---
The only error I got in any log (Event Viewer Application and System) on SharePoint or FAST is Event 22, Microsoft.ResourceManageme
Log Name: Application
Source: Microsoft.ResourceManageme
Date: 2011-03-15 15:47:25
Event ID: 22
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: [My SharePoint server]
Description:
The Forefront Identity Manager Service cannot connect to the SQL Database Server.
The SQL Server could not be contacted. The connection failure may be due to a network failure, firewall configuration error, or other connection issue. Additionally, the SQL Server connection information could be configured incorrectly.
Verify that the SQL Server is reachable from the Forefront Identity Manager Service computer. Ensure that SQL Server is running, that the network connection is active, and that the firewall is configured properly. Last, verify the connection information has been configured properly. This configuration is stored in the Windows Registry.
Source: Microsoft.ResourceManageme
Date: 2011-03-15 15:47:25
Event ID: 22
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: [My SharePoint server]
Description:
The Forefront Identity Manager Service cannot connect to the SQL Database Server.
The SQL Server could not be contacted. The connection failure may be due to a network failure, firewall configuration error, or other connection issue. Additionally, the SQL Server connection information could be configured incorrectly.
Verify that the SQL Server is reachable from the Forefront Identity Manager Service computer. Ensure that SQL Server is running, that the network connection is active, and that the firewall is configured properly. Last, verify the connection information has been configured properly. This configuration is stored in the Windows Registry.
According to the MIIS client on the SharePoint server the profile synchronization works like a charm; I can work with my profiles in Central Administration also.
ASKER
Your question regarding service applications might lead to something valuable. I have two, as I said, and I know one work ("FAST Query SSA"), but I'm not sure about the other ("FASTContent").
FAST Query SSA have a greyed out "Search Service Application Proxy" below it in the list of service applications; FASTContent do not. I don't know whether this is expected or not.
When I mark the FAST Query SSA and click "Manage", below Administration to the left, there's a link called "FAST Search Administration". FASTContent do not; whether this is expected I don't know.
FAST Query SSA crawl content alright, FASTContent can't. But then again, I don't know if FASTContent SSA should be able to crawl.
The slightest input, even question, is much appreciated.
FAST Query SSA have a greyed out "Search Service Application Proxy" below it in the list of service applications; FASTContent do not. I don't know whether this is expected or not.
When I mark the FAST Query SSA and click "Manage", below Administration to the left, there's a link called "FAST Search Administration". FASTContent do not; whether this is expected I don't know.
FAST Query SSA crawl content alright, FASTContent can't. But then again, I don't know if FASTContent SSA should be able to crawl.
The slightest input, even question, is much appreciated.
ASKER
(Regarding the Event Viewer post above, I also sometimes get a cryptic Error 53, SharePoint Server Search, "Could not create a database session.")
The application proxy is only with the query, that is normal behavior.
Are you saying that when you are clicking on the FAST Content that htere is no link to FAST Search Administration? It's on my machine (single sharepoint farm connected to a three-server FAST farm) The only difference I see with the two (not a fast specialist) is that there isn't a Queries and Results area in the FAST Content navigation (which is normal). Can you maybe post a screenshot of your FAST Content Management screen?
Are you saying that when you are clicking on the FAST Content that htere is no link to FAST Search Administration? It's on my machine (single sharepoint farm connected to a three-server FAST farm) The only difference I see with the two (not a fast specialist) is that there isn't a Queries and Results area in the FAST Content navigation (which is normal). Can you maybe post a screenshot of your FAST Content Management screen?
ASKER
Are you saying that when you are clicking on the FAST Content that htere is no link to FAST Search Administration?That's right, see the screenshot below, you asked for (there you can see that I've tried to use it for crawling during my troubleshooting):
FASTContent.png
ASKER
Properties for the seemingly faulty SSA FASTContent is as follows:
One thing I tried very early in this drawn out troubleshooting process, was to change the port of the Content Distributor above, to 13390 instead. This was because 1) that port is open in the FAST server (13391 is not according to Netstat), and 2) googling suggested that that might be the solution; however, it didn't change anything as far as I can remember, so I changed back.
Name: FASTContent
FAST Service Application: FAST Search Connector
Search Service Account: [My SP service account with all the privileges it can ask for - a result of my troubleshooting]
Application Pool for Search Admin Web Service: FAST_Content_App_Pool (Account: said service account)
Content distributors: [FQDN my FAST Search Server]:13391
Content Collection Name: sp
FAST Service Application: FAST Search Connector
Search Service Account: [My SP service account with all the privileges it can ask for - a result of my troubleshooting]
Application Pool for Search Admin Web Service: FAST_Content_App_Pool (Account: said service account)
Content distributors: [FQDN my FAST Search Server]:13391
Content Collection Name: sp
One thing I tried very early in this drawn out troubleshooting process, was to change the port of the Content Distributor above, to 13390 instead. This was because 1) that port is open in the FAST server (13391 is not according to Netstat), and 2) googling suggested that that might be the solution; however, it didn't change anything as far as I can remember, so I changed back.
Ok, I'll check back with you later tonight (at work now and don't have a server farm up here)
ASKER
Thank you. Meanwhile I look around and if I find something interesting I'll post it.
ASKER
Another thing I would be happy to compare to a successful FAST implementation is the "Search Application Topology"; from the beginning it has been bothering me that the FAST Search Server is not listed, only the SharePoint Server and the SQL Server. However in properties for the SAs, the FAST server is used as "Query Service Location", etc.
ASKER
You can try to use this tool to identify where it is going wrong:At last I got around to try this, and was absolutely sure it would turn up nothing, but what do you know: The queries are sent to the FAST Server...!
http://techmikael.blogspot.com/2011/02/fast-search-for-sharepoint-query-logger.html
QueryLogging.PNG
ASKER
If I search in the little search box on the first page, the query goes to FAST Server where (in the FS4SP Query Logger) it is listed as "[key word] site:'http://[site]', but I do not find the document.
If I on the next page, where I'm redirected (OSSSearchResults), click the link "All Sites" -- I get the results: Both Superman.docx, and the document in which the key word "Superman" is written. However, that "All sites" search do not turn up in the Query Logger at the FAST server.
If I on the next page, where I'm redirected (OSSSearchResults), click the link "All Sites" -- I get the results: Both Superman.docx, and the document in which the key word "Superman" is written. However, that "All sites" search do not turn up in the Query Logger at the FAST server.
Did you disable the standard search service? IIRC from the FAST install you need to disable the standard search.
ASKER
"Search Service Application" is running.
I too had a vague memory that it it should not, but since I didn't find a way to disable it, I assumed it must be running. -- After reading your post I've looked for a way to disable it once again, but I really can't find a way to do it, silly enough.
Could you help me out on this detail?
I too had a vague memory that it it should not, but since I didn't find a way to disable it, I assumed it must be running. -- After reading your post I've looked for a way to disable it once again, but I really can't find a way to do it, silly enough.
Could you help me out on this detail?
ASKER
I just made quite a discovery; when I search I actually get results not only from the profile store, but also *from a deleted* web application; the first web application I created, (A), but which I for different reasons got rid of. So when I search from (B) for something that's stored in (B) I get nothing, but when I search for something that's stored in (A), I get the hits. This is searching from the FAST Search web site template.
ASKER
Did you disable the standard search service? IIRC from the FAST install you need to disable the standard search.While I can't disable that service from Central Administration (to the best of my knowledge), in Configure Service Application Association, it is not selected, only FAST Query SSA.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can try to use this tool to identify where it is going wrong:
http://techmikael.blogspot.com/2011/02/fast-search-for-sharepoint-query-logger.html