Error 403 access to subweb denied IIS

[Sandra]

I created a subweb under the root web in IIS. I access
it and publish to it just fine.
I created another subweb the same way, with "permissions
same as parent web". When I try to access it I
get "error 403 forbidden access" or something similar.
When I try to publish to this subweb, it does not show up
as an option when I select "browse". I deleted it and
tried another- same thing.

 

[Thomas A. Rowe]

How are you creating the subweb, from within IIS or FP.

If IIS open the rootweb in FP, create a folder, then right click the folder and select to convert to
web.

If you have direct access to the server, then you may need to stop and start IIS, before you can
access or publish to the subweb directly. Also if this is local, then you should always create your
webs under IIS.


--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

 

[Joe (Sten-tel)]

Actually I used to have this problem until I figured out this about FP Extensions 2002 and FP the Office Produc

1. Use Frontpage to set up the Virtual Directory/Subweb (it does it the cleanest without you having to access the Main Frontpage Admin Web Site

2. When creating sites from Internet Service manager, CLOSE IIS after creating a virtual web. Just to be safe. (The IIS admin interface creates a similar to the FP Web Admin interface error). In order to fix the Web interface problem, you only need to close your browser windows AND Frontpage/Word/Excel (whatever MIGHT open an Inet session). Do a SERVER HEALTH/PERMISSIONs check and DETECT AND REPAIR all settings. Error will dissapear (for now that is

3. If you use the FP Web Tool make sure you do the following
* Remove/un-install previous versions of .NET and all earlier versions of FP Extension (Preferred but not really required
* Then install .NET framework (If you plane to use ASP.NET) (Reboot
* Give domain admins/ASP.NET account (or your account) full access to the WWWRoot (Click RESET AND APPLY TO SUBFOLDERS in advanced
* After installing FP Extension 2002, Install the Sercity Hotfix for it. (Reboot
* In the Internet Service Manager tool (Admin tools), right click the server and choose (MANAGE/CREATE/UPGRADE FP 2002. This way the ENTIRE server is now updated (Not just the DEFAULT web site)
* Now use the Web Interface EXTEND the FP entensions to the site (If not already done for you). Add DOMAIN/your account to as an ADMINISTRATOR inside of FP 2002

That about should do it. Reboot just to make sure

 

[Sandra]

The IIS is a LOCAL host. I went to Control Panel-

Administrative tools->Microsoft Sharepoint Administrator-
Default Web Site ->Create a Subweb. This is the same

process I used to create the first subweb which works.
Should you use a different process for the second subweb??

Thanks for replying.

-----Original Message-----
How are you creating the subweb, from within IIS or FP.

If IIS open the rootweb in FP, create a folder, then

right click the folder and select to convert to

web.

If you have direct access to the server, then you may

need to stop and start IIS, before you can

access or publish to the subweb directly. Also if this

is local, then you should always create your

 

[Sandra]

Does it work through FrontPage if the IIS is a LOCAL host?
I don't know anything about .NET framework

I installed IIS with the "quiet install" provided from
the download.

Thank you.

-----Original Message-----
Actually I used to have this problem until I figured out

this about FP Extensions 2002 and FP the Office Product

1. Use Frontpage to set up the Virtual Directory/Subweb

(it does it the cleanest without you having to access the
Main Frontpage Admin Web Site)

2. When creating sites from Internet Service manager,

CLOSE IIS after creating a virtual web. Just to be safe.
(The IIS admin interface creates a similar to the FP Web
Admin interface error). In order to fix the Web interface
problem, you only need to close your browser windows AND
Frontpage/Word/Excel (whatever MIGHT open an Inet
session). Do a SERVER HEALTH/PERMISSIONs check and DETECT
AND REPAIR all settings. Error will dissapear (for now
that is)

3. If you use the FP Web Tool make sure you do the following:
* Remove/un-install previous versions of .NET and all

earlier versions of FP Extension (Preferred but not
really required)

* Then install .NET framework (If you plane to use ASP.NET) (Reboot)
* Give domain admins/ASP.NET account (or your account)

full access to the WWWRoot (Click RESET AND APPLY TO
SUBFOLDERS in advanced)

* After installing FP Extension 2002, Install the

Sercity Hotfix for it. (Reboot)

* In the Internet Service Manager tool (Admin tools),

right click the server and choose (MANAGE/CREATE/UPGRADE
FP 2002. This way the ENTIRE server is now updated (Not
just the DEFAULT web site).

* Now use the Web Interface EXTEND the FP entensions to

the site (If not already done for you). Add DOMAIN/your
account to as an ADMINISTRATOR inside of FP 2002.

 

[Thomas A. Rowe]

Best to just open the root web in FP, create a folder, then right click the folder and select
convert to web.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

 

[Tom Pepper Willett]

I simply open FP, File | New web and it creates just fine.
--
=====================================================
Tom Pepper Willett [Microsoft MVP - FrontPage]
----------------------------------------------------------------------------
-
Microsoft FrontPage:
http://www.microsoft.com/office/frontpage/prodinfo/default.mspx
http://msdn.microsoft.com/office/understanding/frontpage/

=====================================================

 

[Thomas A. Rowe]

I just chatted with Tom P, and what he was referring to below, will create a new subweb, not a new
website, which is what I was talking about.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

I simply open FP, File | New web and it creates just fine.
--
=====================================================
Tom Pepper Willett [Microsoft MVP - FrontPage]
----------------------------------------------------------------------------
-
Microsoft FrontPage:
http://www.microsoft.com/office/frontpage/prodinfo/default.mspx
http://msdn.microsoft.com/office/understanding/frontpage/
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
=====================================================

Best to just open the root web in FP, create a folder, then right click the folder and select
convert to web.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

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

 

[Tom Pepper Willett]

Yep. Sorry about that. I got off on a tangent and thought we were talking
subwebs. But, Tom R. called me and we got back on the same page.
--
=====================================================
Tom Pepper Willett [Microsoft MVP - FrontPage]
----------------------------------------------------------------------------
-
Microsoft FrontPage:
http://www.microsoft.com/office/frontpage/prodinfo/default.mspx
http://msdn.microsoft.com/office/understanding/frontpage/

=====================================================

 

[lilyforum]

Thank you...

Thank you for this post. Although it's been awhile, it saved my butt. Yes, my company works in the stone age of technology.

The IIS is a LOCAL host. I went to Control Panel-
>Administrative tools->Microsoft Sharepoint Administrator-
>Default Web Site ->Create a Subweb. This is the same
process I used to create the first subweb which works.
Should you use a different process for the second subweb??

Thanks for replying.