You guys were so kind in helping me resolve my database connection problem, my web page is up and running with connections to the database working just great. Thank you all.

Now I am just having a problem getting the Search to work. My web search requests return the following: "No documents matched the query", however, if I go to the Index Service MMC, and use that query, all my documents are returned.

I am running Windows Server 2003 Enterprise with IIS 6.0 on a 64 bit processor. I migrated this web site from the same OS but a 32 bit server. I enabled 32bit apps to be able to run with the IIS. I am not an experienced web master.

I am using query.idq and it looks like this:

[query]
CiCatalog=E:\ACEINDEX
CiScope=%Scope% (also tried with /)
CiColumns=filename,size,rank,characterization,vpath,write
CiTemplate=/cgi-bin/search/query.htx
CiRestriction-(%SearchString%) &! #vpath "\"
CiFlags=DEEP
CiMaxRecordsInResultset=777
CiSort=write[d]
CiLocal=En-US

my variables %Scope% and %SearchString% are being passed from this code in my homepage index.asp :

<form name="QForm" action="/cgi-bin/search/query.idq" METHOD=POST">
<input type="text" name="SearchString" size="30" maxlength="100" value="">
<input type="hidden" name="Scope" Value="/"> (also tried commenting out)
<input type="submit" value="Search">
</form>

I have verified that all the web server extensions for Front Page are installed and "allowed", although I did not use Front Page to develope anything, the previous web master used it. I know the catalogs are created as I can search them from the MMC.

If anyone has any suggestions, I would appreciate the help.

Dani AI

Generated

Good to see the site is back up, and ’s follow‑up makes this a useful troubleshooting note for anyone who hits the same “No documents matched the query” behavior: the Indexing Service can return results in MMC while the web front end returns none for a small set of avoidable reasons. Common culprits and focused checks:

  • Form/parameter transmission: malformed form attributes, stray characters, or using the wrong HTTP method can prevent the search CGI from receiving the values you expect. Temporarily invoke the search CGI with URL parameters from a browser (or switch the form to GET) to see whether the query reaches the engine.
  • 32‑bit vs 64‑bit mismatch on IIS6: the Indexing Service CGI/ISAPI you’re calling may be a 32‑bit component. On a 64‑bit Server 2003 + IIS6 migration you must ensure the IIS worker process mode supports 32‑bit legacy components.
  • Query restrictions and escaping: unescaped quotes, backslashes, or aggressive vpath/CiRestriction filters will unintentionally exclude results. Test with the simplest possible restriction (no filters) to confirm the engine returns hits.
  • Permissions and templates: confirm the IIS account can read the search template and any files the CGI needs, and check Event Viewer plus the IIS W3C logs for clues.

A short, safe ASP debug page to dump incoming form/query values is very handy (drop it somewhere safe and remove after debugging):

<%
Response.ContentType = "text/plain"
For Each k In Request.Form
  Response.Write k & " = " & Server.HTMLEncode(Request.Form(k)) & vbCrLf
Next
For Each k In Request.QueryString
  Response.Write "QS:" & k & " = " & Server.HTMLEncode(Request.QueryString(k)) & vbCrLf
Next
%>

If the MMC query works but the CGI doesn’t, focused tests above usually reveal whether the issue is a syntactic form problem, a 32/64 mismatch, an escaping problem, or a permissions/template problem. Since the original poster later reported the search working, one of these transient or configuration issues was likely the cause.

I don't know what I did, but my search is working today.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.