Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 905424 - Last Review: September 12, 2006 - Revision: 3.3
Some of the advanced search options are missing from the Search Results tab when you use FrontPage to insert a Current Web component into a Web page
Important 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://kbalertz.com/Feedback.aspx?kbNumber=256986/
)
Description of the Microsoft Windows registry
SYMPTOMS
Consider the following scenario. You use Microsoft FrontPage to insert a
Current Web component into a Web page. The Web page is located on a Microsoft Internet Information Services (IIS) Web server. Additionally, the Web server is running Microsoft Windows Server 2003 Service Pack 1 (SP1). In this scenario, you may notice that some of the advanced search options are missing from the
Search Results tab of the
Search Form Properties dialog box. If you try to use the Web page, the Web page uses Indexing Service, and search results are returned as expected.
CAUSE
This behavior occurs because the version of FrontPage 2002 Server Extensions that is included with Microsoft Windows Server 2003 SP1 provides the Integrated Indexing Server Search functionality. In Integrated Indexing Server Search, the
Search Results tab of the
Search Form Properties dialog box looks similar to the user interface for the FrontPage WAIS search engine.
By default, you use the registry to define the search scope on server side in Windows Server 2003 SP1. You cannot define the search scope on client computer.
WORKAROUND
Warning 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 work around this behavior, remove the SearchCatalogName registry subkey:
- On the Web server, click Start, click Run, type regedit in the Open box, and then click OK.
- Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\SharedTools\WebServerExtensions\Ports\Port#
- Right-click the SearchCatalogName registry subkey, click Delete, and then click Yes.
- Quit Registry Editor.
- Click Start, click Run, type iisreset in the Open box, and then click OK.
After you change the registry, the
Scope of Search section and the
Additional information to display in the Search Results list section appear on the
Search Results tab. The
Scope of Search section includes the following options:
- Entire Web site
- This Web site
- Directory
- Maximum records per page
- Maximum records per query
Note This workaround disables the Integrated Indexing feature for this Web site. If the server has multiple Web sites that use Integrated Indexing (single catalog), and if you are disabling this feature only for specific Web sites, you must create a separate catalog for each Web site.
STATUS
This
behavior is by design.
MORE INFORMATION
The version of FrontPage 2002 Server Extensions that is included with Microsoft Windows Server 2003 Service Pack 1 (SP1) provides the Integrated Indexing Server Search functionality. This functionality is a more scalable implementation of the search functionality that is included in the original version of Windows Server 2003.
For more information about the search functionality in FrontPage, visit the following Microsoft Web site:
APPLIES TO
- Microsoft FrontPage 2002 Server Extensions, when used with:
- Microsoft Windows Server 2003 Service Pack 1
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please