Views: 3730
Number of votes: 0
Average rating:

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:

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

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

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

I will report it to EPiServer as a bug

Sep 09, 2014

( 9/10/2014 9:26:01 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
( By Henrik Fransas, 9/11/2014 8:04:41 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

Please login to comment.