Summary

This article describes the Microsoft FAST Search Server 2010 issue that is fixed in the hotfix package that is dated October 29, 2010.

INTRODUCTION

Issue that this hotfix package fixes

In FAST Search Server 2010 for SharePoint, you may experience the following issues:

  • Assume that a FAST Search Server 2010 for SharePoint system contains two or more content distributors. When the primary content distributor is restarted, crawling may fail.

  • Consider the following scenario:

    • You have a FAST Search Server 2010 for SharePoint environment.

    • You create a file share library, and then you only grant the ListFolder / ReadData permission to groups or to users.

    • A user searches files that are located in the file share library.

    In this scenario, the files still display in the search results.

  • Consider the following scenario:

    • You perform a full backup or a full restore on a large scale FAST Search Server 2010 for SharePoint installations.

    • Meanwhile, one or more regular network communication issues occur.

    In this scenario, the full backup or the full restore may never finish.

  • Consider the following scenario:

    • You enable query refinement for a managed property in FAST Search Server 2010 for SharePoint.

    • You delete the managed property.

    • You create a new managed property that uses the same name as the deleted one. However, you change the data type of the new managed property.

    • You enable query refinement for the new managed property.

    • You perform a search.

    In this scenario, the search crashes.

  • In FAST Search Server 2010 for SharePoint, the Get-FASTSearchMetadataCrawledProperty cmdlet that specifies the -Name parameter to a crawled property takes a long time to finish on installations that have many crawled properties. After you apply this hotfix, the execution time of the Get-FASTSearchMetadataCrawledProperty cmdlet is reduced significantly when the cmdlet specifies the -Name parameter. Additionally, the Get-FASTSearchMetadataCrawledProperty cmdlet supports wildcard characters in the -Filter parameter.

  • When you try to implement a query with the numeric refiner in FAST Search Server 2010 for SharePoint, the query never presents the value 0 (zero). Therefore, you cannot drill down on results that have the value 0 (zero) for this managed property.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites



No prerequisites are required for installing this hotfix package.

Restart requirement

You may not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download information

File name

File version

File size

Date

Time

Platform

Fastsearchserver2010-kb2449730-fullfile-x64-glb.exe

14.0.5128.5001

5,490,696

22-Oct-2010

12:54

x86




Microsoft Windows Installer .msp file information

File name

File version

File size

Date

Time

Platform

Fsserver-x-none.msp

Not Applicable

4,724,224

22-Oct-2010

20:13

Not Applicable





After the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:
Fsserver-x-none.msp information

File name

File version

File size

Date

Time

Platform

Contentdistributor.exe

14.0.317.12

2,482,736

06-Oct-2010

11:51

x64

Fsearch.exe

14.0.317.12

14,951,840

06-Oct-2010

11:51

x64

Microsoft.sharepoint.search.extended.administration.dll

14.0.317.12

325,536

06-Oct-2010

11:51

x86

Microsoft.sharepoint.search.extended.administration-services.dll

14.0.317.12

446,880

06-Oct-2010

11:51

Not Applicable

Microsoft.sharepoint.search.extended.installer.mahasen.common.dll

14.0.317.4

156,064

13-Jul-2010

06:05

Not Applicable

Microsoft.sharepoint.search.extended.installer.mahasen.validationframework.dll

14.0.317.4

59,296

13-Jul-2010

06:05

Not Applicable






References

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updatesFor more information about disjoint networks, visit the following Microsoft TechNet website:
Understanding disjoint namespace scenarios

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×