IIS Index Server - Setting up Index Server With FrontPage2002 Extensions on IIS6 (Win2k3)

Author

Setting up Index Server With FrontPage2002 Extensions on IIS6 (Win2k3)

.._..

2007-02-02, 7:19 pm

Setting up Index Server With FrontPage2002 Extensions on IIS6 (Win2k3)

Trying to set up Index Server catalogs with individual FrontPage webs.

Several webs operating already with FP2002 Extensions.

Index Service is running, and I have set up individual catalogs for each web
and assigned them to track individual webs. Catalogs are stored in a
separate folder and I can see activity in each and they respond when I stop
and start the catalogs or when new pages are added.

Searching using the Indexing Service Query Form from the manage serve snap
in, reveals documents as I would expect, along with path and title and so
on. Each is compartamentalized. (The reason being I need both ASP and
FrontPage webs to be able to query these catalogs without crossover between
them.) So I believe the catalogs are good and set up the way I want.

Before I did all of the above, all of the webs using the FrontPage Search
component appeared to be searching with a shared catalog, so they would pick
up one another's data with a search and eithe resent broken links or leak
inforamtion between them. (They were using the default "FrontPagesearch"
catalog that had the entire IIS root in it, which I don't want.)

After setting up individual indexes, I removed the search components and
reinsterted them using FrontPage, recalculated hyperlinks and stoped and
started the indexing service (individual catalogs and the whole thing). The
only thing I didn't do was reboot the server.

Indexing Service is listed as "Allowed" in the Web Service Extensions in
IIS6

Using any search terms from the web page results in "Error from Search:
There is no Catalog"

In previous versions of FrontPage, there was the ability to assign the
search catalog index name or perhaps a check box to "use index server".

At this point, my problem appears to be how to get the FrontPage search
component to query the search catalog.

Here's the code as shown by the server:



I did manually change "useindexserver="0" to "1" with no apparent change.

One odd thing, using FP2003 on the sites on the old server (Win2k IIS5) I
have options "Entire website" "This web" and "Directory" in the Search
results tab. On the NEW server I have no such options.

One option I have is to switch it to ASP queries instead. However that
would take my 'move some sites to a new server quickly' project and turn it
into 'fuss about with a bunch of web sites re-coding them' project that I
would rather avoid. (Plus, my users are barely above the "right click or
left click" stage of computing and have no chance of maintainging ASP code.)

Any suggestions about how to use the FrontPage search component to hook up
to the individual web catalogs or get IIS6 with FPSE to act more like IIS5
with FPSE? I am either missing something in the web settings, IIS settings,
page settings... some simple dumb thing I need to check to get FPSE to be
aware of index service.

Comments appreciated.

Thanks!

.._..

2007-02-02, 7:19 pm

Followup:

Old server is using idq files:

_vti_script/search.htm0.idq

New server is using shtml.dll

_vti_bin/shtml.dll/search.htm

Still need to figure out how to get it to use the idq method rather than
shtml.dll....

".._.." <.._..@yourmom.mil> wrote in message
news:QgNwh.2096$G23.2094@newsreading01.news.tds.net...
> Setting up Index Server With FrontPage2002 Extensions on IIS6 (Win2k3)
>
> Trying to set up Index Server catalogs with individual FrontPage webs.
>
> Several webs operating already with FP2002 Extensions.
>
> Index Service is running, and I have set up individual catalogs for each
> web and assigned them to track individual webs. Catalogs are stored in a
> separate folder and I can see activity in each and they respond when I
> stop and start the catalogs or when new pages are added.
>
> Searching using the Indexing Service Query Form from the manage serve snap
> in, reveals documents as I would expect, along with path and title and so
> on. Each is compartamentalized. (The reason being I need both ASP and
> FrontPage webs to be able to query these catalogs without crossover
> between them.) So I believe the catalogs are good and set up the way I
> want.
>
> Before I did all of the above, all of the webs using the FrontPage Search
> component appeared to be searching with a shared catalog, so they would
> pick up one another's data with a search and eithe resent broken links or
> leak inforamtion between them. (They were using the default
> "FrontPagesearch" catalog that had the entire IIS root in it, which I
> don't want.)
>
> After setting up individual indexes, I removed the search components and
> reinsterted them using FrontPage, recalculated hyperlinks and stoped and
> started the indexing service (individual catalogs and the whole thing).
> The only thing I didn't do was reboot the server.
>
> Indexing Service is listed as "Allowed" in the Web Service Extensions in
> IIS6
>
> Using any search terms from the web page results in "Error from Search:
> There is no Catalog"
>
> In previous versions of FrontPage, there was the ability to assign the
> search catalog index name or perhaps a check box to "use index server".
>
> At this point, my problem appears to be how to get the FrontPage search
> component to query the search catalog.
>
> Here's the code as shown by the server:
>
> 
>
> I did manually change "useindexserver="0" to "1" with no apparent change.
>
> One odd thing, using FP2003 on the sites on the old server (Win2k IIS5) I
> have options "Entire website" "This web" and "Directory" in the Search
> results tab. On the NEW server I have no such options.
>
> One option I have is to switch it to ASP queries instead. However that
> would take my 'move some sites to a new server quickly' project and turn
> it into 'fuss about with a bunch of web sites re-coding them' project that
> I would rather avoid. (Plus, my users are barely above the "right click
> or left click" stage of computing and have no chance of maintainging ASP
> code.)
>
> Any suggestions about how to use the FrontPage search component to hook up
> to the individual web catalogs or get IIS6 with FPSE to act more like IIS5
> with FPSE? I am either missing something in the web settings, IIS
> settings, page settings... some simple dumb thing I need to check to get
> FPSE to be aware of index service.
>
> Comments appreciated.
>
> Thanks!
>

Hilary Cotter

2007-02-10, 1:16 pm

edit this key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Sh
ared Tools\Web Server
Extensions\Ports\Port /LM/W3SVC/1:

Set noindexserver (enter this string value if it is not there) and set it
to 0

This should enable Indeixng Services instead of the front page web engine
you have.

--
Hilary Cotter

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

".._.." <.._..@yourmom.mil> wrote in message
news:QgNwh.2096$G23.2094@newsreading01.news.tds.net...
> Setting up Index Server With FrontPage2002 Extensions on IIS6 (Win2k3)
>
> Trying to set up Index Server catalogs with individual FrontPage webs.
>
> Several webs operating already with FP2002 Extensions.
>
> Index Service is running, and I have set up individual catalogs for each
> web and assigned them to track individual webs. Catalogs are stored in a
> separate folder and I can see activity in each and they respond when I
> stop and start the catalogs or when new pages are added.
>
> Searching using the Indexing Service Query Form from the manage serve snap
> in, reveals documents as I would expect, along with path and title and so
> on. Each is compartamentalized. (The reason being I need both ASP and
> FrontPage webs to be able to query these catalogs without crossover
> between them.) So I believe the catalogs are good and set up the way I
> want.
>
> Before I did all of the above, all of the webs using the FrontPage Search
> component appeared to be searching with a shared catalog, so they would
> pick up one another's data with a search and eithe resent broken links or
> leak inforamtion between them. (They were using the default
> "FrontPagesearch" catalog that had the entire IIS root in it, which I
> don't want.)
>
> After setting up individual indexes, I removed the search components and
> reinsterted them using FrontPage, recalculated hyperlinks and stoped and
> started the indexing service (individual catalogs and the whole thing).
> The only thing I didn't do was reboot the server.
>
> Indexing Service is listed as "Allowed" in the Web Service Extensions in
> IIS6
>
> Using any search terms from the web page results in "Error from Search:
> There is no Catalog"
>
> In previous versions of FrontPage, there was the ability to assign the
> search catalog index name or perhaps a check box to "use index server".
>
> At this point, my problem appears to be how to get the FrontPage search
> component to query the search catalog.
>
> Here's the code as shown by the server:
>
> 
>
> I did manually change "useindexserver="0" to "1" with no apparent change.
>
> One odd thing, using FP2003 on the sites on the old server (Win2k IIS5) I
> have options "Entire website" "This web" and "Directory" in the Search
> results tab. On the NEW server I have no such options.
>
> One option I have is to switch it to ASP queries instead. However that
> would take my 'move some sites to a new server quickly' project and turn
> it into 'fuss about with a bunch of web sites re-coding them' project that
> I would rather avoid. (Plus, my users are barely above the "right click
> or left click" stage of computing and have no chance of maintainging ASP
> code.)
>
> Any suggestions about how to use the FrontPage search component to hook up
> to the individual web catalogs or get IIS6 with FPSE to act more like IIS5
> with FPSE? I am either missing something in the web settings, IIS
> settings, page settings... some simple dumb thing I need to check to get
> FPSE to be aware of index service.
>
> Comments appreciated.
>
> Thanks!
>