Knowledge Base

Server Extensions Must Run in Process on IIS 4.0

Article ID: 198118

Article Last Modified on 11/14/2003


APPLIES TO


This article was previously published under Q198118

SUMMARY

The FrontPage Server Extensions must run in process, rather than in their own memory space, when installed on Internet Information Server (IIS) 4.0.

MORE INFORMATION

When you configure the FrontPage Server Extensions, by default the extensions create an App root in IIS 4.0, and that App root runs in process.

If you add the NoVtiBinApproots=1 setting to the [FrontPage 3.0] section of the Frontpg.ini file, the _vti_bin directory is not made into an App root when the extensions are installed. With this setting, the Web site cannot be run out of process.

For more information about the implications of running the FrontPage Server Extensions with the NoVtiBinApproots setting, please see the security section of the SERK (Server Extensions Resource Kit) online at
http://officeupdate.microsoft.com/frontpage/wpp/serk.

If you want to run the Web site out of process, the _vti_bin directory MUST be an App root and must NOT be run out of process.

NOTE: You cannot run the _vti_bin directory out of process under ANY circumstances.

In versions 3.0.2.1117 and earlier of the FrontPage Server Extensions, the _vti_bin is hard-coded to run in process. The _vti_bin directory can be checked to run out of process in IIS 4.0; there is no effect on the server extensions. The extensions themselves will still run in process.

Keywords: kbinfo KB198118