Prevent crashes due to ‘system.webServer/runtime’ already defined

1 minute read • By Puneet Gupta • March 20, 2024

The following article addresses an issue that may arise within your application, particularly when utilizing XDT transforms or older versions of Site extensions from the App Service Site extension gallery. The symptoms include:

  1. The SCM site enters a crashing loop and fails to recover.
  2. The EventLog.xml file (present in %HOME%\LogFiles folder) records an error concerning a duplicate ‘system.webServer/runtime’ section:
<Data>~1YourSiteName</Data>
<Data>Config section 'system.webServer/runtime' already defined. Sections 
must only appear once per config file. See the help topic <location> for exceptions.
</Data>
<Data>\\?\D:\DWASFiles\Sites\#1YourSiteName\Config\applicationhost.config</Data>
<Data>1150</Data>
<Binary>B7000000</Binary>

This issue arises when a site extension (or custom XDT Transform) contains an incorrect XDT Transform utilizing Insert (instead of InsertIfMissing) to add a custom environment variable within the collection in the resulting applicationHost.config file. This leads to duplicate **'system.webServer/runtime'** tags, triggering the error. Notably, the following site extensions have updates available to address this issue:

  1. NewRelic
  2. Composer

It must be noted that error could surface while using custom XDT transforms or any other site extension that is using Insert instead of InsertIfMissing XDT transform.

How to Resolve

To resolve this problem, follow these steps:

  1. Get the FTP/S endpoing for your app. (Details in Get FTP/S endpoint).
  2. Navigate to /SiteExtensions folder.
  3. Locate the respective site extension and delete the SiteExtension folder (e.g. Composer, NewRelic).
  4. Restart the site from Azure Portal to ensure the site extension update takes effect.
  5. Navigate back to the Kudu Console (.azurewebsites.net) of your app and go to **Site Extensions** tab and install the latest version of the Site Extension from the gallery.

Please execute the mentioned steps only if you have identified that you are experiencing the issue described in the symptoms provided above.

If the app is utilizing a custom XDT Transform, ensure to use InsertIfMissing instead of Insert transform.

Additional Information

The emergence of this issue coincided with an update to the Diagnostic as a Service (DaaS) site extension by App Service. The rollout of this update commenced in February 2024. Notably, the latest iteration of the site extension introduced a new environment variable utilized by DaaS for diagnostic purposes. It is important to highlight that while the DaaS site extension appropriately employed the InsertIfMissing transform, the insertion of the system.webServer/runtime section conflicted with other XDT Transforms utilizing the Insert transform, resulting in failures due to the preexistence of the section.

You may also enjoy