|
Home > Archive > FrontPage Server Extensions for Windows > June 2004 > Any fix yet for this? (was Re: FPSE and search function)
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 |
Any fix yet for this? (was Re: FPSE and search function)
|
|
| One's Too Many 2004-06-09, 5:01 pm |
| "Ronx" <ronx917@hotmail.com> wrote in message news:<uRTWPquSEHA.1472@TK2MSFTNGP09.phx.gbl>...
> How did the user "publish" the page to the server?
> In my experience, action="_derived/nortbots.htm" is the result of FTPing a
> disc-based web or page, and not using HTTP publish.
Synopsis: FPSE 2002 on a brand new W2K3 server with IIS 6, search
function always returning the "_derived/nortbots.htm" error page
claiming there's no FPSE installed on the server instead of doing the
search.
I'm encountering the very same exact problem here. We have a brand
new, freshly and cleanly installed Windows 2003 Standard Server,
Installed the Indexing service, installed IIS with the included
FPSE2002 right off the install cdrom, created a sample website in
FrontPage 2002 with search on the homepage, etc, published via normal
HTTP publishing (not FTP), and still no luck with the webpage search
function. Manually running a test query from /Manage Computer/Services
and Applications/Indexing Services/Web/Query the Catalog/ does indeed
return all kinds of good search results from within the sample
website.
| |
| Tom Pepper Willett 2004-06-09, 11:55 pm |
| This may have something to do with the new security settings in Win2003,
which includes URL scan activated and set to default settings. You may wish
to try the Windows 2003 newsgroup.
--
========================================
=============
Tom Pepper Willett [Microsoft MVP - FrontPage]
----------------------------------------------------------------------------
-------------------
Microsoft FrontPage:
http://www.microsoft.com/office/fro...fo/default.mspx
http://msdn.microsoft.com/office/un...ding/frontpage/
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
========================================
=============
"One's Too Many" <onez2many@yahoo.com> wrote in message
news:809fd590.0406090818.72af9b6e@posting.google.com...
| "Ronx" <ronx917@hotmail.com> wrote in message
news:<uRTWPquSEHA.1472@TK2MSFTNGP09.phx.gbl>...
| > How did the user "publish" the page to the server?
| > In my experience, action="_derived/nortbots.htm" is the result of FTPing
a
| > disc-based web or page, and not using HTTP publish.
|
| Synopsis: FPSE 2002 on a brand new W2K3 server with IIS 6, search
| function always returning the "_derived/nortbots.htm" error page
| claiming there's no FPSE installed on the server instead of doing the
| search.
|
|
| I'm encountering the very same exact problem here. We have a brand
| new, freshly and cleanly installed Windows 2003 Standard Server,
| Installed the Indexing service, installed IIS with the included
| FPSE2002 right off the install cdrom, created a sample website in
| FrontPage 2002 with search on the homepage, etc, published via normal
| HTTP publishing (not FTP), and still no luck with the webpage search
| function. Manually running a test query from /Manage Computer/Services
| and Applications/Indexing Services/Web/Query the Catalog/ does indeed
| return all kinds of good search results from within the sample
| website.
| |
| One's Too Many 2004-06-11, 5:43 pm |
| After trying every possible combination and permutation of
installation and configuration order of the various components and
settings involved, we were about to give up and go back to Apache on
Linux. We finally acquired a copy Frontpage 2003 client and a simple
re-import/re-publish of the test website, and all of a sudden
everything started working correctly. We tried puiblishing again with
the Frontpage 2002 client, and it broke again. Maybe there's some kind
of backwards incompatibility we're encountering with the FP client. I
guess we should have expected that you have to buy upgrade versions
for *all* the software components involved... this seems to be the
norm for MS these days.
|
|
|
|
|