This article describes the issues that are fixed in the Microsoft FAST Search Server 2010 for SharePoint hotfix package that is dated October 8, 2013.
Issues that this hotfix package fixes
When you use a JDBC database connector to extract numeric data for indexing, the numeric data is converted to float values. Therefore, search results are less accurate.
Note After you apply this hotfix, you can add the following parameter to the JDBC connector configuration file to improve the accuracy of the search results:
<group name="Normalization" expand="no">
<![CDATA[The parameter in the "Normalization" group is defining if double precision should be used for indexing when available from the database]]>
<parameter name="UseDoublePrecision" type="boolean">
<![CDATA[If true, double values will be passed for indexing when the retrieved data is a double.
If you want double values extracted from the database to be fed to the search engine as double values, set the value in the code to true.
If you want numeric data to be converted to float values, set the value in the code to false, or remove the parameter from the JDBC connector configuration file.
When you extract content from the SharePoint Server 2010 Indexing Connector for Documentum, some usernames that contain a mix of upper and lowercase letters are not displayed in the Active Directory Lightweight Directory Services (AD LDS) service.
When you perform a crawl on a SharePoint Server 2010 site, you receive the following error message:
AddDecimalNumber(bi1, bconamount, number1) failed: Could not convert decimal number 'number1' to an integer using 0 digit decimal precision.
To make sure that all binary and configuration files are updated correctly, you must run a PSConfig script after you apply this hotfix package on all FAST Search nodes.
For more information about this PSConfig script and how to install updates on FAST Search Server 2010 for SharePoint, go to the following Microsoft TechNet website:
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.
To install this hotfix, you must have either FAST Search Server 2010 for SharePoint Service Pack 1 (SP1) or SP2 installed. For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
2510766 List of all SharePoint 2010 and Office Server 2010 SP1 packages
2687522 List of all SharePoint 2010 and Office Server 2010 SP2 packages
You do not have to restart the computer after you install this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
To use the hotfix in this package, you do not have to make any changes to the registry.
This hotfix package may not contain all the files that you must have to fully update a product to the latest build. This hotfix package contains only the files that you must have to resolve the issue that 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.