1

SharePoint Search Server Express 2010, Why is Rank Returned from Scope() Always Default (100000000)

I need to know what I need to do differently in terms of configuration changes, etc. within Search Server Express to have this rank issue resolved.

I have crawled a very large number of files using Search Server Express 2010 and when I select rank from Scope using QueryText (for a given search term), I always get the same rank for all returned items, 100000000.

Because of this, order by rank makes no difference. I need the rank to reflect the number of occurrences of the particular term in each file. Rank used to vary (and be correct) when SSE 2010 was installed on Windows Server 2008 R2, but with Windows Server 2016 the rank is always 100000000.

For example, If File A has "oil" 1 time, File B has "oil" 3 times and File C has "oil" 4 times, the current order returned from the select below, with the order by, is: File A, File B, File C (because that is the order in which the files were crawled, and each file unfortunately returns the rank of 100000000 for each file). The order I need to have returned, with the order by, is: File C, File B, File A (with File C having a larger rank than B, and B having a larger rank than A, so that the order by rank can order things correctly).

I call method Query of the built in SOAP Service that comes with Search Server Express 2010 (_vti_bin/search.asmx) and pass the following:

<QueryPacket><Query><QueryId /><OriginatorId /><Context>
<QueryText type='MSSQLFT' language='" + language + "'>
   SELECT rank, Filename, path, description FROM SCOPE()
   where (path like 'file://" + RepositoryFiles + "/%.xml')
    and (contains(All, '"oil*"')) 
    order by rank desc
 </QueryText>
 </Context>
 <EnableStemming>true</EnableStemming>
</Query></QueryPacket>;

I very much appreciate insight that can lead to a resolution of this issue.

Improve this question
4
  • MSSE doesn't support Windows Server 2016 and will fall out of support in mid-October of this year. Is there a reason you don't move to a newer solution?
    – user6024
    Commented Jul 19, 2020 at 18:52
  • Thanks. I see now that the download page says "Windows Server 2008 R2, Windows Server 2008 Service Pack 2, Windows Server 2012" and that I will need to look at an alternative. What would the newest solution (the "inheritor to MSSE") be, which can do what MSSE did? SharePoint Server 2019? I just need to crawl xml files and be able to call an asmx or rest service to get results, using an straightforward query like in my example.
    – MikeDev
    Commented Jul 20, 2020 at 12:00
  • SharePoint Server 2019 would be the latest, yes.
    – user6024
    Commented Jul 20, 2020 at 15:13
  • Great, I will pursue that. Thanks again. Please answer with your above notes within the "Answer the Question" area so I can give you the bonus.
    – MikeDev
    Commented Jul 20, 2020 at 16:00

1 Answer 1

Reset to default
0
+100

As MSS(E) will be out of support in October 2020, I would suggest using SharePoint Server 2019.

I would also look at using the REST API rather than the web service as web services have begun their deprecation, starting with the List Web service in 2019.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.