none
CustomPropertyExtractor not giving any results. RRS feed

  • Question

  • Hi,

    I was trying to use the custom property extractor of FAST .I followed the link

    http://msdn.microsoft.com/en-us/library/ff795797.aspx

     and created the custompropertyextractor.xml.Crawling went through fine.But on trying to add refinement based on the managed property which i added for holding the custom property i was not getting any value. SO i tried raw xml to see if that particular managed property is fetching values. To my disappointment the managed property was not fetching any values. DO i need to do any additional steps other than those explained in this link.

    Also in the link  they are mentioning about  a step for normalizing the xml using a lowercase tool. I didn't find any such tool so i skipped that step.Does it affect my result set in any ways? 

    I checked my logs and i didnt see any error.do we need to add any step in the pipelineconfig.xml or the optionalprocessing.xml as i can see my custompropertyextractor is not been called anywhere.

    please advice.

    Thanks in advance,

    Rush

    Monday, August 1, 2011 12:50 PM

All replies

  • After installing SP1, did you execute

    ".\psconfig.ps1 –action p" as per http://technet.microsoft.com/en-us/library/hh285624.aspx

    in order to add the new extractor stages to your pipeline configuration?

    If not, the stage is not added, and thus not executed.

    Regards,
    Mikael Svenson 


    Search Enthusiast - SharePoint MVP/WCF4/ASP.Net4
    http://techmikael.blogspot.com/
    Monday, August 1, 2011 6:25 PM
  • Hello Mikael,

    I could not successfully run .\psconfig.ps1 –action p.I get the following error.


    Unable to regenerate schema. Please check that the user running this script is a member of the FASTSearchAdministrators group and that the admin services and configuration server are running. Unable to apply schema updates. Please check that the user running this script is a member of the FASTSearchAdministrators group and that the admin services and configuration server are running.

     

    Technet Troubleshoot :

    Cause: The World Wide Web Publishing Service has stopped.

    Resolution: Start the World Wide Web Publishing Service and re-run the post-setup configuration script: .\psconfig.ps1 –action p

    Confirmed that the WWW Publishing service is running and the account has admin group access.

     

    Any suggestions?

     

    Regards,

    Thursday, August 25, 2011 7:58 PM
  • Hi,

    Have you opened a FAST Powershell window with admin rights, and made sure the logged in user is a member of the FASTSearchAdministrators group?

    Regards,
    Mikael Svenson 


    Search Enthusiast - SharePoint MVP/WCF4/ASP.Net4
    http://techmikael.blogspot.com/
    Thursday, August 25, 2011 9:17 PM