Search Component Not Supported?

[Brian Mailman]

http://www.jewishfood-list.com (click on Recipes, scroll to the bottom
of the page)

After uploading some files, the Search function wasn't working. I
recalculated the hyperlinks, uninstalled and reinstalled the extensions,
and recalculated again (each time clearing the cache and closing down
Seamonkey before trying again).

I called my web host, Interland/Web.com and this is what they said:

"After re-calculating the hyperlinks on frontpage, the search bar is
still unfunctional.The reason why the FrontPage Search component still
not working after re-calculating hyperlinks and installing the frontpage
expensions is mentioned below:

Due to security issues, Microsoft no longer supports the FrontPage
Search component in their latest version of FrontPage Server
Extensions.Unfortunately, Web.com does not have any control over this
action by Microsoft."

Is this true?

B/

 

[Stefan B Rusynko]

Nonsense
- but partially correct

It is not the FP SE but Windows Server 2003 that does not support the FP WAIS default search
- the other option is for the FP SE to use the server Index Catalog for Search
(this is supported by all levels of the FP SE and by all servers including Windows 2003)
- but many hosts disable or will not enable Index Catalog because it has very high server overhead


--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


| http://www.jewishfood-list.com (click on Recipes, scroll to the bottom
| of the page)
|
| After uploading some files, the Search function wasn't working. I
| recalculated the hyperlinks, uninstalled and reinstalled the extensions,
| and recalculated again (each time clearing the cache and closing down
| Seamonkey before trying again).
|
| I called my web host, Interland/Web.com and this is what they said:
|
| "After re-calculating the hyperlinks on frontpage, the search bar is
| still unfunctional.The reason why the FrontPage Search component still
| not working after re-calculating hyperlinks and installing the frontpage
| expensions is mentioned below:
|
| Due to security issues, Microsoft no longer supports the FrontPage
| Search component in their latest version of FrontPage Server
| Extensions.Unfortunately, Web.com does not have any control over this
| action by Microsoft."
|
| Is this true?
|
| B/

 

[Brian Mailman]

Nonsense - but partially correct

It is not the FP SE but Windows Server 2003 that does not support the
FP WAIS default search - the other option is for the FP SE to use the
server Index Catalog for Search (this is supported by all levels of
the FP SE and by all servers including Windows 2003) - but many hosts
disable or will not enable Index Catalog because it has very high
server overhead

I believe there is a folder on the site called "catalog.wci." Would
that be the "index catalog" you're referring to?

B/

 

[Tom [Pepper] Willett]

By default, the Catalog.wci directory is created on your Web server during
the installation of Microsoft Index Server. You can usually find the catalog
directory under the InetPub directory on the drive where you installed IIS.

This doesn't necessarily mean they are using it. And, they would actually
have to enable it and configure it for your site.
--
===
Tom [Pepper] Willett
Microsoft MVP - FrontPage
"You're a daisy if you do!"
---
FrontPage Support:
http://www.frontpagemvps.com/
===
: Stefan B Rusynko wrote:
: > Nonsense - but partially correct
: >
: > It is not the FP SE but Windows Server 2003 that does not support the
: > FP WAIS default search - the other option is for the FP SE to use the
: > server Index Catalog for Search (this is supported by all levels of
: > the FP SE and by all servers including Windows 2003) - but many hosts
: > disable or will not enable Index Catalog because it has very high
: > server overhead
:
: I believe there is a folder on the site called "catalog.wci." Would
: that be the "index catalog" you're referring to?
:
: B/

 

[Brian Mailman]

By default, the Catalog.wci directory is created on your Web server
during the installation of Microsoft Index Server. You can usually
find the catalog directory under the InetPub directory on the drive
where you installed IIS.

This doesn't necessarily mean they are using it. And, they would
actually have to enable it and configure it for your site.

I worked up the food chain, rung by painful rung, and finally was able
to speak (actually speak!) with a member of the "executive response
team" who insisted that the index server had been disabled for two years
"because the engineers consider it a security risk." He said, "I can go
over to the engineers and ask them again, but I'm pretty sure it'll be a
waste of time because it'll be the same answer." I replied, "if you
don't mind, thanks, and if you could also ask them....'if it's been
disabled for 2 years, why was it working until yesterday when the server
dropped the connection and the extensions corrupted?" He responded, "I
can't verify that; it couldn't have been working it's been disabled." I
said, "then why didn't I complain 2 years ago? Are you saying that
neither I nor anyone else in my 'organization'* have used the search
function in the past 2 years?"

He called back a couple hours later and said he was "partially right"
that most of the Interland/Web.com servers had had index server disabled
but the one that I was using was "different" and hadn't been. He told
me he was running the catalogue as we spoke. He then called me back in
another couple hours and told me it was working. He also told me they
were reviewing the accounts on that server and might disable it there,
as well.

I thanked him profusely for going to bat for me and I knew how difficult
it must have been for him to buck the system.

So, for now, all's well..... thanks for the help.

*all volunteers who help format the files.

B/