Done all the checks and still no search working

[andrew_webby at hotmail]

Hi all

I'm having problems getting the FPSE2002 search component to work.

Here's what I've done so far on a clean box:

Installed Win2K3, ASP.Net, Indexing Service, FP2002 extensions, WWW
service, {asp, idc, remote admin, ssi, webdav, www service}

Used the IISMT tool to copy everything over from an old NT4 IIS4 box.
Then, fixed all the permissions properly so FP2002 is working
properly. Also, spotted that the IISMT tool broke all the associations
for .asp, .idq etc, so fixed them and verified them. They are all OK
now.

Created an index catalog and pointed it to c:\inetpub\catalog.wci. WWW
site root is at d:\inetpub\wwwroot so it's not 'in' the website. Set
the tracking of the index to the "default web site". Ensured the
"index this resource" entry is ticked for the web.

Added the d:\inetpub\wwwroot directory to the catalog and watched it
index everything. Test queried in the Indexing Service interface and
it returns entries as expected.

Generated an FP2002 search page using the search component. File made
the appropriate IDQ/HTX and according to flags it's
b-useindexserver="1" so I'm using IS and not WAIS for search.

Ran a search from my HTM page - and got

"No documents found. Please try again.
It may take several minutes for recently saved documents to appear in
the search"

I know the terms I searched for exist as I can query and return them
in the IS interface.

Following google advice for this situation, I have Tools, Recalculated
links, and also rebuilt the catalog several times. The effect is the
same.

For fun, I added parameter cicatalog=c:\inetpub\catalog.wci to the IDQ
and when the HTM searches it returns "There is no catalog". Putting
that back to "c:\inetpub" it's back to "No documents found..." so
that's good.

If I stop the IS service, it's "Service is not running". So I've
verified that I'm using the correct catalog and also that it's using
IS.

Deleted the catalog, created elsewhere, added wwwroot again, set to
track the default www site. Built the catalog and still the same
result.

So how come the FP component search isn't returning anything?

What am I missing here? I've been on this all day and most of
yesterday to no avail, so it's time to throw in the towel I'm
afraid...

Thanks in advance

AW

 

[andrew_webby at hotmail]

Hi Paul

Thanks for the suggestions. Sorry, that's something I forgot to
mention that I had already done. Under the extensions, everything is
allowed at the moment.

Rgds

AW

Deleted the catalog, created elsewhere, added wwwroot again, set to
track the default www site. Built the catalog and still the same
result.

So how come the FP component search isn't returning anything?

What am I missing here? I've been on this all day and most of
yesterday to no avail, so it's time to throw in the towel I'm
afraid...

FPSE 2002 can be difficult. But one more thing you need to check is
the Web Service Extensions. Since it is Win2K3 server, I presume that
you add the Application Role to the server, which is how you get IIS,
etc. Go to manage that server, which brings up the Appsrv Management
Console. Expand the IIS server so that you see three folders under
neath it, in the left pane. Double-click on the bottom folder(Web
Service Extensions) to show the list of Web Service Extensions that it
knows about. Make sure that Indexing Service is present and Allowed.
If it is not present, then you have to un-install the IIS component,
and reinstall it with the Indexing Service component selected for
installation.

Hollis D. Paul [MVP - Outlook]
[email protected]
Mukilteo, WA USA

Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
http://search.support.microsoft.com/kb/c.asp?FR=0&SD=TECH&LN=EN-US

Mukilteo, WA USA

 

[andrew_webby at hotmail]

Thanks again Paul

Already tried an iireset as well.

Sorry I haven't documented all this, but I've done so much that in
remembering it all I must have just missed a couple out.

Any other clues?

AW

Thanks for the suggestions. Sorry, that's something I forgot to
mention that I had already done. Under the extensions, everything is
allowed at the moment.

OK. Now you have to amend that first post, to add the Web Service
Extensions stuff, and post it to the
microsoft.public.Inetserver.Indexserver newsgroup. That's where the
real experts on indexing services hang out.

While you wait for an answer there, install FPSE 2000, and all its
patches, then configure your site to use the FPSE2K, and run the
command iireset from the server's console. Then see if the search form
works.

Hollis D. Paul [MVP - Outlook]
[email protected]
Mukilteo, WA USA

Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
http://search.support.microsoft.com/kb/c.asp?FR=0&SD=TECH&LN=EN-US

Mukilteo, WA USA

 

[Tom Pepper Willett]

Here they are, Hollis:
FrontPage 2002 Server Extensions Support Center:

http://support.microsoft.com/default.aspx?scid=fh;en-us;fp10se
----
1) Download FP 2002 Server Extensions:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservext/html/fpse02win.asp

2) Download FP2002 Server Extensions Updates (and install in this order):

http://download.microsoft.com/download/FrontPage2002/fpse1001/1/W98NT42KMeXP/EN-US/fpse1001.exe

http://download.microsoft.com/download/FrontPage2002/fpse1002/1/W98NT42KMeXP/EN-US/fpse1002.exe

3) Security Patch:

http://support.microsoft.com/default.aspx?scid=kb;en-us;813380
--
===
Tom "Pepper" Willett
Microsoft MVP - FrontPage
---
About FrontPage 2003:
http://office.microsoft.com/home/office.aspx?assetid=FX01085802
FrontPage 2003 Product Information:
http://www.microsoft.com/office/frontpage/prodinfo/default.mspx
Understanding FrontPage:
http://msdn.microsoft.com/office/understanding/frontpage/
FrontPage 2002 Server Extensions Support Center:
http://support.microsoft.com/default.aspx?scid=fh;en-us;fp10se
===
| In article <[email protected]>,
| Andrew_webby at hotmail wrote:
| > Any other clues?
| >
| Many of the FrontPage MVPs do not use FPSE2002 because it can't be made
| to work properly. However, Tom Pepper Willett, I believe, has a post
| that gives the URLs to all the patches and the order in which they must
| be installed. I did that and can get my searches to work, so, if you
| need anything else in FPSE2002, then perhaps you should ask for that
| recipe, and see if you can bet the evil brew to cook properly.
|
| Hollis D. Paul [MVP - Outlook]
| [email protected]
| Mukilteo, WA USA
|
| Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
| http://search.support.microsoft.com/kb/c.asp?FR=0&SD=TECH&LN=EN-US
|
| Mukilteo, WA USA
|
|

 

[andrew_webby at hotmail]

Still didn't work for me I'm afraid.

In desperation, I tried setting up all the components on another
server and it worked fine. I compared the settings against the one not
working and couldn't find anything significantly different.

So in super-desperation I rebuilt the broken machine and installed
again. Instead of using the IIS Migration tool this time, I simply
dragged all the files over and recreated the webs manually. This
worked.

Damnit !

Thanks for all the help guys, but I lay the blame for this one
squarely at the IISMT tool's feet...

AW