[FrontPage Search Component] Displaying instead of actual search

[Thomas A. Rowe]

and see:
http://technet2.microsoft.com/WindowsServer/en/Library/96ae9e70-660a-4a1e-833a-bece404852051033.mspx

bottom of page

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

Jim,

Based on:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservext02/fpse2002win.asp

There are no updated extensions for Windows 2003.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

Hmm. I looked under Control Panel, Add/Remove Windows Components, and didn't
see FPSE sitting there two levels deep, so I downloaded and installed them
from http://msdn.microsoft.com/library/en-us/dnservext02/fpse2002win.asp.
That plus a security release put the server at FPSE 5.0.2.4803.

If that was the wrong thing to do, OK, but that's what I did. As to whether
it made any difference in the Web Search bot working/not working, I haven't a
clue.

There are no updated versions of the FP2002 extensions for Windows 2003 Server, only those
available
on the Windows 2003 CD.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

Well then, as a wild shot, you might unextend the FPSE from each virtual
server, remove it under Cotnrol Panel programs, download the latest version
and security fix from
http://msdn.microsoft.com/library/en-us/dnservext02/fpse2002win.asp, install
them, and then reextend your virtual server(s).

Even so, however, that would usually be a fix for No Documents Found rather
than [FrontPage Search Component].

[FrontPage Search Component] usually means that the FPSE aren't finding or
processing the search bot at all.

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
o--> Microsoft Visual Web Developer 2005 Express Edition: Build a Web Site
Now!
o--> Microsoft Office FrontPage 2003 Inside Out
o--> Microsoft Windows SharePoint Services Inside Out
o--> Faster Smarter Beginning Programming


:

You could be right about the order.
I do not recall the name of the single catalogue for the web, but the
installation of SP1 was over an existing, working Win2003 install.
Existing catalogues for three web sites were maintained by Index
Service, but the WWW tracking entry in the properties was set to
"None" for all these.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support: http://www.frontpagemvps.com/


And yet, with SP1 installed, installing FPSE and extending a virtual
server
created a new catalog called FPSE_Search. The existing System and
Web
catalogs are still there, too. So that's three catalogs under SP1,
not just
one.

Perhaps its the *order* of installing SP1 and/or FPSE that matters.

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
o--> Microsoft Visual Web Developer 2005 Express Edition: Build a
Web Site
Now!
o--> Microsoft Office FrontPage 2003 Inside Out
o--> Microsoft Windows SharePoint Services Inside Out
o--> Faster Smarter Beginning Programming


:

The FP search failed for me after installing SP1 on Windows 2003.
SP1
introduced a single catalogue for all web sites on the computer,
and
the FP search reacted by showing the [FrontPage Search Component]
error. Uninstalling SP1 and creating separate catalogues for each
site cured this.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support: http://www.frontpagemvps.com/


Well, I'm close to running out of ideas.

I did some additional reasearch on this, and some people seem to
believe
that the FrontPage Web Search component just doesn't work on
Windows
Sever
2003. However, it does work on that operating system for me.

FWIW, I'm using the lastest server extensions and security
update
from

http://msdn.microsoft.com/library/en-us/dnservext02/fpse2002win.asp

Extending a virtual server with these extensions created the
necessary
Indexing Service catalog automatically, but I still had to
right-click the
catalog in the Indexing Service MMC, choose Properties, and make
the
following configuration changes:

o On the Tracking tab, set WWW Server to the MMC name of the
Web
Server.
o On the Generation tab, clear Inherit Settings Fron Service
and
select
Index Files With Unknown Extensions and Generate Abstracts.

Lack of these settings, however, *didn't* cause [FrontPage
Search
Component]
to appear. Instead, the search form appeared as expected but all
searches
returned No Documents Found.

Under Web Service Extensions I have:

All Unknown CGI Extensions - Prohibited
All Unknown ISAPI Extensions - Prohibited
Active Server Pages - Allowed
ASP.NET v1.1.4322 - Allowed
FrontPage Server Extensions - Allowed
FrontPage Server Extensions 2002 - Allowed
Internet Data Connector - Prohibited
Server Side Includes - Allowed
WebDAV - Prohibited
Windows SharePoint Services - Allowed (Note: you probably won't
have
this one)

There was one report of [FrontPage Search Component] being
resolved
by
creating a new virtual server, extending it, and publishing the
site
onto it.
I suppose that bypassed some configuration error that'd crept
into
the
original virtual server but we'll never know what that was.

If you create a new page that contains nothing but the Search
form,
does
that fail too?

You *are* browsing the page with an http:// URL, right?

And if you open the site directly in FrontPage, using an http://
URL,
choosing Tools, Server, Administration Home, a FrontPage Server
Extensions
2002 Site Administration Web page opens in the browser, right?

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
o--> Microsoft Visual Web Developer 2005 Express Edition: Build
a
Web Site
Now!
o--> Microsoft Office FrontPage 2003 Inside Out
o--> Microsoft Windows SharePoint Services Inside Out
o--> Faster Smarter Beginning Programming


:

I've tried all of the things you've suggested including
restarting
the server
with no luck.

:

This is down to grasping at straws but use FrontPage to once
again open the
page directly on the server, then make a minor change such
as
adding and
deleting a space somewhere, then save it.

If the problem persists, try clicking Ctrl+Refresh in the
browser.

If the problem *still* persists, try rebooting the server.

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
o--> Microsoft Visual Web Developer 2005 Express Edition:
Build
a Web Site
Now!
o--> Microsoft Office FrontPage 2003 Inside Out
o--> Microsoft Windows SharePoint Services Inside Out
o--> Faster Smarter Beginning Programming


:

Jim

I found the area you were talking about and it was
prohibited
so I allowed
it. I then restarted the services for that site, but I'm
still having no
luck.

:

Jim

I don't see Web Services Extensions anywhere...

:

Hmmm... Stubborn bugger...

On the server, in IIS Manager, open the entry for your
Web
server, select
Web Service Extensions, and make sure Internet Data
Connector (at the right)
is set to "Allowed".

Jim Buyens
Microsoft MVP
http://www.interlacken.com
Author of:
o--> Microsoft Visual Web Developer 2005 Express
Edition:
Build a Web Site
Now!
o--> Microsoft Office FrontPage 2003 Inside Out
o--> Microsoft Windows SharePoint Services Inside Out
o--> Faster Smarter Beginning Programming




:

Search in IIS Manager is returning correct results
from
your site, right? Yes

The FrontPage Server Extensions are installed on the
problem server, right?
Yes

And the problem page's file name's extension is
..htm?
Yes

I'm also including the URL if you would ilke to take
a
look.


http://www.owatonna.k12.mn.us/OPS Header Page Copy.htm

Thanks





:

Well, all that looks correct. Indexing Service is
installed and running, and
there's no NoIndexServer=1 registry entry getting
in
the way.

Search in IIS Manager is returning correct results
from your site, right?