Henrik Fransas
Sep 9, 2014
visibility 5102
star star star star star
(0 votes)

How to solve “Missing configuration section: episerver” error

A couple of times I have gotten this message when updating the nuget-package from EPiServer. The problem is that one of the nuget packages has an error in it’s web.config transformation that puts the assembly-dependency back to an old version of EPiServer.Configuration.

If you see this error, check your configuration file (web.config) and search for this row:

<assemblyIdentity name="EPiServer.Configuration" publicKeyToken="8fe83dea738b45b7" culture="neutral" />

Check what version it says, for me after last upgrade it said:

<dependentAssembly>
  <assemblyIdentity name="EPiServer.Configuration" publicKeyToken="8fe83dea738b45b7" culture="neutral" />
  <bindingRedirect oldVersion="0.0.0.0-7.5.394.2" newVersion="7.5.394.2" />
</dependentAssembly>

That is a very old version, and after manually changing to the version I updated to (rightclick and select property on the EpiServer.Configuration – dll file below the package EPiServer CMS Core) I got it to work

dependentAssembly>
  <assemblyIdentity name="EPiServer.Configuration" publicKeyToken="8fe83dea738b45b7" culture="neutral" />
  <bindingRedirect oldVersion="0.0.0.0-7.13.3.0" newVersion="7.13.3.0" />
</dependentAssembly>

I will report it to EPiServer as a bug

Sep 09, 2014

Comments

Sep 10, 2014 09:26 AM

I cant see that we have changed anything regarding this. What we do is that we have a install.ps1 that is called during install. It will iterate over all files in the lib folder for that specific nuget package and add binding redirects for them. Clearly 7.5.394.2 version is not there....
My guess is for some reason is GAC installed assemblies involved, perhaps by Visual Studio??
But please report a bug, and then we can try to investigate more around this. Please add as much information as possible in the bug, that can be very useful during investigation.

Henrik Fransas
Henrik Fransas Sep 11, 2014 08:04 AM

I will do that Johan, I think it was in the order i installed it, but I will try to reproduce it on a alloy-site

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |

Giving Optimizely 13 Content Types Meaningful Icons and Thumbnails

When working with an Optimizely CMS solution that has evolved over time, it is common to end up with many content types. As the number grows, the...

Pär Wissmark | Sep 16, 2026 |