Henrik Fransas
Sep 9, 2014
visibility 5143
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
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026