Posts Tagged ‘FAST Search’

From SharePoint administrator to technical decision makers , this session is for you. This session will focuses on Out-Of-Box features and functions, pertinent terminology, capacity planning considerations, and a demonstration & walkthrough of connecting SQL Azure to your FAST for SharePoint 2010 implementation. For the SharePoint administrators the capacity planning and pertinent terminology sections will enable you to implement a successful FAST for SharePoint 2010 implementation. Project managers, Power users, and technical decision makers will benefit most from the Out-Of-Box sections and the SQL Azure demonstration, which will provide a high level view of the capabilities and features of FAST for SharePoint 2010.

Thanks to everyone who came to my presentation today, and asked questions!!

Presentation Download: RBA-FAST_PresentationSPFEST11.pdf

Important Links:

http://www.rbaconsulting.com

http://www.sharepointfest.com/Denver/

 

 

Posted by IsaacBlum at 14 September 2010

Category: Uncategorized

Tags: , , , ,

Come see me at: SRC 102 – FAST for SharePoint 2:00 – 3:15 http://www.sharepointfest.com

This error occurred when clicking “FAST Search Keywords” within the site collection.

Error from ULS Logging : 

Admin OM Exception occurred. Message: Failed to communicate with the WCF service. , Error Code:e107, Stacktrace:Microsoft.SharePoint.Search.Extended.Administration.Common.AdminException: Failed to communicate with the WCF service. —> System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: The trust relationship between the primary domain and the trusted domain failed.   (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: System.SystemException: The trust relationship between the primary domain and the trusted domain failed.      at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed)     at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)     at System.Security.Permissions.IDRole.get_Sid()     at System.Security.Permissions.PrincipalPermission.Demand()     at System.Security.PermissionSet.DemandNonCAS()     at Microsoft.SharePoint.Search.Extended.Administration.WCF.KeywordServiceImpl.GetNamedSearchSettingGroup(String name)     at SyncInvokeGetNamedSearchSettingGroup(Object , Object[] , Object[] )     at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)     at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageR…).     — End of inner exception stack trace —     at Microsoft.SharePoint.Search.Extended.Administration.WCF.ServiceClientExceptionHandler.TranslateException(Exception e)     at Microsoft.SharePoint.Search.Extended.Administration.Common.ServiceClientExceptionHandlingInterceptor.Execute[T](Func`1 target, String errorCode, String[] values)     at Microsoft.SharePoint.Search.Extended.Administration.Common.ServiceClientExceptionHandlingInterceptor.Execute[T](Func`1 target)     at Microsoft.SharePoint.Search.Extended.Administration.WCFClient.SearchSettingGroupCollectionImplWCF.GetSearchSettingGroup(String groupName)     at Microsoft.SharePoint.Search.Extended.Administration.WCFClient.SearchSettingGroupCollectionImplWCF.ContainsSearchSettingGroup(String groupName)     at Microsoft.Office.Server.Search.Extended.Administration.Facade.AdminOMHelperBase..ctor(String siteID)     at Microsoft.Office.Server.Search.Extended.Administration.Facade.KeywordHelper..ctor(String siteId)     at Microsoft.Office.Server.Search.Extended.Administration.Internal.UI.ContextualKeywordManagement.OnLoad(EventArgs e)

 Resolution :

This customer had both DNS issues with the domain controllers in there development environment and they had inactive trusts that remained due to an old company merger.

Thanks http://support.microsoft.com/kb/2293357

  1. Install PDF iFilter 9.0 (64 bit) from http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025 (http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025)
  2. Download PDF icon picture from Adobe web site http://www.adobe.com/misc/linking.html (http://www.adobe.com/misc/linking.html) and copied at C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14TEMPLATEIMAGES
  3. Add the following entry in docIcon.xml file, which can be found at: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14TEMPLATEXML
    <Mapping Key=”pdf” Value=”pdf16.gif” />
  4. Add pdf file type on the File Type page under Search Service Application
  5. Open regedit
  6. Navigate to the following location:
    HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice Server14.0SearchSetupContentIndexCommonFiltersExtension
  7. Right-click > Click New > Key to create a new key for .pdf
  8. Add the following GUID in the default value
    {E8978DA6-047F-4E3D-9C78-CDBE46041603}
    • Name: Extension
      Type: REG_SZ
      Data: pdf
    • Name: FileTypeBucket
      Type: REG_DWORD
      Data: 0×00000001 (1)
    • Name: MimeTypes
      Type: REG_SZ
      Data: application/pdf
  • Restart the SharePoint Server Search 14
  • Reboot the SharePoint servers in Farm
  • Create a Test site (with any out-of-box site template) and create a document library upload any sample PDF document(s).
  • Perform FULL Crawl to get search result.

