FrontPage Server Extensions for Windows - FPSE 2002 search problem

This is Interesting: Free IT Magazines  
Home > Archive > FrontPage Server Extensions for Windows > May 2004 > FPSE 2002 search problem





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author FPSE 2002 search problem
Antti

2004-05-24, 7:35 am

Hello,

I have problems with FPSE 2002 search component. Despite my best efforts,
the WAIS search function doesn't work if used with IIS 6 and content on a
UNC-share. Everything else works fine (like publishing, forum, themes, admin
pages etc.) but the search component appears on a page as "[FrontPage Search
Component]". According to STS admin guide WAIS should be enabled in the
downloadable version of FPSE 2002 [1]

I have configured my file and web servers as described in "Connecting Web
Sites to UNC Network Shares" [2] and "Authenticating Users Separately For
Each Virtual Server" [3]. I also have enabled FPSE from IIS admin console.

I will really appreciate any help to get around this problem.

[1]
http://www.microsoft.com/resources/...doc/owsi06.mspx

[2]
http://www.microsoft.com/resources/...doc/owsj04.mspx

[3]
http://www.microsoft.com/resources/...doc/owsj03.mspx

--
Antti


Hollis D. Paul

2004-05-24, 4:37 pm

In article <evoLnoWQEHA.3596@tk2msftngp13.phx.gbl>, Antti wrote:
> Despite my best efforts,
> the WAIS search function doesn't work if used with IIS 6
>

IIS 6 does not support WAIS.

Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Mukilteo, WA USA

Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
http://search.support.microsoft.com...D=TECH&LN=EN-US

Mukilteo, WA USA


Antti

2004-05-25, 7:37 am

"Hollis D. Paul" <Hollis@outhousebythesound.com> wrote in message
news:VA.00001a2d.00078530@obts-outlookdev.outlookbythesound.mukwoods...
> IIS 6 does not support WAIS.


Thank you for your answer. I'm afraid, however, that you're wrong.
The following page very clearly states that it's supported in
WS2003 with the downloadable version of FPSE 2002:

http://www.microsoft.com/resources/...doc/owsi06.mspx

The actual functionality of it is, of course, a complete different
story! (which makes me wonder if this is just another promiseware
from MS)

The search function is crucial. We can not migrate from IIS 5 to
IIS 6 until it works with UNC content.

--
Antti

Ronx

2004-05-25, 7:37 am

My interpretation of that article is that, if you install Win2003 SP1, the
WAIS search will not function, no matter which version of FP extensions are
used.
<quote>
Note: If you install Office XP SP3 or Windows Server 2003 SP1, Integrated
Indexing Server Search replaces WAIS.
</quote>
--
Ron
Reply only to group - emails will be deleted unread.

"Antti" <avah@community.nospam> wrote in message
news:O%232RtGjQEHA.132@TK2MSFTNGP09.phx.gbl...
> "Hollis D. Paul" <Hollis@outhousebythesound.com> wrote in message
> news:VA.00001a2d.00078530@obts-outlookdev.outlookbythesound.mukwoods...
>
> Thank you for your answer. I'm afraid, however, that you're wrong.
> The following page very clearly states that it's supported in
> WS2003 with the downloadable version of FPSE 2002:
>
>

http://www.microsoft.com/resources/...doc/owsi06.mspx
>
> The actual functionality of it is, of course, a complete different
> story! (which makes me wonder if this is just another promiseware
> from MS)
>
> The search function is crucial. We can not migrate from IIS 5 to
> IIS 6 until it works with UNC content.
>
> --
> Antti
>



Antti

2004-05-25, 7:37 am

"Ronx" <ronx917@hotmail.com> wrote in message
news:OHAXOUjQEHA.2248@TK2MSFTNGP12.phx.gbl...
> My interpretation of that article is that, if you install
> Win2003 SP1, the WAIS search will not function, no matter
> which version of FP extensions are used.


WS2003 SP1 is not a possible solution due to the obvious lack of
its existence. Office XP SP3 is not a possible solution due to
licensing issue (available licensing models are not applicable for
an ISP use).

It doesn't have to be precisely WAIS. I can live with whatever
search function as long as it works with IIS6, FPSE2002 and UNC
located content.

