FrontPage Server Extensions for Windows - Nortbot error

This is Interesting: Free IT Magazines  
Home > Archive > FrontPage Server Extensions for Windows > April 2004 > Nortbot error





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 Nortbot error
Andrew

2004-03-11, 10:41 pm

I get a nortbot error and a 404 on the search page. windows SBS2003 server. check the KB. please guide me in the right direction
Harikumar H [MSFT]

2004-03-11, 10:41 pm

Hi Andew,

Windows 2003 server will not support WAIS search. Make sure that the
indexing is started in the web server.

In the existing site you can check whether the search web bot uses the
indexing service or not by using the following steps.

1. Insert the search web bot on a new page in the existing site. Do the
same in the newly created site. Compare the properties of the search web
bot.
2. In the code view search of b-useindexserver. If the value is 0, then
it is not using the Indexing service.


The resolution is - Create a new site and publish the old site to this new
one.

Hope this helps


regards

Hari
MSFT

This posting is provided "as is" with no warranties and confers no rights

Andrew

2004-03-11, 10:41 pm

Followed instructions. The following dispays on the page instead "[FrontPage Search Component] - the Indexing search in the MMC work perfectly for the site catalog, if only it woud do that on my site. where can i find more information?

Harikumar H [MSFT]

2004-03-18, 1:56 pm

Hi Andrew,

Create a new web site and catalog for that site. Then create some test
pages on that site and make sure that the search is working. If it is
working, publish the old site to the new one.

Check the following KB articles also.

http://support.microsoft.com/defaul...kb;EN-US;203796

http://support.microsoft.com/defaul...kb;en-us;205618

http://support.microsoft.com/defaul...kb;en-us;194262

http://support.microsoft.com/defaul...kb;en-us;188821


Hope this helps


regards

Hari
MSFT

This posting is provided "as is" with no warranties and confers no rights

Peter

2004-04-01, 11:40 am

Hey,

nothing of this all solves my problem.
still get to see [FrontPage Search Component].
My catalog is working fine, when I do "Query catalog" in the Indexing Service, I get results
I made a simple index.htm, only with this search web component on it.
I tried everything. nothing helps. :-(

help please...
Hollis Paul [MVP - Outlook]

2004-04-01, 4:50 pm

Show us the contents of your search page's .idq file. It is located in the
_vti_Scripts folder in the root of your web site. There is an index there
that should be pointing to your catalog. Have you set the catalog tracking
property to point to the virtual server of your site?

Hollis

"Peter" <anonymous@discussions.microsoft.com> wrote in message
news:D1EE606A-C420-4348-8CC4-36F77311ADAB@microsoft.com...
> Hey,
>
> nothing of this all solves my problem.
> still get to see [FrontPage Search Component].
> My catalog is working fine, when I do "Query catalog" in the Indexing

Service, I get results
> I made a simple index.htm, only with this search web component on it.
> I tried everything. nothing helps. :-(
>
> help please...



Peter

2004-04-11, 4:27 pm

there's no file in this directory.

now I copied my htm page onto my web server, the bot is working, but when I enter anything and click search I get an error that a page cannot be displayed (_derived/nortbots.htm)
this directory also does not exist.

Peter
Hollis Paul [MVP - Outlook]

2004-04-11, 4:27 pm

I think you have to publish the page with FrontPage or you will not get the
ancillary pages placed in the proper directories.

Hollis Paul

"Peter" <anonymous@discussions.microsoft.com> wrote in message
news:CBBC36B3-CBDB-4B23-A3A7-F32FDFA84C49@microsoft.com...
> there's no file in this directory.
>
> now I copied my htm page onto my web server, the bot is working, but when

I enter anything and click search I get an error that a page cannot be
displayed (_derived/nortbots.htm)
> this directory also does not exist.
>
> Peter



Peter

2004-04-21, 5:35 am

I did that, but then I get nothing but "[Frontpage Web Component]" on my screen.
that's just the strange thing
when I publish my whole site (just a few pages) from Frontpage, the /derived directory is not published to the server...

Peter
Hollis D. Paul

2004-04-21, 12:37 pm

In article <2F38DF58-519E-4698-99C0-0C03927DE082@microsoft.com>, =?Utf-8?B?UGV0ZXI=?= wrote:
> I did that, but then I get nothing but "[Frontpage Web Component]" on my screen.
> that's just the strange thing
> when I publish my whole site (just a few pages) from Frontpage, the /derived directory is not published to the server...
>
> Peter
>

Peter,

I know that it takes attention to detail, but could you in the future, enter something
that identifies you in the sending address. You jumped in on someone else's thread, and
is hard to tell where your messages start and his stops, though he did start to use
"harikumh" after his first message.

But, since you did jump in the middle, you didn't say what kind of a system you were
using and we can't really give you a reasonable answer till you tell us. You are not
getting those ancillary files, because your IIS virtual server is not using the Front
Page Server Extensions. That is why you see "[FrontPage Web Component]" on your screen.
Getting a Virtual Server to use the FPSE is a two step process: 1) install the FPSE to
the IIS server, and 2) configure any Virtual Server to use whatever Server Extensions
you want it to use. I would guess that you have not done step 2. How you fix that is
dependent on what version of the OS and SE you are running. Whatever those are, the
help files on the OS will tell you what to do. Search on "configure".

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

Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2195
http://search.support.microsoft.com...D=TECH&LN=EN-US

