FrontPage Server Extensions for Windows - Using search form created by Frontpage on IIS 6.0 returns HTTP 405

This is Interesting: Free IT Magazines  
Home > Archive > FrontPage Server Extensions for Windows > March 2005 > Using search form created by Frontpage on IIS 6.0 returns HTTP 405





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Using search form created by Frontpage on IIS 6.0 returns HTTP 405
Bill Cunningham

2005-03-22, 8:46 pm

Problem: Using search form created by Frontpage on IIS 6.0 returns HTTP 405
or 404 error.

Configuration:
Windows 2003 server running IIS 6.0 with FrontPage extensions installed &
configured.
ASP pages allowed. ASP.NET allowed. FP 2002 allowed. Internet Data
Connection allowed.

Was getting HTTP 405 error prior to application configuration changes. Added
*.ida and *.idq point to c:\windows\system32\idq.dll, for verbs GET,HEAD,POST
which changed error to HTTP 404.

Search page IDQ file exists in /_vti_scripts/search.htm0.idq. Contents of
file below. IDQ calls catalog file "IntranetCatalog" located in
C:\Data\IntranetCatalog. Index service is running. IntranetCatalog points to
c:\data\intranet. IIS permissions are scripts only for /_vti_scripts/.
Vti_bin is set to script & executables. Iusr_servername account has read &
execute permissions.

What setting is wrong or missing that causes all searches to return HTTP 404?


SEARCH.HTM0.IDQ FILE>>>>
[Query]
citemplate=/_derived/search.htm0.htx
ciflags=DEEP
cicatalog=C:\Data\IntranetCatalog
cidialect=1
cimaxrecordsperpage=20
ciscope=/
cirestriction=$contents %UserRestriction% & ! #vpath \iisadmin* &! #vpath
\iishelp* &! #vpath \iissamples* &! #vpath *\_vti* & ! #vpath *\_private\* &
! #vpath *\_derived\* & ! #vpath *\_themes\* & ! #vpath *\_overlay\* & !
#vpath *\_fpclass\* & ! #vpath *\_borders\* & ! #vpath *\toc.htm* & ! #vpath
*\tocproto.htm* & ! #vpath *.class & ! #vpath *.css
cisort=Rank[d]
cimaxrecordsinresultset=500
cicolumns=DocTitle,filename,vpath,write,
size

IIS LOGS
2005-03-22 21:01:30 10.59.19.97 GET /search.htm - 80 - 10.59.19.97
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322) 200 0 0
2005-03-22 21:01:30 10.59.19.97 GET /_vti_bin/fpcount.exe/
Page=search.htm|Image=1 80 - 10.59.19.97
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322) 200 0 0
2005-03-22 21:01:36 10.59.19.97 POST /_vti_script/search.htm0.idq - 80 -
10.59.19.97
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322) 404 2
1260

Hollis D. Paul

2005-03-23, 2:47 am

In article <C6082FA8-9AA2-49EB-B5A7-7DDD6AAFA42C@microsoft.com>,
=?Utf-8?B?QmlsbCBDdW5uaW5naGFt?= wrote:
> cicatalog=C:\Data\IntranetCatalog
>

Did you use the Indexing Service Management Console to set the Catalog
to track your intranet site? I am specifically speaking about
C:\windows\system32\ciadv.msc. I keep a shortcut to it on my desktop.
You should have used that to create the catalog. But you also have to
set the tracking parameter of the catalog to the web site you are
trying to index.

Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Mukilteo, WA USA


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com