IIS 6 Search Engine

Index Server integration with IIS6 is not enabled by default. Go to
add/remove programs, add/remove Windows components, Application Server, and
enable it from there for IIS.

The reason this changed in IIS6 is for security reasons. Recall that
Nimda/CodeRed propagates itself through the pre-installed but never used
Index Server ISAPI -- so for IIS6, no such programs are enabled by default
unless specifically specified.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"bob" <bob.TakeThisOut@khemian.org> wrote in message
news:04ad01c3a4dd$e9c40050$a601280a@phx.gbl...
Hi,
I migrated our IIS4 server to a 2003 server/IIS6 and now
our search engine's broken. I have index server
configured correctly, the sites are checked to index
themselves, they seem to be indexing no problem, catalogs
are all there. I've tried the registry hack where you put
in the absolute path for index server to start from.
We're using search.html that returns query.idx, after
being formatted by query.htx, that kind of setup. I would
like to fix this or start from scratch with something
else, whatever works. Is it even supposed to work on
IIS6? Thanks,
Bob
 >> Stay informed about: IIS 6 Search Engine 

Hi David,
I looked in there before, thinking I missed something. I just checked again, I don't see anything. I loaded the application server console and BITS, but that doesn't seem to give me anything. I have the application server mmc open and I don't see anything in there. I also looked in the IIS admin mmc, nothing in there either. I'm not real clear on what I'm supposed to be enabling. When I do submit a search, I get: HTTP Error 404 - File or directory not found. I've given read and execute permissions to the everyone group and the anonymous user account, no change. Any ideas? Am I missing the API? thanks,
Bob

----- David Wang [Msft] wrote: -----

Index Server integration with IIS6 is not enabled by default. Go to
add/remove programs, add/remove Windows components, Application Server, and
enable it from there for IIS.

The reason this changed in IIS6 is for security reasons. Recall that
Nimda/CodeRed propagates itself through the pre-installed but never used
Index Server ISAPI -- so for IIS6, no such programs are enabled by default
unless specifically specified.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"bob" <bob.RemoveThis@khemian.org> wrote in message
news:04ad01c3a4dd$e9c40050$a601280a@phx.gbl...
Hi,
I migrated our IIS4 server to a 2003 server/IIS6 and now
our search engine's broken. I have index server
configured correctly, the sites are checked to index
themselves, they seem to be indexing no problem, catalogs
are all there. I've tried the registry hack where you put
in the absolute path for index server to start from.
We're using search.html that returns query.idx, after
being formatted by query.htx, that kind of setup. I would
like to fix this or start from scratch with something
else, whatever works. Is it even supposed to work on
IIS6? Thanks,
Bob
 >> Stay informed about: IIS 6 Search Engine 

You need to go to the Control Panel, Add/Remove Programs -- it has nothing
to do with the Server Console nor BITS. At this point, I think Index Server
is not installed/enabled on your server, which is the default behavior, so
you are seeing legitimate 404s. Thus, you need to install and enable Index
Server, and that's the proper resolution to this 404.

Changing permissions on users, etc is absolutely useless, so please change
all the permissions back to the original. It may be possible that this
change has already been harmful to the system... at which point I can only
suggest reinstalling the OS to get the settings back.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Bob" <anonymous.DeleteThis@discussions.microsoft.com> wrote in message
news:DB4DCA9D-52B0-4EDD-9015-A7BE686C1B26@microsoft.com...

Hi David,
I looked in there before, thinking I missed something. I just checked
again, I don't see anything. I loaded the application server console and
BITS, but that doesn't seem to give me anything. I have the application
server mmc open and I don't see anything in there. I also looked in the IIS
admin mmc, nothing in there either. I'm not real clear on what I'm supposed
to be enabling. When I do submit a search, I get: HTTP Error 404 - File
or directory not found. I've given read and execute permissions to the
everyone group and the anonymous user account, no change. Any ideas? Am I
missing the API? thanks,
Bob

----- David Wang [Msft] wrote: -----

