Article ID: 905216 - Last Review: September 26, 2007 - Revision: 2.4 You cannot query a specific search server in a server farm deployment of SharePoint Portal Server 2003Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986
(http://support.microsoft.com/kb/256986/
)
Description of the Microsoft Windows registry On This PageSYMPTOMSWhen you search your server farm deployment of Microsoft SharePoint Portal Server 2003, there is no supported method to query a specific search server directly. This issue can make troubleshooting difficult to determine which search server is behaving unexpectedly. RESOLUTIONThis problem was first fixed in a hotfix that is now contained in a service pack. If you installed the latest SharePoint Portal Server 2003 service pack, you do not have to install the hotfix. Service pack informationThis problem is corrected in SharePoint Portal Server 2003 Service Pack 3. To resolve this problem, obtain the latest service pack for SharePoint Portal Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:889380
(http://support.microsoft.com/kb/889380/
)
How to obtain the latest service pack for SharePoint Portal Server 2003 After you install the service pack, follow the steps that are listed in the "How to enable the hotfix" section of the article to set the AllowSearchServerInQueryString registry key and to activate the hotfix. Hotfix informationHow to obtain the hotfixThis issue is fixed in the SharePoint Portal Server 2003 hotfix packages 919175 and 898547. For more information about the English version of this hotfix package, click the following article number to view the article in the Microsoft Knowledge Base:919175
(http://support.microsoft.com/kb/919175/
)
Description of the SharePoint Portal Server 2003 post-Service Pack 2 hotfix package: June 16, 2006
For more information about the German and the Spanish versions of this hotfix package, click the following article number to view the article in the Microsoft Knowledge Base:
898547
(http://support.microsoft.com/kb/898547/
)
Description of the SharePoint Portal Server 2003 post-Service Pack 2 hotfix package: October 24, 2005
How to enable the hotfixWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.To enable this hotfix, follow these steps:
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in SharePoint Portal Server 2003 Service Pack 3. MORE INFORMATIONAfter you apply this hotfix, you can query an individual server. In a query that is similar to the following query, specify the server name in front of the catalog name: Select "dav:href" from servername.catalogname..scope() where contains('microsoft') Note In the example query, the servername placeholder must be replaced with the name of the search server that you want to interrogate. The catalogname placeholder should be replaced with the catalog from which you want to obtain results.There is no out-of-the-box ability to perform this kind of query in Microsoft SharePoint Portal Server. You must create a custom query interface to use this syntax. For more information, see the Microsoft Office SharePoint Products and Technologies 2003 Software Development Kit (SDK). To obtain this SDK, visit the following Microsoft Web site: http://www.microsoft.com/downloads/details.aspx?familyid=aa3e7fe5-daee-4d10-980f-789b827967b0
(http://www.microsoft.com/downloads/details.aspx?familyid=aa3e7fe5-daee-4d10-980f-789b827967b0)
| Article Translations
|
Back to the top
