Troubleshoot IIS feature delegation conflicts
- Last UpdatedOct 18, 2024
- 2 minute read
IIS feature delegation allows a web administrator to manage certain web configuration features. Web configuration is also handled by a web application’s web.config file.
If some of the web feature delegation settings are locked in IIS (that is, their delegation is set to Read Only), then MES Web Portal cannot automatically include those configuration settings in the MES Web Portal web.config file.
There are two options for handling this conflict:
-
Select the Update option and click the Configure button. The Configurator will update the IIS applicationHost.config file with the proper MES Web Portal configuration settings, and remove those settings from the MES Web Portal web.config file. (The feature settings can only be included in one of these files, but not both. Otherwise, the MES Web Portal web site will not run.)
-
Do not select Update option and click the Configure button. The Configurator does not update the IIS applicationHost.config file and leaves the conflicting feature settings in the web.config file. A message is logged that feature delegations were detected that must be added to the IIS configuration to support MES Web Portal.
To allow the MES Web Portal web site to run, a web administrator must then either:
-
Change the setting for the conflicting feature delegations to Read/Write in IIS Manager, or
-
Edit the IIS applicationHost.config file manually to set the feature settings to the appropriate MES Web Portal values and remove those settings from the MES Web Portal web.config file.
For instructions about how to set feature delegations in IIS Manager and how to manually modify the applicationHost.config file, refer to the IIS Feature Delegation topics on the Microsoft TechNet web site.
-