|
Home > Archive > FrontPage Server Extensions for Windows > April 2004 > Search component
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]
|
|
| §andro 2004-04-20, 12:40 pm |
| I am having search issues with FrontPage. Server is Windows 2003
with IIS 6. Index Server is installed and website files are cataloged (and
the catalog is pointing to the webserver), as I can search with Index Server
query without an issue. However, when publishing a search page, and then
opening it, I get 'the file cannot be found' error and it is pointing to the
/_vti_script/search.htm0.idq
file.
When I view the search page source, the b-useindexserver line indicates
a 1.
I have an htx file in the _derived folder, and an idq file in the
_vti_script folder.
The idq file has a line beginning with ciCatalog= which correctly points to
the catalog.
I had to manually add the .idq extension to the website home directory
Application Configuration.
Strangely I don't have Indexing service listed as a Web service extensions
where you can set them to Allowed/Prohibited in the IIS manager.
Should it be there? I seem to remember seeing it on a privious instalation
when the search component was working.
As you may have guessed I have been fighting with this problem for weeks and
I have scoured the newsgroups and tech articles for an answer but to no
avail.
If anyone has any ideas I would really appreciate them.
| |
| Hollis D. Paul 2004-04-20, 12:40 pm |
| In article <O52mLXtJEHA.1000@TK2MSFTNGP11.phx.gbl>, §andro wrote:
> However, when publishing a search page, and then
> opening it, I get 'the file cannot be found' error and it is pointing to the
> /_vti_script/search.htm0.idq
> file.
>
Please past the contents of that .idq file into your next message. Very
likely it does not contain a ciCatalog line. Consequently, it is attempting
to look for your stuff in the default catalog. The ciCatalog file should be
in the following format: ciCatalog="<path to catalog.wci folder>" . Without
the brackets.
Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Mukilteo, WA USA
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2195
http://search.support.microsoft.com...D=TECH&LN=EN-US
Mukilteo, WA USA
| |
| §andro 2004-04-21, 12:35 am |
| My idq file...
[Query]
citemplate=/_derived/search.htm0.htx
ciflags=DEEP
cicatalog=C:\Inetpub\Catalogs\Xparx
cidialect=1
ciscope=/
cirestriction=$contents %UserRestriction% & ! #vpath \iisadmin* &! #vpath
\iishelp* &! #vpath \iissamples* &! #vpath *\_vti* & ! #vpath *\_private\* &
! #vpath *\_derived\* & ! #vpath *\_themes\* & ! #vpath *\_overlay\* & !
#vpath *\_fpclass\* & ! #vpath *\_borders\* & ! #vpath *\toc.htm* & ! #vpath
*\tocproto.htm* & ! #vpath *.class & ! #vpath *.css
cisort=Rank[d]
cicolumns=DocTitle,filename,vpath
As suggested in a tech article I have created a Catalogs directory outside
the root of my sites and have set the indexing to place the catalog.wci
there.
If I try to extend the path right down to
cicatalog=C:\Inetpub\Catalogs\Xparx\cata
log.wci, when I do a 'recalculate'
on the site it seems to change the idq file back to the original path
cicatalog=C:\Inetpub\Catalogs\Xparx.
Thanks for your response.
"Hollis D. Paul" <Hollis@outhousebythesound.com> wrote in message
news:VA.000019b3.00784776@obts-outlookdev.outlookbythesound.com...
> In article <O52mLXtJEHA.1000@TK2MSFTNGP11.phx.gbl>, §andro wrote:
the[vbcol=seagreen]
> Please past the contents of that .idq file into your next message. Very
> likely it does not contain a ciCatalog line. Consequently, it is
attempting
> to look for your stuff in the default catalog. The ciCatalog file should
be
> in the following format: ciCatalog="<path to catalog.wci folder>" .
Without
> the brackets.
>
> Hollis D. Paul [MVP - Outlook]
> Hollis@outhousebythesound.com
> Mukilteo, WA USA
>
> Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2195
> http://search.support.microsoft.com...D=TECH&LN=EN-US
>
> Mukilteo, WA USA
>
>
| |
| Hollis D. Paul 2004-04-21, 12:37 pm |
| In article <eyvIjV1JEHA.808@tk2msftngp13.phx.gbl>, §andro wrote:
> [Query]
> citemplate=/_derived/search.htm0.htx
>
That doesn't look right to me. In my forms which are working, the
template is located in the _derived folder of the root of my site,
which is one folder down from root of the virtual server. So, if the
home directory of my virtual server is d:\NetTest, I publish the site
"TestNet" to d:\NetTest\TestNet, and the template is in
/TestNet/_derived/search.htm0.htx.
It would appear that you are publishing Xparx at
C:\inetpub\wwwroot\Xparx, so it should be looking for the template as
/Xparx/_derived/search.htm0.htx .
It appears that your idq file is pointing to the root of the Virtual
Server, which is reserved web application stuff. I would also advise
creating your own virtual server, independent of the default web site,
and giving it its own application pool. You will need to reserve an IP
address in the TCP/IP properties of your LAN NIC (if you are using a
fixed IP for the NIC) or in the DHCP properties of the DHCP server that
is provisioning your computers. In SBS2003, which sits on top of
Win2003, the help file is really very good about telling you how to set
all this up.
Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Mukilteo, WA USA
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2195
http://search.support.microsoft.com...D=TECH&LN=EN-US
Mukilteo, WA USA
|
|
|
|
|