FAST Search Center Template - Results page webpart error
-
Friday, November 27, 2009 10:49 PMI've installed and configured a FAST Server for SharePoint 2010 (I have SharePoint Server 2010 installed on a different machine), done a crawl, created a site collection using the FAST Search Center Template. When I do a search the results page shows a webpart error:
"Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator."
The webpart showing the error is Search Core Results.
Now, I'm pretty sure I followed all the steps in the FAST Search Deployment guide but I could have got something wrong somewhere. Has anyone else managed to get FAST Search working?
Cheers,
Colin
Answers
-
Tuesday, December 01, 2009 2:42 PM
Let me try to take some frustration away colinrippey, and hopefully for some others reporting the same issue as well.
The examples in the installation guide mainly uses https but, noticed that it is not completely consistent, especially the install_info.txt file reports port 13285 which is wrong in the beta.
If you use http to connect to the FAST backend you have to use port 13287, where as 13286 is used for https.
Assuming you have installed the MOSS STS certificate on the FAST backend servers as described in page 31/32 in the section "Enable queries over http",
you can execute the following PowerShell command in the "SharePoint 2010 Management Shell" -> See note below about which cmdlet's can be found where.> Set-SPEnterpriseSearchExtendedQueryProperty -SearchApplication "<Your SSA Name here>" -Identity "FASTSearchQueryServiceLocation" -Value "http://fqdn:13286/"
> IISReset
However if you use http, in the beta realease, you also have to change the file qrproxy.config as described on
page 33, Point 2:Edit the file bin\QRProxyService.exe.config to enable http by removing the comments around the following two sections.
This should be all to connect to the FAST Backend.There is a shorter version of the installation guide available at which might be easier to follow :-)
http://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2009/11/28/FAST-Search-Step-by-Step-Install.aspxNote to Steve Grey-Wilson's thread:
The get-SP* cmdlets are only available on the "SharePoint 2010 Management Shell", where as the *-FAST* cmdlets are available on the FAST backend servers.
See page 36 of the install guide on how to register the cmdlets on the FAST servers.
> Add-PSSnapin Microsoft.FASTSearch.Powershell # In the FAST Backend PowerShell terminal- Marked As Answer by Colin Rippey Thursday, December 03, 2009 10:55 AM
All Replies
-
Friday, November 27, 2009 11:37 PMI have the same problem ... and posted a similiar post. http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/4eb43c74-d640-4ff8-9f08-a553e483ba25
This is not much help except now I feel somewhat better as I have been trying to get FAST Search working for a while now. Lets hope somebody from the FAST Search team see these mesages -
Monday, November 30, 2009 3:07 PM
Hi Steve,
I've held off replying as I wanted to try and work this out myself but I just cannot get it working. From what I can tell there's an inconsistency with the port numbers in the both the Deployment guide (http://www.microsoft.com/downloads/details.aspx?FamilyID=a65aef6f-bc99-4b29-81bb-37fce8ad6ea7&displaylang=en) and indeed the FAST search files themselves (or more likely I'm just not following the instructions precisely enough)
I'm trying to do the simplest install, a single server using http for querying.
On pages 19 and 28 of the guide it states that the install_info.txt file contains the addresses and port numbers. My install_info.txt file is as follows:
===============================================================FASTSearch: Installation Details
===============================================================
---------------------------------------------------------------
APPS TEAM
---------------------------------------------------------------
QR Server Proxy(s): FAST.2010.sp.dev:13285
WCF Service: FAST.2010.sp.dev:13256
Resource Store: FAST.2010.sp.dev:13255
---------------------------------------------------------------
CONNECTORS
---------------------------------------------------------------
Log Server: FAST.2010.sp.dev:13415
Content Distributors: FAST.2010.sp.dev:13329
SQL Server database: jdbc:sqlserver://WIN2008R2.2010.sp.dev;DatabaseName=fastconfigdb;integratedSecurity=true
---------------------------------------------------------------
So, from the above and the details in the guide I would guess that when I create my FAST Query SSA that I should use FAST.2010.sp.dev:13285 for the Query Service Location value. Or should I use port 13286 (for HTTPS) or port 13287 (for HTTP).
Next, on pages 31 & 32 the powershell script has the line:
$queryServiceLocationValue = "http://" + $fastsearchqrserver + ":13287"
What is the correct port here? Is it 13285, 13286, 13276?
Next, on page 33 we are asked to edit the QRProxyService.exe.config file, this file contains many references to urls and ports. Some pertinent entries are:
<appSettings>
<add key="qr_server" value="FAST.2010.sp.dev" />
<add key="qr_port" value="13280" />
<add key="sts_port" value="13288" />
<add key="logLevel" value="WARNING" />
<add key="logFilename" value="qrproxylog.txt" />
<add key="SharePointSTSCertThumbprint" value="10E7D374B50768ECEFAA31390BC255BD952BE4AD" />
<add key="enableClaimsAuth" value="True" />
</appSettings>
(note that we don't get asked to edit the above, just thought I'd include it here - should we be using port 13280 anywhere)
and
<service name="Microsoft.SharePoint.Search.Extended.QRServer.ProxyWCFWinAuth">
<host>
<baseAddresses>
<add baseAddress="net.tcp://localhost:13285" />
</baseAddresses>
</host>
<endpoint address="qrsproxyTcp" binding="customBinding" bindingConfiguration="TCP_WINAUTH_SECURE" contract="Microsoft.SharePoint.Search.Extended.QRServer.IProxyRemote">
</endpoint>
</service>
<service name="Microsoft.SharePoint.Search.Extended.QRServer.ProxyWCFClaims">
<endpoint address="https://localhost:13286/qrsproxyClaims" binding="customBinding" bindingConfiguration="HTTPS_CLAIMS_SECURE" contract="Microsoft.SharePoint.Search.Extended.QRServer.IProxyRemote">
</endpoint>
<endpoint address="http://localhost:13287/qrsproxyClaims" binding="customBinding" bindingConfiguration="HTTP_CLAIMS_INSECURE" contract="Microsoft.SharePoint.Search.Extended.QRServer.IProxyRemote"> </endpoint>
</service>
</services>
From both of these above sections from the config file what should the correct port values and host names be? Should we be replacing localhost with the fqdn of our server?
Finally (and this might be completely off-topic but...) when I use resource monitor to have a look at what ports are being listened on, I can see that ports the qservice.exe is listening on 13280 and 13282. I cannot see a process listening on ports 13285, 13286 or 13287 (of course this may be a complete red herring).
I've tried a variety of different combinations of ports in the SSA configuration, powershell scripts and xml files. Almost all of the time I see the following type of message in the ULS logs on the SharePoint server: (note I have turned off the firewall on the FAST Search box)
11/30/2009 14:11:06.51 w3wp.exe (0x22C8) 0x0EB8 Office Search Server Query dl9q Exception FastSearchGateway::GetQueryResult--Exception searching on QRServer: http://FAST.2010.sp.dev:13285. putting qrserver to the exclude list for a while! Exception: Could not connect to http://fast.2010.sp.dev:13285/qrsproxyClaims. TCP error code 10061: No connection could be made because the target machine actively refused it 10.78.87.10:13285. System.ServiceModel.EndpointNotFoundException: Could not connect to http://fast.2010.sp.dev:13285/qrsproxyClaims. TCP error code 10061: No connection could be made because the target machine actively refused it 10.78.87.10:13285. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.78.87.10:13285 at System.Net.Sock... f218fa56-ef47-4d1c-aa31-46cafd95422a
I have seen the following error but cannot remember exactly what set of settings I used to get this:
11/27/2009 23:36:31.57 w3wp.exe (0x094C) 0x0C8C Office Search Server Query dl9q Exception FastSearchGateway::GetQueryResult--Exception searching on QRServer: http://FAST.2010.sp.dev:13282. putting qrserver to the exclude list for a while! Exception: The content type text/plain of the response message does not match the content type of the binding (application/soap+msbin1). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 24 bytes of the response were: 'callXMLRPC returned NULL'. System.ServiceModel.ProtocolException: The content type text/plain of the response message does not match the content type of the binding (application/soap+msbin1). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 24 bytes of the response were: 'callXMLRPC returned NULL'. ---> System.N... e019abc9-9e26-4ad5-a27e-28311a537e01
All very frustrating :-( -
Monday, November 30, 2009 5:07 PMColin,
I tried again and looked at your comments etc and I too see the inconsistancy but it still failed. I used the ports in the info_txt file.
Just as another point I see in the install doc page 30 the mention of
Get-SPEnterpriseSearchExtendedQueryProperty “SearchApplication “name of the Query SSA that was created"
I opened the FAST Admin consple and I don't see any GET-SP cmdlets
get-help get-sp* returns nothing.
There are Get-FAST cmdlets but nothing equiv to Get-SPEnterpriseSearchExtendedQueryProperty
I do hope the installation process is made somewhat easier to follow in later releases or at least some instructions that we can follow that works :-)
I wish I had better news
Steve -
Tuesday, December 01, 2009 4:30 AM
We have followed the deployment guide on two seperate virtual platforms and have had the same result as posted above.
I do have a question for everyone - are you using Kerberos authenticaiton or NTLM within SharePoint 2010?
Thx,
Gaylen -
Tuesday, December 01, 2009 11:17 AMHi Gaylen,
I am using NTLM.
Steve suggested in another thread to have a watch of the Deploying FAST Search session from the recent SharePoint conference. I did watch the session last night, unfortunately the guys doing the demo didn't seem to need to do any of the deployment steps such as running powershell scripts and editing the QRProxyService.exe.config file (in fact during the demo they didn't even configure a Query SSA - they had one pre-provisioned already ;-)
One thing I did notice during the session was that it was mentioned (on slide 11) that IPSec was used to securely communicate between the SharePoint serve and the FAST server. I had disabled the firewall on my FAST server (as I thought this might be the cause of my Connection Refused errors detailed above).
During one of my (many) re-installs I did notice a warning message during the execution of the FAST psconfig.ps1 script telling me something about IPSec being unavailable as the firewall was disabled.
So, I might start again with the firewall turned on and see what happens.
Cheers,
Colin -
Tuesday, December 01, 2009 12:25 PMI have got the same webpart error. The documentation is not very clear about which ports will be used by FAST and for what purpose.
The error i get is different though.
It says there is nog service on the endpoint specified.
AbstractSearchGateway::Search--Exception when searching for test Microsoft.Office.Server.Search.Query.FASTSearchQueryException: There was no endpoint listening at http://fast001.company.com:13255/qrsproxyClaims that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. at Microsoft.Office.Server.Search.Query.Gateway.FastSearchGateway.GetQueryResult(IQuery query) at Microsoft.Office.Server.Search.Query.Gateway.FastSearchGateway.ExecuteSearch(SearchRequest request, String queryString) at Microsoft.Office.Server.Search.Query.Gateway.AbstractSearchGateway.Search(SearchRequest request)
I've tried changing the port numbers but it is not clear what service i need. :( -
Tuesday, December 01, 2009 2:42 PM
Let me try to take some frustration away colinrippey, and hopefully for some others reporting the same issue as well.
The examples in the installation guide mainly uses https but, noticed that it is not completely consistent, especially the install_info.txt file reports port 13285 which is wrong in the beta.
If you use http to connect to the FAST backend you have to use port 13287, where as 13286 is used for https.
Assuming you have installed the MOSS STS certificate on the FAST backend servers as described in page 31/32 in the section "Enable queries over http",
you can execute the following PowerShell command in the "SharePoint 2010 Management Shell" -> See note below about which cmdlet's can be found where.> Set-SPEnterpriseSearchExtendedQueryProperty -SearchApplication "<Your SSA Name here>" -Identity "FASTSearchQueryServiceLocation" -Value "http://fqdn:13286/"
> IISReset
However if you use http, in the beta realease, you also have to change the file qrproxy.config as described on
page 33, Point 2:Edit the file bin\QRProxyService.exe.config to enable http by removing the comments around the following two sections.
This should be all to connect to the FAST Backend.There is a shorter version of the installation guide available at which might be easier to follow :-)
http://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2009/11/28/FAST-Search-Step-by-Step-Install.aspxNote to Steve Grey-Wilson's thread:
The get-SP* cmdlets are only available on the "SharePoint 2010 Management Shell", where as the *-FAST* cmdlets are available on the FAST backend servers.
See page 36 of the install guide on how to register the cmdlets on the FAST servers.
> Add-PSSnapin Microsoft.FASTSearch.Powershell # In the FAST Backend PowerShell terminal- Marked As Answer by Colin Rippey Thursday, December 03, 2009 10:55 AM
-
Tuesday, December 01, 2009 10:00 PMManfred-
Are we to assume that you have navigated this mine-field successfully then? Have you sucesssfully deployed the FAST beta product?
We are pulling our hair out on this end. thanks for the tips - we are going to attempt the installation using this shorter guide that you provided.
Thx,
Gaylen -
Wednesday, December 02, 2009 4:47 AMWell let use know if you get it working - I have been trying for some time
The section Enable queries over HTTP is just black art.
I ask myself way this is not a a UI .....
I was not able to get this combinatio to work - I'm sorry is it a single line or 2 lines ?
Set-FASTSearchQRProxyMOSSConfiguration -STSThumbprint
$sharepointSTSCert.Thumbprint -RestartServices true -
Wednesday, December 02, 2009 6:16 AM
I have got it working. After i posted my reply i went back and checked everything again.
The one thing i changed is, like Manfred posted, the port number for the FAST Query SSA on page 28.
I used 13287 and followed the directions once more from this page onwards. My query server is: http://fast001.company.com:13287.
Everything works as expected i just have some problems with refinements giving an error on the FAST search center page.
Another thing: i needed to give my service accounts access to the SQL databases for FAST.
Steve: It is one command.
My config file copy and pasted from the one i saved that works:
$sharepointSTSCertFilename = 'c:\MOSS_STS.cer' # Import SharePoint Security Token Service Certificate $trustedPeopleCertStore = new-object System.Security.Cryptography.X509Certificates.X509Store('TrustedPeople', [System.Security.Cryptography.X509Certificates.StoreLocation]::LocalMachine) $trustedPeopleCertStore.Open([System.Security.Cryptography.X509Certificates.OpenFlags]::ReadWrite) $sharepointSTSCert = new-object System.Security.Cryptography.X509Certificates.X509Certificate2 $sharepointSTSCert.Import($sharepointSTSCertFilename) $trustedPeopleCertStore.Add($sharepointSTSCert) $trustedPeopleCertStore.Close() # Configure FAST Search Server to trust SharePoint Security Token Service certificate Set-FASTSearchQRProxyMOSSConfiguration -STSThumbprint $sharepointSTSCert.Thumbprint -RestartServices trueThe following error shows up in my Sharepoint log when i try to refine the search on the page using the "Site" refinement:
FASTQueryInternal::Execute--FAST Search Query Exception when trying to search FAST backend: Invalid refinement token: Invalid character in a Base-64 string. Microsoft.Office.Server.Search.Query.FASTSearchQueryException: Invalid refinement token: Invalid character in a Base-64 string. at Microsoft.Office.Server.Search.Query.Gateway.FastSearchGateway.AddRefinementFilters(IQuery query, StringCollection refinementFilterList) at Microsoft.Office.Server.Search.Query.Gateway.FastSearchGateway.ExecuteSearch(SearchRequest request, String queryString) at Microsoft.Office.Server.Search.Query.Gateway.AbstractSearchGateway.Search(SearchRequest request) at Microsoft.Office.Server.Search.Query.FASTQueryInternal.ExecuteSearch(SearchRequest request, ResultTableCollection rtc) at Microsoft.Office.Server.Search.Query.FASTQueryInternal.Execute(QueryProperties properties)
Any idea?
Document type and company refinement works fine. -
Wednesday, December 02, 2009 8:40 AMSite refiner does not work in beta 2. I think it is mentioned somewhere in the release documentation under known issues.....
-
Wednesday, December 02, 2009 9:29 AMWell that explains.......
Glad it was not me misconfiguring things :) -
Wednesday, December 02, 2009 2:47 PMHi Manfred,
Thanks for the details. Unfortunately for me I am still unable to get this working. Can I ask you the following questions:
1. What OS are you running on (I am on WIN2008 R2)
2. Have you installed FAST on the same server as SharePoint or on a different server.
3. If you have installed FAST on a different server can you tell me on which server you are running each of your PowerShell scripts.
4. The FAST Deployment guide asks you to configure the default service application configuration so that your web apps use the newly created FAST Query SSA instead of the default SharePoint Search Service, Are you doing this step.
Thanks again for the details, hopefully I'll get it working soon.
Colin -
Wednesday, December 02, 2009 4:48 PMWell, i am not Manfred but i'll take a shot. Feel free to ignore it.
Also running R2 64 Bit on Hyper V
FAST is installed on a different server. They both share the same SQL server.
Power shell scripts are run on the Sharepoint server for the export cert bit. The other script i posted above is running on the FAST server.
I have created the SSA and configured it on my webapps.
I created a blank web app this time and did not use the configuration wizard. -
Wednesday, December 02, 2009 8:37 PMHi
Pants79 already answered your questions I hope.
Some additions which might help.
All Powershell Cmdlets containing *FAST* run on the FAST Backend servers, all other which contain *SP* run on the SahrePoint nodes.
About point 4. That really depends on how you setup the connection between the SSA (Search Service Application) and the FAST backend.
If you created a new SSA for searching with FAST you have to set this newly created SSA to the Web-App you have want to search from.
This is done in the CentralAdmin->"Manage Web Applications". There select your WebApplication and from the ribbon choose "Service Connections".
From there you will get a popup where youo can select "custom" and select all service apps which you use. (Probably All). If you have multiple SSA's select the one you just created and also klick on "Set as default".
From that point on all the searches on this web-app will use the FAST SSA to search. -
Wednesday, December 02, 2009 10:25 PM
I started with a new VM server but kept my SharePoint Server but removed all the connections and the fastdatabase.
Reworked my FAST Server and I did not have any errors etc.
As best I can tell having gone through the document many times I feel I did everything as mentioned but still getting the error
Port 13287 is not open
but 13285 and 13286 is
I used 13286 as per the info_text file
In the logs I get
Exception FASTQueryInternal::Execute--FAST Search Query Exception when trying to search FAST backend: An error occurred while receiving the HTTP response to http://fc-vm409.ptcnet.ptc.com:13285/qrsproxyClaims. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. Microsoft.Office.Server.Search.Query.FASTSearchQueryException: An error occurred while receiving the HTTP response to http://fc-vm409.ptcnet.ptc.com:13285/qrsproxyClaims. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shuttin...
Which does point to the wrong port or something else.
Do I have to rebuild my SharePoint Server?
I'm pretty disappointed, thought today I would be able to get it going
Any help would be greatly appreciated - I know I getting lots of suggestions and I really apprecaite the help.
Steve GW -
Thursday, December 03, 2009 9:03 AMI don't know if it opens the HTTP port only after you have modified the QRProxy config and uncommented the HTTP stuff in it.
After this you run the script i posted above which restarts the FAST services.
I had the exact same error you got. -
Thursday, December 03, 2009 10:51 AMThanks to both Pants79 and Manfred for their help. I now have what appears to be the correct connectivity in place both on port 13286 and 13287. What my experience is now is that when I do a search I get no results back.
On my FAST search page I try to search for text that I know is on a site and I don't get any results. What I can see is that in the following folder on the FAST server:
C:\FASTSearch\var\log\querylogs
I can see various query_log.YYYYMMDDTTTTTT files that do have some contents in them which appear to match my searches from the FAST search however I don't get any results.
I have done content crawls using the FAST Connector and the FAST Query but to no avail. -
Thursday, December 03, 2009 11:17 AMI had this also, it wasn't until after i crawled my Sharepoint server that i got results, i had a fileshare setup first.
I hope they make the setup easier on release. It isn't really obvious how stuff works. -
Thursday, December 03, 2009 3:55 PMManfred, Colin, Pants79
I too now have a FAST server running and the port number I vote for is 13287 :-)
Thanks to you all for helping.
I kept the faith and kept trying.
Next is People search
Steve GW -
Thursday, December 03, 2009 4:02 PMGood to hear :)
It is nice though, when you get it running that is. :) -
Thursday, December 03, 2009 4:41 PMRe: Manfred Berry:
I was curious by the depth of knowledge in his first post from someone who didn't list himself as Microsoft, so I had a quick look and found Manfred Berry listed as a developer at Fast, "A Microsoft company".
(Source: http://espwebparts.codeplex.com/team/view admittedly codeplex but there's an official Fast logo on that page)
Too much of a coincidence to be anything but the same guy so ...
Please Manfred change your Display Name for posts you make to the SharePoint 2010 forums. I don't care if it says MSFT or FAST but it should say one or the other. Failing that your sig should say so.
(Moderator)
P.S. The forum system spots some people - so for instance Jie Li is listed as "Jie Li - SharePoint MSFT" of which MSFT has been automatically added but clearly it isn't spotting that you work for a MSFT company because there is no "MSFT" after your forum display name, so we need that information provided by you in some way.
FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com
Complete Book Lists (incl. foreign language) on each site.- Edited by Mike Walsh FINMicrosoft Community Contributor Thursday, December 03, 2009 4:54 PM (Source: ... ) added
-
Friday, December 04, 2009 8:26 AMHi Mike
Wow that was a friendly post :-)
It's nice to feel like an ____ after trying to help people.
I just created the account here because I tried to help people as fast as possible and I was not aware of the "fact" that it was so important to have a full profile filled in. And obviously others in this forum are neither.....
I have updated my profile now.
Regards,
Manfred -
Friday, December 04, 2009 8:39 AM> Wow that was a friendly post :-)It was not intended to be unfriendly and I can identify nothing unfriendly in the wording of it.It was merely asking you to identify yourself as working for Microsoft as the system apparently isn't picking that fact up and is therefore not identifying you automatically as MSFT.Mike WalshP.S. Thanks for the new and clear name. I have the reverse problem in that I have MVP in the name and I'm getting the MVP automatically as well. Unfortunately the system doesn't accept me changing my name to Mike Walsh.
FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com
Complete Book Lists (incl. foreign language) on each site. -
Friday, December 04, 2009 9:43 AM
I have written a blog post on http://blogs.msdn.com/mberry/archive/2009/12/04/configuring-sharepoint-2010-for-fast-search-server-query-and-admin.aspx which hopefully answeres most of the questions in this thread.
>I hope they make the setup easier on release. It isn't really obvious how stuff works
Agree! -
Friday, December 04, 2009 10:43 AMHi Manfred,
Thanks for posting the article on your blog. Can you check your port numbers in the article, your diagram states the port number for the admin service is 13257 but then your script later has it as 13256 (just a wee typo I'm sure but it might confuse someone).
I would have commented on your blog post but anonymous comments are disabled.
Colin -
Friday, December 04, 2009 3:13 PMThanks a lot Colin.
Have fixed that now.
-Manfred -
Friday, December 04, 2009 4:11 PMJust one more wee thing that might seem obvious but caught me out. I finally got everything working and was seeing some results. The thing was I was only seeing results that were from the mysite host site collection and not from any of the other site collections I had set up. I finally realised that the my site host is setup by default to allow "NT AUTHORITY\Authenticated Users" read permission.
None of the other sites I had setup were configured with any permissions other than the domain administrator was a site collection administrator. I had been running everything as the domain administrator and just didn't think I'd need to alter any site level permissions. None of the crawl logs indicated that there was a problem, indeed the standard SharePoint search was returning items from all the other site collections when I was using that.
So, I added the "NT AUTHORITY\Authenticated Users" group read permissions on each of the other site collections and voila, I was getting back search results from all my sites.
Fantastic, now I can go ahead and convince our IT leadership team that they absolutely *must* upgrade to SharePoint 2010 and FAST as soon as it's available as I can get all the brilliant demos I seen at the conference put together in a context that my company will understand.
Manfred, Pants79, Steve, Have a great weekend and (as we say in my part of the world) "lang may yer lum reek" :-) -
Thursday, December 10, 2009 9:29 AMput together in a context that my company will understand.
I've found that this is really important when demo'ing Sharepoint.
Too bad it usually takes quite a lot of work to get that far.
Sample BCS connection to existing backends.
Sample data.
etc. etc.
Nice you got it working. -
Friday, December 11, 2009 9:25 AMOnly documents accessible to the user running the query will appear in search results. If you query as your crawl account, everything should be visible. From your description, it looks like all the documents have been crawled, and there should thus be no warning in the crawl logs. It is just the security trimming of the results that prevents non-authorized users to see them.
I'll have to take a rain check for the difference wrt search server displaying results from sites where access has not been granted. -
Tuesday, December 15, 2009 11:47 PM
Got it working! Thanks!!!!
After completing the steps above mine was still not working so I went into the MOSS admin and checked the properties on my FAST Query SSA. Even through I had changed the port and protocol using Powershell and verified the changes in Powershell the old values still persisted in the Admin UI. So I changed them and IISRESET'ed and it works now.- Proposed As Answer by mashby Wednesday, December 16, 2009 12:34 AM
-
Friday, January 08, 2010 9:33 AM
I get the following error when I execute a query
Could not connect to http://fastsrv2010.sps2010.com:13287/qrsproxyClaims. TCP error code 10061: No connection could be made because the target machine actively refused it 129.227.130.47:13287
In the fast server there isn't any process listening in port 13287
¿Any Ideas?
Thanks
Angel.
Saludos -
Friday, January 08, 2010 9:43 AMColin,
Finally, can you see any process listening on ports 13287 in resource monitor?
Saludos -
Monday, January 18, 2010 8:40 AM
Hi all,
Please clarify where i am going wrong -Below are the steps which i followed
- Installed the Fast Search server 2010
- Configured the Fast Search Connector - with content distributor - 13329
- Configured Fast Search Query Service - with Query Service at port number -13287,Administrative Service - 13256 ,Resource store location -13255
- Crawled the content sucessfully
- Created a Fast Search Site
- Tried to search a document - "Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator".
I Tried with various port numbers but no luck.Please some body suggest what i can do in order to make it work....?
Rajee
-
Monday, February 22, 2010 4:54 PM
I followed the steps exactly but still got the same WebPart error.
does it make any differencies if I have to run all of the services on one server for trial? I've also followed the export/ import cert steps on this server.
Insecure is enabled in the query config file.
Any comments? -
Sunday, April 18, 2010 10:55 AM
same case, same error mesg here.. multiple deployment, still same error mesg
but yes everytime see this firewall mesg, i ignore it..
seems u will make me try it with firewall enabled and see what happens
-
Sunday, April 18, 2010 2:09 PM
ohhhhhhhhhhhhh worked for meeeee
changing the port and doing the certificate again this work like sharp.... oh yes thanks thanks thanks...
to MANFRED NYSTED BERRY THANK YOUUUUUUUUUUUUU
.png){kind=spacer}
