Skip to main content

SearchServiceApplicationProxy Unable to connect with the Fast Service Proxy (Bug)

SharePoint 2010 getting search keyword: we were writing a custom code to get the Search keyword & best bets, we used the FAST Search Proxy. The big bug found & that mentioned below. Special thanks for Mikael Svenson. He already did a lot of research on it.

var ssaProxy = (SearchServiceApplicationProxy)SearchServiceApplicationProxy.GetProxy(SPServiceContext.Current);
if (ssaProxy.FASTAdminProxy != null) Error line
{
var fastProxy = ssaProxy.FASTAdminProxy;
KeywordContext keywordContext = fastProxy.KeywordContext;
var searchGroup = (from x in keywordContext.SearchSettingGroups wherex.Name==SPContext.Current.Site.ID.ToString() select x).First();
 }

Above code was not working, the problem was Fast Search Service Proxy unable to connect with the search service.

The FASTAdminProxy reads it’s WCF configuration from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\FASTSearchAdmin\ContentCollectionService\client.config.
Service keep searching for the service name “ContentCollection.svc” at location folder %FASTSEARCH%\components\admin-services\. But on the FAST server the endpoint is named “ContentCollectionService.svc”

Thanks to Mikael Svenson Post “http://techmikael.blogspot.in/2011/08/working-with-content-collections-via.html

The fix is simple and involves making a copy of this file
%FASTSEARCH%\components\admin-services\contentcollectionservice.svc

Paste it at same location and change its name “contentcollectionservice.svc” to “contentcollection.svc”

%FASTSEARCH%\components\admin-services\contentcollection.svc



After that I deployed my custom web service. Guess what…L another issue encounter. Custom Service that consuming the fast Admin proxy throwing error “FAST Search - Unexpected error occurred while communicating with Administration Service”. The Application pool account of the Web Application does not have access to the FAST search engine.

Resolution
Add the Application Pool account to 'FASTSearchAdministrators' group
  • Open Active Directory Users and Computers
  • Navigate to domain control in the tree view
  • Click on Users and look for “FASTSearchAdministrators” group (In general, this group can be found in the 'Local Users and Groups' on the
  • systems that have FAST search installed)
  • Add the application pool account for the web application to this group.

Comments

Popular posts from this blog

SharePoint RPC Protocols Examples Using OWSSVR.DLL

What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView  Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...

SharePoint 2013 Search Database Part 1

SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database  In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...

STS CryptographicException Error : Key set does not exist

Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification.  Solution to this problem Set the same identity pool to  : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis