I migrated an nt4, IIS4 server to a 2003, IIS6 box. The
search "engine" has been broken ever since. I am unable
to get anything other than the contents of the query.idq
page. I use the nt4 search sample pages basically,
adjusted for my server. I'm using search.html that takes
the user input and feeds it to query.idq for the search
and the results come back formatted from query.htx. This
all worked flawlessly for years on the nt4 box, it ran
itself, never had any problems. I know I have index
server setup correctly. I have one catalog that points to
the root of the web, the catalog itself is 177MB now. I
would tune all of this between index server and the
query.idq page, but I can't get a basic setup to work. If
I submit a query through index serve's query form, it
works no problem and returns more than enough, too many
because the scope is so broad now. Everything else about
this site is fine and healthy. It's the only site that
needs search so I don't use it on other sites on this
box. However, the search is just as broken on the
development 2003 IIS6 box that mirrors this one. The
other sites on this box are fine, although they don't use
the search/index server stuff. IIS seems fine, no hitches
or anything. I know other people have had this same
problem, seemingly with no luck in finding a fix. Thanks
for any insights,
~Bob

RE: IIS 6.0 Search Problems by timcof

timcof
Tue Dec 16 05:53:52 CST 2003

Check permissions; ensure system has needed permissions on content to be indexed. Also, try here:
microsoft.public.inetserver.indexserver

Thank you. I hope this information is helpful.

Tim Coffey [MSFT]

This posting is provided ?AS IS? with no warranties, and confers no rights. You assume all risk for your use. © 2001 Microsoft Corporation. All rights reserved.
--------------------
| Content-Class: urn:content-classes:message
| From: "Bob" <anonymous@discussions.microsoft.com>
| Sender: "Bob" <anonymous@discussions.microsoft.com>
| Subject: IIS 6.0 Search Problems
| Date: Tue, 25 Nov 2003 10:59:42 -0800
| Lines: 26
| Message-ID: <0d2701c3b386$48e48030$a001280a@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| thread-index: AcOzhkjk8LYhtP/3S5ao8ebOo/8pfw==
| Newsgroups: microsoft.public.inetserver.iis
| Path: cpmsftngxa07.phx.gbl
| Xref: cpmsftngxa07.phx.gbl microsoft.public.inetserver.iis:284967
| NNTP-Posting-Host: tk2msftngxa08.phx.gbl 10.40.1.160
| X-Tomcat-NG: microsoft.public.inetserver.iis
|
| I migrated an nt4, IIS4 server to a 2003, IIS6 box. The
| search "engine" has been broken ever since. I am unable
| to get anything other than the contents of the query.idq
| page. I use the nt4 search sample pages basically,
| adjusted for my server. I'm using search.html that takes
| the user input and feeds it to query.idq for the search
| and the results come back formatted from query.htx. This
| all worked flawlessly for years on the nt4 box, it ran
| itself, never had any problems. I know I have index
| server setup correctly. I have one catalog that points to
| the root of the web, the catalog itself is 177MB now. I
| would tune all of this between index server and the
| query.idq page, but I can't get a basic setup to work. If
| I submit a query through index serve's query form, it
| works no problem and returns more than enough, too many
| because the scope is so broad now. Everything else about
| this site is fine and healthy. It's the only site that
| needs search so I don't use it on other sites on this
| box. However, the search is just as broken on the
| development 2003 IIS6 box that mirrors this one. The
| other sites on this box are fine, although they don't use
| the search/index server stuff. IIS seems fine, no hitches
| or anything. I know other people have had this same
| problem, seemingly with no luck in finding a fix. Thanks
| for any insights,
| ~Bob
|