When enabling Frontpage extensions on a site in IIS6.0, it sets up the
_vti_bin to run under the MSSharePointAppPool but leaves the web site under
the DefaultAppPool where it happened to be created initially. This caused
problem on the web site, it stopped responding. After wasting couple hours,
I moved the web site to the MSSharePointAppPool where _vti_bin was setup,
it's responding okay now.

Why doesn't Microsoft move the web site also to the MSSharePointAppPool when
enabling Frontpage if that's a requirement?

Appreciate your comments? Is there something I am doing wrong?

Thanks,
Paul

[ Post a follow-up to this message ]

Hi,

The default web site should not need to be in the MSSharepointAppPool. That
pool is created to isolate various FPSE components, including the FPSE
administration website, from other websites you have running on your
machine.

If your main website stopped responding, then something is wrong. Can you
tell us what "not responding" means in your case? Where you getting errors?
What where they? Where you getting nothing? Where you getting something but
not what you expect?

Thanks

Cheers
Ken

"PaulT" <pthakur@apsc.com> wrote in message
news:OfRV6LihEHA.644@tk2msftngp13.phx.gbl...
> When enabling Frontpage extensions on a site in IIS6.0, it sets up the
> _vti_bin to run under the MSSharePointAppPool but leaves the web site
> under
> the DefaultAppPool where it happened to be created initially. This caused
> problem on the web site, it stopped responding. After wasting couple
> hours,
> I moved the web site to the MSSharePointAppPool where _vti_bin was setup,
> it's responding okay now.
>
> Why doesn't Microsoft move the web site also to the MSSharePointAppPool
> when
> enabling Frontpage if that's a requirement?
>
> Appreciate your comments? Is there something I am doing wrong?
>
> Thanks,
> Paul
>
>

[ Post a follow-up to this message ]

Well I just tried again, before and after enabling FrontPage on a site.
Before FrontPage install, the "postinfo.html" page would display okay in the
browser however after the install it doesn't until I change the application
pool to MSSharePointAppPool. I can't even open this web site in FrontPage
unless I move it to the MSSharePointAppPool, I get the following message:

"The server sent a response which FrontPage could not parse. If you are
trying to connect to a FrontPage server, check with the server's
administrator to make sure teh FrontPage server extensions are installed
properly."

"Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
news:%23p7OU%23khEHA.3348@TK2MSFTNGP12.phx.gbl...
> Hi,
>
> The default web site should not need to be in the MSSharepointAppPool.
That
> pool is created to isolate various FPSE components, including the FPSE
> administration website, from other websites you have running on your
> machine.
>
> If your main website stopped responding, then something is wrong. Can you
> tell us what "not responding" means in your case? Where you getting
errors?
> What where they? Where you getting nothing? Where you getting something
but
> not what you expect?
>
> Thanks
>
> Cheers
> Ken
>

[ Post a follow-up to this message ]

I found the problem. We had tightened security on the "Web Server
Extensions" folder under Program Files to just the System and Administrators
group under IIS 5.0 and it worked without any problem. I was using the same
tightened security under IIS 6.0 and it doesn't like that. When I added
local "users" group, it started working fine even if the web site is not
running under the MSSharePointAppPool.

What's the minimum permissions I can get by on the folder "web server
extensions" under program files, has anyone tried?


"PaulT" <pthakur@apsc.com> wrote in message
news:uuRUb46iEHA.2992@TK2MSFTNGP12.phx.gbl...
> Well I just tried again, before and after enabling FrontPage on a site.
> Before FrontPage install, the "postinfo.html" page would display okay in
the
> browser however after the install it doesn't until I change the
application
> pool to MSSharePointAppPool. I can't even open this web site in FrontPage
> unless I move it to the MSSharePointAppPool, I get the following message:
>
> "The server sent a response which FrontPage could not parse. If you are
> trying to connect to a FrontPage server, check with the server's
> administrator to make sure teh FrontPage server extensions are installed
> properly."
>
> "Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
> news:%23p7OU%23khEHA.3348@TK2MSFTNGP12.phx.gbl... 
> That 
you[vbcol=seagreen] 
> errors? 
> but 
>
>

[ Post a follow-up to this message ]

Windows 2003 comes locked down, so you really shouldn't have to adjust any p
ermissions or those
related to the FP extensions unless you want to open up access.

--
 ========================================
======
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

"PaulT" <pthakur@apsc.com> wrote in message news:%23OTqM37iEHA.3968@TK2MSFTNGP10.phx.gbl...[
vbcol=seagreen]
> I found the problem. We had tightened security on the "Web Server
> Extensions" folder under Program Files to just the System and Administrato
rs
> group under IIS 5.0 and it worked without any problem. I was using the sam
e
> tightened security under IIS 6.0 and it doesn't like that. When I added
> local "users" group, it started working fine even if the web site is not
> running under the MSSharePointAppPool.
>
> What's the minimum permissions I can get by on the folder "web server
> extensions" under program files, has anyone tried?
>
>
> "PaulT" <pthakur@apsc.com> wrote in message
> news:uuRUb46iEHA.2992@TK2MSFTNGP12.phx.gbl... 
> the 
> application 
> you 
>
>[/vbcol]

[ Post a follow-up to this message ]

Thanks for the feedback, I would leave the permissions alone now.

[ Post a follow-up to this message ]