Re: 403 Error after extending a SharePoint Site

From: Mike Walsh [MVP] (englantilainen_at_hotmail.com)
Date: 03/26/04 

Date: Fri, 26 Mar 2004 07:32:33 +0200

1. This is a SharePoint Portal Server 2003 installation problem and should
therefore NOT be posted here (the Windows SharePoint Services newsgroup) but
to the SPS newsgroup at microsoft.public.sharepoint.portalserver.

2. As far as I know only WSS can be installed on Web edition (together with
as you have another server running SQL Server).

However as this is the WSS newsgroup we in any case only answer questions on
WSS (and on WSS problems common to all implementations). Please post SPS
questions only to its newsgroup.

Mike Walsh, Helsinki, Finland
WSS FAQ at wss.collutions.com
Please post questions to the newsgroup only.

"Victor Turegano" <vTuregano@no_spam.invalid.net> wrote in message
news:OyUc4utEEHA.1600@tk2msftngp13.phx.gbl...
> Hi All, I'm having a similar problem but I don't think it's App Pool
> related. This is what I've done and the error.
>
> 1. Intall 2 W2k3 Web Edition + 1 W2k3/SQL for DB
> 2. (According to SP Admin Guide) Configure NLB and Farm Installation
> pre-requisites.
> 3. Install Sharepoint Portal Server on both Web Front End servers
> 4. Create Config DB from NODE1 and connect to the DB in NODE2
> 5. Create empty folder C:\Prod\SiteRoot in both NODES
> 6. Create Web Site using IIS in BOTH Nodes
> 7. Extend using only SharePoint Services in NODE1 creating both an
exclusive
> AppPool and a Content DB
> 8. Test extended site in NODE1 and apply template. Everything OK!
> 9. Extend site in NODE2 and connect to previously created DB
> 10. Test site in NODE2. I get an HTTP 403 "Directory Listing Denied"
error.
>
> Even if I try to create the site in NODE2 for start, I get the 403 error.
> I've already re-installed SharePoint Portal Server and still get the same
> error.
>
> The error only appears when I connect to NODE2. NODE1 works just fine. I
> have several extended sites working each in different AppPools. They all
> work Ok in NODE1 and return 403 errors in NODE2.
>
> Anyone has an idea?
>
> Best Regards,
>
>
> --
> [ Victor S Garcia Turegano ]
> I T i k o n s - IT Consulting Services
>
>
>

Relevant Pages

  • Re: Help
    ... The WSS that comes with SPS 2003 is indeed WSS 2.0 but that still doesn't mean that this newsgroup is for people who are running SPS 2003. ... this is what you wrote "I ran smigrate program to restore these files into SharePoint Portal Server 2003 blank site" it is completely clear from this that you are restoring to an SPS 2003 installation. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: SharePoint error with Windows Server 2003 hotfixes
    ... This is clearly a SharePoint Portal Server 2003 (SPS 2003) question. ... This newsgroup is for the standalone WSS product plus common WSS features. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Help
    ... The fact is that for people like you who refuse to accept that that WSS newsgroup is for people who have installed a WSS product and the ..portalserver newsgroup is for people who have installed the SPS 2003 or MOSS 2007 product there are newsgroups available for all products. ... this is what you wrote "I ran smigrate program to restore these files into SharePoint Portal Server 2003 blank site" it is completely clear from this that you are restoring to an SPS 2003 installation. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: SharePoint Namespaces
    ... This is a programming question. ... That too is a managed newsgroup so you will still get support there from ... I placed the .dll into my C:/Windows/Components folder. ... You can develop applications using the SharePoint Portal Server 2003 ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Share Point login
    ... Thank you for posting to the SBS Newsgroup. ... Server, and Sharepoint Portal Server is not SBS 2K3 Server components. ... - Microsoft Exchange Server ...
    (microsoft.public.windows.server.sbs)