**FAST Search Info**

By default fast search will index inside of pdf’s, however this would may be necessary to edit/ add this if using a third party IFliter.

Edit this file :

C:FASTSearchetcconfig_dataDocumentProcessorformatdetectoruser_converter_rules.xml

Add this :

<ConverterRules>
<IFilter>
<trust>
<ext name=”.pdf” mimetype=”application/pdf” />
</trust>
</IFilter>
<MimeMapping>
<mime type=”application/pdf”>PDF File</mime>
</MimeMapping>
</ConverterRules>

Run psctrl reset to reset all currently running item processors in the system.

** Please note this is a direct posting from Microsoft http://technet.microsoft.com/en-us/library/ff381261.aspx#BKMK_Configure_ssl_enabled_communication

Follow these below instructions. Take close note to this line, especially the part in BOLD : Navigate to the directory where you copied the securefastsearchconnector.ps1 script and run it, replacing the necessary parameters with the values for your environment. The domain and user name should reflect the details of the user running the SharePoint Server Search 14 (OSearch14) service.

Configure SSL enabled communication

Ff381261.Warning(en-us,office.14).gifWarning:
Configuring SSL enabled communication is mandatory.

 

Secure Sockets Layer (SSL) communication is required to feed content from SharePoint Server 2010 to FAST Search Server 2010 for SharePoint. To enable secure communications, configure the Content SSA to use an SSL certificate for FAST Search Server 2010 for SharePoint. FAST Search Server 2010 for SharePoint generates a self-signed certificate during post-setup configuration. This section describes how to use this certificate to enable SSL communication using the self-signed certificate. It is recommended to use certificates issued by a proper Certificate Authority in production environments, refer to Manage certificates (FAST Search Server 2010 for SharePoint) for advanced instructions.

The following procedure has to be followed at least one time, to enable SSL communication between the SharePoint Server 2010 server that runs the Content SSA crawl component and the FAST Search Server 2010 for SharePoint back-end. If your environment contains additional SharePoint Server 2010 servers running a Content SSA crawl component, additional steps are required to enable SSL communication for those servers. Refer to Multiple server deployment of the Content SSA (FAST Search Server 2010 for SharePoint) for more information.

Ff381261.Important(en-us,office.14).gifImportant:
This procedure includes copying sensitive information. Ensure that the certificate information is kept private.

 

  1. Copy the script securefastsearchconnector.ps1 from the FAST Search Server 2010 for SharePoint admin server to the SharePoint Server 2010 server. The securefastsearchconnector.ps1 script is in the installation folder, under installerscripts.
  2. Copy the certificate file FASTSearchCert.pfx from the FAST Search Server 2010 for SharePoint admin server to the SharePoint Server 2010 server. The certificate file is in the installation folder, under datadata_securitycert.
  3. Open a Microsoft SharePoint 2010 Administration Shell with the Run as administratoroption on the SharePoint Server 2010 server.Navigate to the directory where you copied the securefastsearchconnector.ps1 script and run it, replacing the necessary parameters with the values for your environment. The domain and user name should reflect the details of the user running the SharePoint Server Search 14 (OSearch14) service.

    .SecureFASTSearchConnector.ps1 –certPath “path of the certificatecertificatename.pfx” –ssaName “name of your content SSA” –username “domainusername”

    When prompted to enter the certificate password, enter the certificate password that you supplied when you ran the post-setup configuration of FAST Search Server 2010 for SharePoint.

    Ff381261.Important(en-us,office.14).gifImportant:
    The script verifies the connection to FAST Search Server 2010 for SharePoint. Therefore, make sure that all servers in the FAST Search Server 2010 for SharePoint farm are running before you run this script.
  • Archives

  • Tags

  • Subscribe
  • Pages

  • More

  • Disclaimer…

    This is my personal weblog. The opinions expressed herein are my own and are not representative of any 3rd party influence. The owner of this blog reserves the right to edit or delete any comments submitted to this blog without notice if they are deemed to be spam, offensive or otherwise inappropriate. The owner of this blog makes no representations as to the accuracy or completeness of any information on this site or found by following any link on this site. The owner will not be liable for any errors or omissions in this information nor for the availability of this information. The owner will not be liable for any losses, injuries, or damages from the display or use of this information.


    Lastly, I do my best to document my sources if the article is not of my own creation. If I have missed or forgotten to source your work. I would love feedback via the comments section. Thank you.

DreamHost promos
SiteLock