03-16-07 06:17 PM
Hi Marek,
please check the IIS log.
What is the substatus code of the 403?
If enabled it will be the number behind the 403.
It will give us the explanation about why the 403 happend.
Cheers,
Stefan
"Marek zegarek" <testowy@mailik.pl> wrote in message
news:ub%23U539ZHHA.4508@TK2MSFTNGP03.phx.gbl...
> 1) Check in the IIS master properties if the two CMS ISAPI filters are
> listed and that they are not listed twice
>
> I checked it - I've got two filters without double.
>
> 2) If this is Windows XP:
> Go to your Local Computer Policy, click Computer Configuration, then
> Windows Settings, then Security Settings, then Local Policy, then Security
> Options. Change the "Network access: Sharing and security model for local
> accounts" setting to "Classic - local users authenticate as themselves".
>
> I have Classic option set
>
> 3) If Sharepoint Portal Server 2003 is installed look in the Internet
> Information Server (IIS) log. You will see a 403.18 which means "Cannot
> execute requested URL in the current application pool." Ensure that MCMS
> and Sharepoint Portal Server are configured to use the same application
> pool.
>
> I don't have Sharepoint on this server and in domain
>
> 4) Ensure that all MCMS folders run in the same application pool as the
> Web site. See here for details:
> 842429 - You receive a 403.18 error message when you run an MCMS
> application in a different application pool on IIS 6.0
>
> I have all in the same application pool.
> ----------------------------
> I saw this FAQ few minutes before my question here.... No solution
> there....
>
>
> Użytkownik "Stefan Goßner [MSFT]" <stefang@online.microsoft.com> napis
ał w
> wiadomości news:OOcAjt9ZHHA.3968@TK2MSFTNGP06.phx.gbl...
>
>
[ Post a follow-up to this message ]
| 