Index Server integration with IIS6 is not enabled by default. Go to
add/remove programs, add/remove Windows components, Application Server,
and
enable it from there for IIS.

The reason this changed in IIS6 is for security reasons. Recall that
Nimda/CodeRed propagates itself through the pre-installed but never
used
Index Server ISAPI -- so for IIS6, no such programs are enabled by
default
unless specifically specified.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no
rights.
//
"bob" <bob.DeleteThis@khemian.org> wrote in message
news:04ad01c3a4dd$e9c40050$a601280a@phx.gbl...
Hi,
I migrated our IIS4 server to a 2003 server/IIS6 and now
our search engine's broken. I have index server
configured correctly, the sites are checked to index
themselves, they seem to be indexing no problem, catalogs
are all there. I've tried the registry hack where you put
in the absolute path for index server to start from.
We're using search.html that returns query.idx, after
being formatted by query.htx, that kind of setup. I would
like to fix this or start from scratch with something
else, whatever works. Is it even supposed to work on
IIS6? Thanks,
Bob
 >> Stay informed about: IIS 6 Search Engine 

There is nothing in Add/Remove programs|windows
components|etc...

We have an MS consultant around, he checked too, he didn't
find anything or know anything either. I added the
application server mmc and found nothing in there. There
is nothing to enable. I'm using the IIS 4 search pages,
they work now on our IIS 4 box. search.html -> query.idq -
 > query.htx -> query.html or something along those lines,
this gets me a 404 page cannot be found.

When I get the 404 error, the page in the url is:
<a style='text-decoration: underline;' href="http://inform/h1002/Search/query.idq?CiScope=%" target="_blank">http://inform/h1002/Search/query.idq?CiScope=%</a>
2F&CiMaxRecordsPerPage=10&TemplateName=query&CiSort=rank%
5Bd%5D&HTMLQueryForm=query.htm&CiRestriction=asdf

This is an intranet server and we're all behind the
firewall on the same 10.6.10.1 - 10.6.191.1 network.

I have index server configured correctly, it catalogs,
etc. I have the ciscope="" set correctly and all that
other stuff that is site specific in these couple of
files. Thanks for any ideas, suggestions, etc...

Bob

 >-----Original Message-----
 >Index Server integration with IIS6 is not enabled by
default. Go to
 >add/remove programs, add/remove Windows components,
Application Server, and
 >enable it from there for IIS.
 >
 >The reason this changed in IIS6 is for security reasons.
Recall that
 >Nimda/CodeRed propagates itself through the pre-installed
but never used
 >Index Server ISAPI -- so for IIS6, no such programs are
enabled by default
 >unless specifically specified.
 >
 >--
 >//David
 >IIS
 >This posting is provided "AS IS" with no warranties, and
confers no rights.
 >//
 >"bob" <bob.DeleteThis@khemian.org> wrote in message
 >news:04ad01c3a4dd$e9c40050$a601280a@phx.gbl...
 >Hi,
 >I migrated our IIS4 server to a 2003 server/IIS6 and now
 >our search engine's broken. I have index server
 >configured correctly, the sites are checked to index
 >themselves, they seem to be indexing no problem, catalogs
 >are all there. I've tried the registry hack where you put
 >in the absolute path for index server to start from.
 >We're using search.html that returns query.idx, after
 >being formatted by query.htx, that kind of setup. I would
 >like to fix this or start from scratch with something
 >else, whatever works. Is it even supposed to work on
 >IIS6? Thanks,
 >Bob
 >
 >
 >.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS 6 Search Engine 

The 404 error is most like due to ...
<a style='text-decoration: underline;' href="http://support.microsoft.com/default.aspx?scid=kb;en-us;315122&Product=iis60" target="_blank">http://support.microsoft.com/default.aspx?scid=kb;en-us;315122&Product=iis60</a>

