Repro metabase corruption

Our project uses IIS to host custom web applications. We received an issue where sometimes the application pool wouldn’t start because of an corrupt configuration.


To reproduce the issue we run the software to install the web application. This way the application pool is created and available in the metabase for editing.

After completion stop the application pool, then open “C:\Windows\System32\inetsrv\config\applicationHost.config” and locate the applicationPool.

<!-- .... -->
      <add name="ReproAppPool" autoStart="false" managedRuntimeVersion="v4.0" />
<!-- .... -->

Change an attribute so it is not accepted by IIS (eg <add name=”ReproAppPool” managedSomething=”v4.0″ />) This will cause the metabase to throw the exception.

Now undo the change to the applicationHost.config. Other applications will stop throwing the HTTP500, but the ReproAppPool will not start by itself and that application keeps throwing HTTP503.

With this repro we can now fix the issue by adding some exception handling.

About erictummers

Working in a DevOps team is the best thing that happened to me. I like challenges and sharing the solutions with others. On my blog I’ll mostly post about my work, but expect an occasional home project, productivity tip and tooling review.
This entry was posted in Development and tagged , . Bookmark the permalink.

1 Response to Repro metabase corruption

  1. Pingback: Repro metabase COM Exceptions | .NET Development by Eric

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.