Not getting much on other forums so posting here since
this involves server extensions.  Site search does not
work not matter what I do.

Here are some links to my search page, I HAVE TRIED
SEVERAL VERSIONS and created some on the server itself so
in case I was not publishing all the files they would be
there.

We run our own server and other pages, like topten.htm,
that use extensions/share point services work find. All
my forms work fine too.

HTTP://WWW.FBCBRANDON.ORG/(page below)
a) searchonserver.htm (this one does not seem to
recognize the front page component)

b) searchcompoent.htm (looks ok on page, but when enter
text and start search - gives error that needs server
extensions which are definetly Installed)

c) site_search.htm (does not seem to recognize frontpage
component either and although when you do VIEWSOURCE in
the browser, it appears differently than before
published - it does not look that way when editing in
code

I am really puzzled. Also, I would like to mention this
is FrontPage 2003 on Windows 2003 server (our own server)
and I have reinstalled server extensions 2 times.

Any help would be appreciated greatly.
dkfbc

[ Post a follow-up to this message ]

Hi Ddk,

The search functionality in windows 2003 needs Indexing service.  Please
ensure that the Indexing service is installed and it is 'Allowed' in the
web server extensions.

If the site is migrated from a Windows 2000 box to 2003, then you need to
create a new site and then publish the old site again. This is because the
search functionality in Windows 2000 uses WAIS and Windows 2003 only
supports Indexing.

Hope this helps


regards

Hari
MSFT

This posting is provided "as is" with no warranties and confers no rights

[ Post a follow-up to this message ]

Indexing is installed and "allowed" per the directory in
IIS.  The site was not migrated.
If you have looked at the pages I specified, you will see
that it does not seem to even recognize the search
component, it appears on 2 of the pages as:
[FrontPage Search Component]

Any ideas?


>-----Original Message-----
>Hi Ddk,
>
>The search functionality in windows 2003 needs Indexing
service.  Please
>ensure that the Indexing service is installed and it
is 'Allowed' in the
>web server extensions.
>
>If the site is migrated from a Windows 2000 box to 2003,
then you need to
>create a new site and then publish the old site again.
This is because the
>search functionality in Windows 2000 uses WAIS and
Windows 2003 only
>supports Indexing.
>
>Hope this helps
>
>
>regards
>
>Hari
>MSFT
>
>This posting is provided "as is" with no warranties and
confers no rights
>
>.
>

[ Post a follow-up to this message ]

In article <2a8401c3fcac$97ab5b70$a001280a@phx.gbl>, Ddk wrote:
> I am really puzzled. Also, I would like to mention this
> is FrontPage 2003 on Windows 2003 server (our own server)
> and I have reinstalled server extensions 2 times.
>
You haven't used the magic word "configure".  You can install FPSE to
the server box, and uninstall it, and reinstall it as many times as you
want, but if you don't configure your site to use the FPSE, it will
always give you the error message that the FPSE are not installed.
Have you ever done that on this site?  Can you point to a page on this
site where a component that uses FPSE is actually working?

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

[ Post a follow-up to this message ]

Hi Ddk,

Create a new virtual server.  Open the site in Frontpage and insert a
search component.  Right click on the properties of the search component
and compare the same with the search component which is present in the site
which is not working.  If the search component uses Indexing service, you
can see the difference there.

If the search in the new site is working, then you can publish the site
which is not working to the newly created site.

Hope this helps


regards

Hari
MSFT

This posting is provided "as is" with no warranties and confers no rights

[ Post a follow-up to this message ]

Check indexing service is running in services
Go to add remove programs & install indexing service
Go to ISS Admin ,WebService extension allow indexing service
Check search

"ddk" <anonymous@discussions.microsoft.com> wrote in message
news:2a8401c3fcac$97ab5b70$a001280a@phx.gbl...
> Not getting much on other forums so posting here since
> this involves server extensions.  Site search does not
> work not matter what I do.
>
> Here are some links to my search page, I HAVE TRIED
> SEVERAL VERSIONS and created some on the server itself so
> in case I was not publishing all the files they would be
> there.
>
> We run our own server and other pages, like topten.htm,
> that use extensions/share point services work find. All
> my forms work fine too.
>
> HTTP://WWW.FBCBRANDON.ORG/(page below)
> a) searchonserver.htm (this one does not seem to
> recognize the front page component)
>
> b) searchcompoent.htm (looks ok on page, but when enter
> text and start search - gives error that needs server
> extensions which are definetly Installed)
>
> c) site_search.htm (does not seem to recognize frontpage
> component either and although when you do VIEWSOURCE in
> the browser, it appears differently than before
> published - it does not look that way when editing in
> code
>
> I am really puzzled. Also, I would like to mention this
> is FrontPage 2003 on Windows 2003 server (our own server)
> and I have reinstalled server extensions 2 times.
>
> Any help would be appreciated greatly.
> dkfbc
>

[ Post a follow-up to this message ]

Please check out this link, it answered my same problem.

http://www.chat11.com/ Getting_Text...
al_Search_Box 


quote:
Originally posted by Ranjit Rai 
Check indexing service is running in services
Go to add remove programs & install indexing service
Go to ISS Admin ,WebService extension allow indexing service
Check search

"ddk" <anonymous@discussions.microsoft.com> wrote in message
news:2a8401c3fcac$97ab5b70$a001280a@phx.gbl...
> Not getting much on other forums so posting here since
> this involves server extensions.  Site search does not
> work not matter what I do.
>
> Here are some links to my search page, I HAVE TRIED
> SEVERAL VERSIONS and created some on the server itself so
> in case I was not publishing all the files they would be
> there.
>
> We run our own server and other pages, like topten.htm,
> that use extensions/share point services work find. All
> my forms work fine too.
>
> HTTP://WWW.FBCBRANDON.ORG/(page below)
> a) searchonserver.htm (this one does not seem to
> recognize the front page component)
>
> b) searchcompoent.htm (looks ok on page, but when enter
> text and start search - gives error that needs server
> extensions which are definetly Installed)
>
> c) site_search.htm (does not seem to recognize frontpage
> component either and although when you do VIEWSOURCE in
> the browser, it appears differently than before
> published - it does not look that way when editing in
> code
>
> I am really puzzled. Also, I would like to mention this
> is FrontPage 2003 on Windows 2003 server (our own server)
> and I have reinstalled server extensions 2 times.
>
> Any help would be appreciated greatly.
> dkfbc
> 

[ Post a follow-up to this message ]

OK, this link did not work when posted so will try to post the actual text o
f the message:

searched and searched for a solution. Having gleaned bits and pieces from va
rious sources, here's what I discovered and how I fixed it: 

I realized that the indexing service wasn't listed in IIS under Web Service 
Extensions. And despite the fact that the service was running and I'd config
ured catalogs, I found that when I went to Add/Remove?Create Programs ยป Win
dows Components, Indexing Service wasn't checked. So I checked it, it instal
led (again?), I reset IIS, found the service was now appropriately listed in
 the Web Service Extensions, I "allowed" it, recalculated the web, and viola
! 

Your mileage may vary, but I hope this information proves helpful. Please po
st your results so that others may benefit. Cheers! . 




----------------------------------------------------------------------------
----
After doing the above, the next error you might get might be something like 
   yourdomain/_vti_script/search.html0.idq  gets a "Page Cannot Be Found"

Go to Web Service Extensions, and enable "Indexing Service" 

The next problem you'll see is "No Documents Found. Please Try Again." 

Go into Computer Management, Add a new Catalog for each virtual website. 

After adding the catalog for a virtual website, then add it's root directory
 

After adding the root directory, stop and then start index server. 



quote:
Originally posted by thule 
Please check out this link, it answered my same problem.

http://www.chat11.com/ Getting_Text...rch_Bo
x 

[ Post a follow-up to this message ]