You receive a 403.18 error message when you run an MCMS application in a different application pool on IIS 6.0

Article translations Article translations
Article ID: 842429 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

On a computer that is running Microsoft Internet Information Services (IIS) 6.0, when you isolate a Microsoft Content Management Server (MCMS) 2002 application in a different application pool from where the Web site is hosted, you may receive the following 403.18 error message from the server:
Forbidden: Cannot execute requested URL in the current application pool.
If you move the MCMS application back into the application pool that hosts the Web site where the application is running, the Web site functions correctly again.
This behavior is by design.

MORE INFORMATION

The MCMS application must run in the same application pool where the MCMS Web site is bound. If the Web site and the MCMS application are hosted in different application pools, the Web site and the MCMS application cannot communicate.

If you move any one of the following virtual directories to a different application pool, this issue might occur:
  • mcms
  • nr
  • nrconfig
  • webctrl_client
  • channels
  • All top-level channels in MCMS 2002
  • MCMS Web application virtual directories that do not have a matching top-level channel
If process isolation is required for an MCMS application, you must create a new Web site and enable it as a Web Entry Point in the MCMS Server Configuration Application. You can then move both the MCMS application and the Web site into their own application pool to provide process isolation.

Properties

Article ID: 842429 - Last Review: January 10, 2015 - Revision: 1.0
APPLIES TO
  • Microsoft Content Management Server 2002
Keywords: 
kbnosurvey kbarchive kbinfo KB842429

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com