--
Antti

WebGeeks

2004-05-30, 10:46 am

So, what causes FrontPage to basically not see the Index
server, even though it is there and IIS was installed
after the Index server and the web catalog points to your
site, which works using the index server search in the MMC
on Win2K3/IIS6?

FrontPage properties for the search page reports "...
contains an Unknown FrontPage component Search" as an
error and if you view the page you get the "[FrontPage
Search Component".

I just can seem to get IIS 6 with the FPSE to see the
Index Server. In the Web Service Extensions, I have ensure
Index Server is enabled

Cheers,

John
Tom Pepper Willett

2004-05-30, 10:46 am

Have you tried posting in the Index Server newsgroup?
--
========================================
=============
Tom Pepper Willett [Microsoft MVP - FrontPage]
----------------------------------------------------------------------------
-------------------
Microsoft FrontPage:
http://www.microsoft.com/office/fro...fo/default.mspx
http://msdn.microsoft.com/office/un...ding/frontpage/
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
========================================
=============
"WebGeeks" <anonymous@discussions.microsoft.com> wrote in message
news:1327f01c44384$e100b300$a501280a@phx
.gbl...
| So, what causes FrontPage to basically not see the Index
| server, even though it is there and IIS was installed
| after the Index server and the web catalog points to your
| site, which works using the index server search in the MMC
| on Win2K3/IIS6?
|
| FrontPage properties for the search page reports "...
| contains an Unknown FrontPage component Search" as an
| error and if you view the page you get the "[FrontPage
| Search Component".
|
| I just can seem to get IIS 6 with the FPSE to see the
| Index Server. In the Web Service Extensions, I have ensure
| Index Server is enabled
|
| Cheers,
|
| John


Hollis D. Paul

2004-05-30, 10:46 am

In article <1327f01c44384$e100b300$a501280a@phx.gbl>, WebGeeks wrote:
> FrontPage properties for the search page reports "...
> contains an Unknown FrontPage component Search" as an
> error and if you view the page you get the "[FrontPage
> Search Component".
>

This message indicates that you have not configured your site to use
the FPSE. Since you can have several different sets of Server
Extensions installed to the server at a time, you have to 'configure"
each site to use just one of them. In IIS 6 this means "extend"-ing
the site with the SharePoint administration tools.

After that, you have to make sure that the Indexing Service is listed
in the Web Server Extensions and allowed. Open the IIS Manager on the
server box, and expand the third folder under the server icon--the Web
Server Extensions. If Indexing Services does not appear in the list in
the right-hand pane, then you have to uninstall IIS, and reinstall,
making sure that the Indexing Service is selected as a component of IIS
to install.

Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Mukilteo, WA USA

Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
http://search.support.microsoft.com...D=TECH&LN=EN-US

Mukilteo, WA USA


2004-05-30, 10:46 am

Thanks,

Will verify this ... but I am sure I did configure FPSE.

John

>-----Original Message-----
>In article <1327f01c44384$e100b300$a501280a@phx.gbl>,

WebGeeks wrote:
>This message indicates that you have not configured your

site to use
>the FPSE. Since you can have several different sets of

Server
>Extensions installed to the server at a time, you have

to 'configure"
>each site to use just one of them. In IIS 6 this

means "extend"-ing
>the site with the SharePoint administration tools.
>
>After that, you have to make sure that the Indexing

Service is listed
>in the Web Server Extensions and allowed. Open the IIS

Manager on the
>server box, and expand the third folder under the server

icon--the Web
>Server Extensions. If Indexing Services does not appear

in the list in
>the right-hand pane, then you have to uninstall IIS, and

reinstall,
>making sure that the Indexing Service is selected as a

component of IIS
>to install.
>
> Hollis D. Paul [MVP - Outlook]
> Hollis@outhousebythesound.com
> Mukilteo, WA USA
>
> Using Virtual Access 4.52 build 277 (32-bit), Windows

2000 build 2600
> http://search.support.microsoft.com/kb/c.asp?

FR=0&SD=TECH&LN=EN-US
>
> Mukilteo, WA USA
>
>
>.
>

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com