--
Tom Kaminski IIS MVP
<a style='text-decoration: underline;' href="http://www.iistoolshed.com/" target="_blank">http://www.iistoolshed.com/</a> - tools, scripts, and utilities for running IIS
<a style='text-decoration: underline;' href="http://mvp.support.microsoft.com/" target="_blank">http://mvp.support.microsoft.com/</a>
<a style='text-decoration: underline;' href="http://www.microsoft.com/windowsserver2003/community/centers/iis/" target="_blank">http://www.microsoft.com/windowsserver2003/community/centers/iis/</a>

"bob" <bob.DeleteThis@khemian.org> wrote in message
news:276001c3a961$217a9770$a601280a@phx.gbl...
 > There is nothing in Add/Remove programs|windows
 > components|etc...
 >
 > We have an MS consultant around, he checked too, he didn't
 > find anything or know anything either. I added the
 > application server mmc and found nothing in there. There
 > is nothing to enable. I'm using the IIS 4 search pages,
 > they work now on our IIS 4 box. search.html -> query.idq -
  > > query.htx -> query.html or something along those lines,
 > this gets me a 404 page cannot be found.
 >
 > When I get the 404 error, the page in the url is:
<font color=purple> > <a style='text-decoration: underline;' href="http://inform/h1002/Search/query.idq?CiScope=%</font" target="_blank">http://inform/h1002/Search/query.idq?CiScope=%</font</a>>
 > 2F&CiMaxRecordsPerPage=10&TemplateName=query&CiSort=rank%
 > 5Bd%5D&HTMLQueryForm=query.htm&CiRestriction=asdf
 >
 > This is an intranet server and we're all behind the
 > firewall on the same 10.6.10.1 - 10.6.191.1 network.
 >
 > I have index server configured correctly, it catalogs,
 > etc. I have the ciscope="" set correctly and all that
 > other stuff that is site specific in these couple of
 > files. Thanks for any ideas, suggestions, etc...
 >
 > Bob
 >
  > >-----Original Message-----
  > >Index Server integration with IIS6 is not enabled by
 > default. Go to
  > >add/remove programs, add/remove Windows components,
 > Application Server, and
  > >enable it from there for IIS.
  > >
  > >The reason this changed in IIS6 is for security reasons.
 > Recall that
  > >Nimda/CodeRed propagates itself through the pre-installed
 > but never used
  > >Index Server ISAPI -- so for IIS6, no such programs are
 > enabled by default
  > >unless specifically specified.
  > >
  > >--
  > >//David
  > >IIS
  > >This posting is provided "AS IS" with no warranties, and
 > confers no rights.
  > >//
  > >"bob" <bob.DeleteThis@khemian.org> wrote in message
  > >news:04ad01c3a4dd$e9c40050$a601280a@phx.gbl...
  > >Hi,
  > >I migrated our IIS4 server to a 2003 server/IIS6 and now
  > >our search engine's broken. I have index server
  > >configured correctly, the sites are checked to index
  > >themselves, they seem to be indexing no problem, catalogs
  > >are all there. I've tried the registry hack where you put
  > >in the absolute path for index server to start from.
  > >We're using search.html that returns query.idx, after
  > >being formatted by query.htx, that kind of setup. I would
  > >like to fix this or start from scratch with something
  > >else, whatever works. Is it even supposed to work on
  > >IIS6? Thanks,
  > >Bob
  > >
  > >
  > >.
  > ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: IIS 6 Search Engine 

Here is the instruction how to enable the search engine usind idq and htx on IIS 6.0.

Make sure Index Server is running
Open IIS 6.0
->Click on the Web Server Extension
->Click on Add New Web Server Extention
->A pop up screen will come up. Asking the name of the extension - Type in the name, ex. IDQ or Search
->Click on the Add button, another pop up screen will come up asking for the location and file name. Click on browse and select this file c:\windows\system32\idq.dll
->Also you need to select the box set this extension to allow box.
->Lasting you need to setup the configue file extension .idq on the property of the website. Using the same file.

Good luck!!!
 >> Stay informed about: IIS 6 Search Engine