FP 2002 search on W2k3

[Chris]

Hi, my first post here!

I've just migrated my FP webs from NT4 to w2k3 using the migration tool. All
seems to be working fine.

The only thing I can't seem to get to work is the FP search bot. Index
server is setup and working fine via the Indexing Service Query Form...

On the website that has FP 2002 extensions installed I get the following
error:

FrontPage Run-Time Component Page
You have submitted a form or followed a link to a page that requires a web
server and the FrontPage Server Extensions to function properly.

This form or other FrontPage component will work correctly if you publish
this web to a web server that has the FrontPage Server Extensions installed.


Any Ideas why this might happen, can't seem to find any relevant info
searching the web

 

[Harikumar H [MSFT]]

Hi,

Integration of FPSE with the Indexing service
FPSE is tightly integrated with Indexing Service. The functionalities that
indexing service provides is much better that the built-in search engine,
WAIS.
Configuration of Indexing service on an FPSE based web site
1. Install Indexing service through Add/Remove Windows Components.
2. Create a catalog and point this catalog to the FPSE enabled web site.
3. Follow this KB article to Configure indexing service on the FPSE site.
4. HOW TO: Create and Configure a Catalog for indexing.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308202
5. Test the catalog using 'Query the catalog' option.
Troubleshooting guidelines and the flow chart
1. Check if Index this site is enabled in the web site properties
2. Ensure that Indexing service is installed. If it is a windows 2003
server, also ensure that Indexing service is allowed in the Web server
extensions in the IIS manager.
3. Ensure that a catalog is created and it is mapped to the appropriate web
site.
4. Open the site in FrontPage and insert a page with a search form in it.
Right click on the Search form and go to properties, and it should contain
some additional properties which are related to index server.
5. In the code view, search for b-useindexserver. If the value is 0, then
it is not using the Indexing service and if it is 1, then it is using the
indexing service.
6. Ensure that 'noindexserver' is set to 0 in the registry. If it is 1, it
means that FPSE will not use indexing service, even it is present.
7. Ensure that .IDQ and .IDA file extensions are mapped to IDQ.DLL in the
Application configuration of the Web server properties as well as the
properties of the web site.

Hope this helps


regards

Hari
MSFT

This posting is provided "as is" with no warranties and confers no rights
--------------------
|
| Hi, my first post here!
|
| I've just migrated my FP webs from NT4 to w2k3 using the migration tool.
All
| seems to be working fine.
|
| The only thing I can't seem to get to work is the FP search bot. Index
| server is setup and working fine via the Indexing Service Query Form...
|
| On the website that has FP 2002 extensions installed I get the following
| error:
|
| FrontPage Run-Time Component Page
| You have submitted a form or followed a link to a page that requires a
web
| server and the FrontPage Server Extensions to function properly.
|
| This form or other FrontPage component will work correctly if you publish
| this web to a web server that has the FrontPage Server Extensions
installed.
|
|
| Any Ideas why this might happen, can't seem to find any relevant info
| searching the web
|
|

 

[Chris]

Thanks Hari

SOLVED!

Checked point 5. and replaced 0 with 1

Checked point 6. No registry entry

Checked point 7. file extensions where on web server but not in web site, corrected.

restarted IIS and search now works - Thanks again!