I have two WFEs in my environment running SP2010 and FAST Search Server 2010 on a Fast Content Service SSA. There are 9 site collections that are covered in the Content Source of that SSA. I have a file called "uniqueFile.txt" and it's part of the Site Assets of each site collection.

When I run a search for "uniqueFile.txt" it shows 17 results with 16 duplicates. Half of these duplicates are because this same file exists at different locations, however the other half of the results return are pointing to the exact same file twice (Same URL, same doc id.. etc).

I have gone through the crawl logs and these files have been crawled multiple times and each time it has the same Crawl ID.

What troubleshooting steps can you recommend?

  • Sounds like the search index and crawl log is not in sync. Have you ever done index resets without clearing the FAST collection? Oct 22, 2015 at 15:01
  • No I haven't done that - is this what you're talking about Reset the content index?
    – Matty_R
    Oct 23, 2015 at 1:07
  • Mikael - I tried as you suggested in my DEV environment to see if I could replicate the problem but it didn't seem to have an effect.
    – Matty_R
    Oct 23, 2015 at 2:49
  • Mikael - I did it about 10-15 times in my DEV environment to see if I could break it and it looks like i've been able to replicate the issue. Thanks heaps mate, this issue has been haunting our production environment for a while now.
    – Matty_R
    Oct 23, 2015 at 3:33
  • 1
    I did an index reset and then a full crawl without clearing the FAST collection about 10-15 times which eventually reproduced the problem. Then I did an index reset, cleared the FAST collection, and then full crawl which fixed the issue.
    – Matty_R
    Oct 24, 2015 at 8:39

2 Answers 2


When you do an index reset with FAST in central admin you also have to clear the content collection using powershell from one of the FAST servers. This ensures the crawl database and index are in sync.

  • It looks like after a few weeks the problem has reoccured, this time I know there hasn't been any index resets or clearing of the FAST collection.
    – Matty_R
    Nov 12, 2015 at 6:23
  • What kind of crawl schedules have you set up, and weird indeed. Nov 12, 2015 at 11:25
  • Nothing out of the ordinary - it does an incremental every 30 mins and a full crawl every week.
    – Matty_R
    Nov 12, 2015 at 21:55

The overall fix was to turn off Case Sensitive Crawling:

SharePoint Powershell:

$ssa = Get-SPEnterpriseSearchServiceApplication "FAST Content Service App"

This should return False.


This should return True.

Perform an index reset, following the instructions for clearing on the FAST Server also.

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.