|
Home > Archive > Microsoft Content Management Server > April 2006 > Error 403 - Access denied when switch to Edit Mode
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Error 403 - Access denied when switch to Edit Mode
|
|
| helloCMS 2006-04-01, 2:40 pm |
| We are encountering a really strange issue with CMS, on one of the
'staging/beta' site after the user authenticates himself, the pages
navigates through all its pages fine, but when the user switches to
edit mode in any page, the entire pages goes into 403 error: Access
denied. There are existing sites on the same authoring server that
behaves fine, ie. switches to edit mode with no problems.
The server is Win2k3, running CMS2002 SP1a, each CMS virtual site has
its own app pool. The strange thing is that when I do copy an existing
'working' CMS site into another newly created virtual server the edit
console gives the access denied err.
I have read Stefan's FAQ on 403 errrors but that did not help. There
were several issues similar to mine that appears in this newsgroup but
I have not read any conclusive solution. Can someone who had
experienced this problem and managed to resolve it please help me?
Thanks
Vincent W
| |
| Stefan [MSFT] 2006-04-01, 2:40 pm |
| Hi Vincent,
MCMS requires that all template projects are running in the same application
pool as the root of the website.
It is not allowed to have different template projects in the same IIS site
in different application pools.
If you need to use different application pools you are required to have
different IIS websites.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------
"helloCMS" <vincent.wongv@gmail.com> wrote in message
news:1143651215.090634.100550@g10g2000cwb.googlegroups.com...
> We are encountering a really strange issue with CMS, on one of the
> 'staging/beta' site after the user authenticates himself, the pages
> navigates through all its pages fine, but when the user switches to
> edit mode in any page, the entire pages goes into 403 error: Access
> denied. There are existing sites on the same authoring server that
> behaves fine, ie. switches to edit mode with no problems.
>
> The server is Win2k3, running CMS2002 SP1a, each CMS virtual site has
> its own app pool. The strange thing is that when I do copy an existing
> 'working' CMS site into another newly created virtual server the edit
> console gives the access denied err.
>
> I have read Stefan's FAQ on 403 errrors but that did not help. There
> were several issues similar to mine that appears in this newsgroup but
> I have not read any conclusive solution. Can someone who had
> experienced this problem and managed to resolve it please help me?
>
> Thanks
> Vincent W
>
| |
| helloCMS 2006-04-01, 2:40 pm |
| Hi Stefan,
Each template project is set up as an separate IIS site, and individual
app pool assigned to respective IIS sites. So yes, we have different
IIS sites using separate applicaiton pool.
>From my above post, I mentioned that there are 3 existing sites that
'switch to edit' mode works. So for testing purposes, I copied a
working code folder into another virtual directory, say from
040.workingsite.com to 041.replicatedworkingsite.com; technically
speaking, because the 040 works the new 041 site should switch to edit
mode without issues, however, this is not the case.
Test 2: I again ported the 041 code to a virtual directory, this time
in another CMS server (CMS_2) and import the SDO to CMS_2 database,
this time the 'switch to edit' works.
Test 3: I have double/triple check the permissions on file/code
folders, and even the CMS program files, everything looks kosher. We
even temporarily gave 'everyone' permissions on the folders to rule
out any access issues, but that did not work.
Using the process of elimination, the code works, gave 'everyone'
file/folder permissions, the database works (we tried in CMS_2 and it
works). I strongly suspect that the CMS software is corrupt.
I will try to 'repair' the CMS installation and see if that works.
BTW, keep the suggestions comming, I am sure that many out there are
facing or have faced the same issues that I am encountering at this
moment. I hope to resolve this so that we can document this in the KB.
Thanks!
| |
| Stefan [MSFT] 2006-04-01, 2:40 pm |
| Hi,
please double check if the website is MCMS enabled in the SCA.
If you missed this step you will also see a 403 error.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------
"helloCMS" <vincent.wongv@gmail.com> wrote in message
news:1143753405.505031.204480@j33g2000cwa.googlegroups.com...
> Hi Stefan,
>
> Each template project is set up as an separate IIS site, and individual
> app pool assigned to respective IIS sites. So yes, we have different
> IIS sites using separate applicaiton pool.
>
> 'switch to edit' mode works. So for testing purposes, I copied a
> working code folder into another virtual directory, say from
> 040.workingsite.com to 041.replicatedworkingsite.com; technically
> speaking, because the 040 works the new 041 site should switch to edit
> mode without issues, however, this is not the case.
>
> Test 2: I again ported the 041 code to a virtual directory, this time
> in another CMS server (CMS_2) and import the SDO to CMS_2 database,
> this time the 'switch to edit' works.
>
> Test 3: I have double/triple check the permissions on file/code
> folders, and even the CMS program files, everything looks kosher. We
> even temporarily gave 'everyone' permissions on the folders to rule
> out any access issues, but that did not work.
>
> Using the process of elimination, the code works, gave 'everyone'
> file/folder permissions, the database works (we tried in CMS_2 and it
> works). I strongly suspect that the CMS software is corrupt.
>
> I will try to 'repair' the CMS installation and see if that works.
>
> BTW, keep the suggestions comming, I am sure that many out there are
> facing or have faced the same issues that I am encountering at this
> moment. I hope to resolve this so that we can document this in the KB.
>
> Thanks!
>
|
|
|
|
|