Re: Window Server 2003, SE adding FPSE
From: Lori (Lori_at_discussions.microsoft.com)
Date: 06/11/04
- Previous message: OhPearl: "Re: Window Server 2003, SE adding FPSE"
- In reply to: Hollis D. Paul: "Re: Window Server 2003, SE adding FPSE"
- Next in thread: Ronx: "Re: Window Server 2003, SE adding FPSE"
- Reply: Ronx: "Re: Window Server 2003, SE adding FPSE"
- Reply: Hollis D. Paul: "Re: Window Server 2003, SE adding FPSE"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 11 Jun 2004 14:54:01 -0700
"Hollis D. Paul" wrote:
> In article <90A53E43-3EED-49D2-94E2-52E9A85BDBBB@microsoft.com>, =?Utf-8?B?TG9yaQ==?= wrote:
> > I have downloaded FPSE 2002 to the server. I have gone on the server remotely and gone to tools to recalculate the hyperlinks, however I still get an error message. "Cannot run front page server extension on this page". What do I do now? Do I need download or change something else?
> >
> First, configure your web site. Then consider the stuff below:
>
> With Win2K3 and IIS6, in addition to installing and configuring the
> sites, and giving them their own application pool, you have to look in
> that third folder under your IIS server (in the IIS Manager console).
>
> Double click that folder and look at the list of extensions that are
> allowed in the left hand pane. From your description, I would guess
> that FPSE, FPSE2K2 are there and allowed, but that the Internet Service
> is not. You have to install this as a component of IIS, and it is not
> installed by default.
>
> http://www.experts-exchange.com/Applications/MS_Office/FrontPage/Q_2077
> 8551.html
>
> "By default, Windows 2003 Server does not install the indexing server.
> You should actually see an option in the IIS console to "allow" or
> "prohibit" the indexing service under the Web Service Extension
> section.
>
> The solution:
> 1) Go to "add/remove components" - "Windows Components" and uncheck
> the indexing service so it can be uninstalled.
> 2) Reboot the system
> 3) Go back to "add/remove components" and reinstall the indexing
> service.
> 4) In the IIS console, under "Web Service Extension", "allow" the
> indexing service.
> 5) Recalculate the website
>
> The search should function properly!"
>
>
> The link to this info in a page on my site:
> http://www.outlookbythesound.com/SBS2003/FrontPage_search_component.htm
>
>
> Hollis D. Paul [MVP - Outlook]
> Hollis@outhousebythesound.com
> 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
>
>
Hello,
Thanks for the help so far, but I need some clarifications.
When I go to the IIS Manager I do see Applications Pools and it is the default application pool. Do I need to set up an Application Pool for the web itself? Do I also need to set up an Application Pool for the specific page that houses the form?
Also when I went to the IIS Manager, I do not see Indexing Service or Server listed under the Web Service Extension. So I couldn't Allow it or Prohibit it. Does it have I different name or do I need to download this as well?
Thanks again for your help
- Previous message: OhPearl: "Re: Window Server 2003, SE adding FPSE"
- In reply to: Hollis D. Paul: "Re: Window Server 2003, SE adding FPSE"
- Next in thread: Ronx: "Re: Window Server 2003, SE adding FPSE"
- Reply: Ronx: "Re: Window Server 2003, SE adding FPSE"
- Reply: Hollis D. Paul: "Re: Window Server 2003, SE adding FPSE"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|