Mukilteo, WA USA


Peter

2004-04-22, 8:42 am

Hollis,

sorry for the first issue, had not seen that.
so, I will go into detail about what I'm doing here and on what machines.
I use FrontPage 2003 on my Windows XP pro sp1 computer. I publish to a windows server 2003 standard, running IIS and SE2002.
I created a site to where I publish (not the default site), configured the SE on it, also the virtual server as you mention.
Now, when I publish my page with the search bot, it is visible. so far so good.
I also created an Index on my website directory, using the Indexing Service, this also is ok, it works when using the "Query Catalog" page.
But when I enter something on my page, I always get the "page cannot be found" for the /derived/nortbot.htm... I tried several ways to publish, copy... whatever... nothing changes this "feature".
when I look into the code, the option in the bot ' b-useindexserver="0" ' should be ="1", I read about that, but it isn't. how do I fix that?
and what should I pay attention to on the Indexing Service? I also put my site in the WWW Server field on the Tracking tab of my index property page. something else to be changed?

Peter

Hollis D. Paul

2004-04-22, 11:43 am

In article <B02D87F1-64D0-4224-9635-FC7B97804700@microsoft.com>, =?Utf-8?B?UGV0ZXI=?= wrote:
> when I look into the code, the option in the bot ' b-useindexserver="0" ' should be ="1", I read about that, but it isn't. how do I fix that?
>

Hari Kumar had this to say in another thread:

"In the existing site you can check whether the search web bot uses the
indexing service or not by using the following steps.


1. In the code view of the search page, search for b-useindexserver. If
the value is 0, then it is not using the Indexing service.



If the web server is windows 2003, then Check whether the Indexing service
is Allowed in the Web service extensions
using IIS manager.

If it is set to enabled, then create a new catalog for this web site and
check whether the search is working.

Windows 2003 server will not support WAIS search."

And then, in this thread:

"Windows 2003 server will not support WAIS search. Make sure that the
indexing is started in the web server.

In the existing site you can check whether the search web bot uses the
indexing service or not by using the following steps.

1. Insert the search web bot on a new page in the existing site. Do the
same in the newly created site. Compare the properties of the search web
bot.
2. In the code view search of b-useindexserver. If the value is 0, then
it is not using the Indexing service."

That business about being allowed in the Web Service Extensions is an easy one to miss.
I know because I missed it also, in my installation of SBS2003. When you Open up the IIS
Manager, on your server's box, you will see just the local computer listed. Double click
the computer Icon and you get three folders, Application Pools, Web Sites, and Web Service
Extensions. Double click the Web Service Extensions folder and you get a list of web
service extensions that are installed, and some are not allowed. If Indexing Service is
not on that list and allowed, then you need to go back to Windows Components installation
and install it, even though you know it is already installed. You have to get it into
the windows metabase for IIS properly.

If it is there, try creating a new site, and seeing if you can get the form to work there,
as Hari suggests.

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

Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2195
http://search.support.microsoft.com...D=TECH&LN=EN-US

Mukilteo, WA USA


Peter

2004-04-23, 3:35 am

OK ! That's the trick !
finally, it works ;-)... thx a lot for your help...
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com