Re: FP2002 Extensions not working in IIS

From: Thomas A. Rowe (tarowe_at_mvps.org)
Date: 11/05/04


Date: Fri, 5 Nov 2004 09:26:53 -0500

Under Index Server on the server, you must build a Index Catalog for the specific site.

-- 
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
http://www.ycoln-resources.com
FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
"Jesse Aviles" <monk@coqui.net> wrote in message news:J7Iid.1421$gC6.392@fe39.usenetserver.com...
> That worked. Thank you.  Now after I published the only component that didnt
> seem to work was the search form.  No matter what term I entered in the box,
> the form wsn't able to find anything.  I had published this web to a live
> website to test it and the form works but not so in my computer.  Any
> additional help you can offer.
>
>
> -- 
> Jesse Avilés
> monk@coqui.net
>
> Reply Only To The Newsgroup
>
>
> "Mark Fitzpatrick" <markfitz@fitzme.com> wrote in message 
> news:eut3cNBwEHA.1228@TK2MSFTNGP10.phx.gbl...
>> Actually, you can use the FP Server Extensions on a virtual directory, but you first must make it 
>> a web. You can do this through the IIS Management Console, right-click on the virtual server 
>> root, select New | Server Extensions Web and then give the web the exact same name as the virtual 
>> directory. You'll then probably have to use the permissions wizard to inherit settings then run 
>> check and fix to try to get the permissions correct. This process can get fussy sometimes about 
>> permissions.
>>
>>        Hope this helps,
>>        Mark Fitzpatrick
>>        Microsoft MVP - FrontPage
>>
>> "Jesse Aviles" <monk@coqui.net> wrote in message news:f7phd.1606$oh4.580@fe61.usenetserver.com...
>>>I have FPXP on a Windows XP Pro computer.  After installing IIS and
>>> receiving an error message saying that FP2002 extensions could not be
>>> installed because the system was not NTFS I decided to convert.  I did so
>>> and the extensions installed OK but I can't see the FP components on my web
>>> page.  I'm running the web and IIS on my machine. Am I doing something
>>> wrong?  My web is located on My Docs folder and referenced by IIS as a
>>> Virtual Directory.  I can see the web and navigate but not use the
>>> components.  Thanks for any help.
>>>
>>> -- 
>>> Jesse Avilés
>>> monk@coqui.net
>>>
>>> Reply Only To The Newsgroup
>>>
>>>
>>>
>>>
>>
>>
>
>
> 


Relevant Pages

  • Re: Nokia E50 ActiveSync problem with SBS2003 SP2
    ... Open IIS Manager ... Open properties of virtual directory OMA ... Click Start on your SBS server, ... And then please verify Authentication settings by the following steps. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange OMA issue
    ... enabled on the server, we do have two connections available, it seemed ... For Exchange-oma virtual directory and the virtual directory you created ... Open IIS Manager ... Exchange Server 2003 SP2 ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA Problems - continued
    ... For the steps to create a new virtual directory please follow ... web site in IIS. ... will find the new web sites in "web sites" folder. ... Install Imported Certificates on a Web Server in Windows ...
    (microsoft.public.windows.server.sbs)
  • Re: inhability to display http://localhost
    ... FrontPage web publishing is not a part of IIS but rather a special ... a clean Event Log does not mean the server is functioning correctly. ...
    (microsoft.public.inetserver.iis.security)
  • Re: simple step by step for enableing FPSE?
    ... Let go back...forget about IIS and extensions for the moment, let se about getting your web ... FrontPage Resources, WebCircle, MS KB Quick Links, etc. ... I think they are there because they show up in IIS) ... if authoring against a web server please contact the webmaster for this sites server. ...
    (microsoft.public.frontpage.extensions.windowsnt)