Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Description of the FAST Search Server 2010 for SharePoint hotfix package (fsserver-x-none.msp): August 31, 2010


View products that this article applies to.

Summary

This article describes the Microsoft FAST Search Server 2010 issues that are fixed in the hotfix package that is dated August 31, 2010.

↑ Back to the top


INTRODUCTION

Issues that this hotfix package fixes

When you install the FAST Search Server 2010 for SharePoint in a disjointed network environment, the Post Setup Configuration of FAST Search Server 2010 for SharePoint fails. Additionally, you receive the following error message:

Exception - System.ArgumentException: A problem occurred when retrieving information on machine: fast-search-servername.subdomain.DomainName.com. Make sure the machinename is spelled correctly and that the machine is available ---> Microsoft.SharePoint.Search.Extended.Installer.Mahasen.Common.IPSec.IPSecException: Exception occurred while looking up the SID for machine: "servername.subdomain.DomainName.com". LDAP Filter: "(&(objectCategory=computer)(objectClass=computer)(cn=fast-search-servername))". Path: "LDAP://DC=domaincontroller,DC=DomainName,DC=com". ---> System.DirectoryServices.DirectoryServicesCOMException (0x8007202B): A referral was returned from the server.



   at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)

   at System.DirectoryServices.DirectoryEntry.Bind()

   at System.DirectoryServices.DirectoryEntry.get_AdsObject()

   at System.DirectoryServices.DirectorySearcher.FindAll(Boolean findMoreThanOne)

   at Microsoft.SharePoint.Search.Extended.Installer.Mahasen.Common.IPSec.LDAPInformationRetriever.GetSID(String machineName)

   --- End of inner exception stack trace ---

   at Microsoft.SharePoint.Search.Extended.Installer.Mahasen.Common.IPSec.LDAPInformationRetriever.GetSID(String machineName)

   at Microsoft.SharePoint.Search.Extended.Installer.Mahasen.Common.IPSec.LDAPInformationRetriever.GetSID(String machineName, String user, String password)

   at Microsoft.SharePoint.Search.Extended.Installer.Mahasen.Common.IPSec.MachineManager..ctor(String localMachineName, IEnumerable`1 machineNames, String domainUser, String domainUserPassword, ILogWriter logWriter, ILDAPInformationRetriever ldapinfoRetriever, IDNSInformationRetriever dnsinfoRetriever)

   --- End of inner exception stack trace ---

   at Microsoft.SharePoint.Search.Extended.Installer.Mahasen.Common.IPSec.MachineManager..ctor(String localMachineName, IEnumerable`1 machineNames, String domainUser, String domainUserPassword, ILogWriter logWriter, ILDAPInformationRetriever ldapinfoRetriever, IDNSInformationRetriever dnsinfoRetriever)

   at Microsoft.SharePoint.Search.Extended.Installer.Mahasen.Common.IPSec.MachineManager..ctor(String localMachineName, IEnumerable`1 machineNames, String domainUser, String domainUserPassword, ILogWriter logWriter)

   at Microsoft.SharePoint.Search.Extended.Installer.Mahasen.Common.IPSec.IPSecManager.CreateIPSecRules(String localMachineName, ICollection`1 hostNames, Int32 basePort, String groupname, String domainUser, String domainUserPassword)

   at Microsoft.SharePoint.Search.Extended.Installer.Mahasen.Cmdlets.SetIPSecCommand.CreateRules(ICollection`1 hostnames, IHostConfig hostConfig)

   at Microsoft.SharePoint.Search.Extended.Installer.Mahasen.Cmdlets.SetIPSecCommand.CreateAdminRules(IHostConfig hostConfig)

   at Microsoft.SharePoint.Search.Extended.Installer.Mahasen.Cmdlets.SetIPSecCommand.ProcessRecord()

↑ Back to the top


More Information

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: Note 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.


Note After the installation is complete successfully, please run the psconfig.ps1 PowerShell cmdlet from an elevated PowerShell prompt, and add the following additional command-line parameter:disjointNamespace

For example:
.\psconfig.ps1 -action i -roleName admin -userName DOMAIN\username -localMachineName fast-search-servername.subdomain.DomainName.com -databaseConnectionString sqlserver.subdomain.DomainName.com -databaseName FAST_Search_database_name -disjointNamespace

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 nameFile versionFile sizeDateTimePlatform
Office-kb2308915-fullfile-x64-glb.exe14.0.5123.50001,015,66413-Aug-201010:59x86


Microsoft Windows Installer .msp file information


File nameFile versionFile sizeDateTimePlatform
Fsserver-x-none.mspNot Applicable1,022,46412-Aug-201023:03Not 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:
File nameFile versionFile sizeDateTimePlatform
Microsoft.sharepoint.search.extended.installer.mahasen.common.dll14.0.317.4156,06413-Jul-20106:05Not Applicable
Microsoft.sharepoint.search.extended.installer.mahasen.validationframework.dll14.0.317.459,29613-Jul-20106:05Not Applicable




↑ Back to the top


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 updates
For more information about disjoint networks, visit the following Microsoft TechNet website:
Understanding disjoint namespace scenarios

↑ Back to the top


Keywords: kbcu, kbsurveynew, kbexpertiseinter, kbqfe, kbhotfixserver, kbhotfixrollup, kbautohotfix, kb

↑ Back to the top

Article Info
Article ID : 2308915
Revision : 4
Created on : 9/19/2018
Published on : 9/19/2018
Exists online : False
Views : 380