Petter Klang
Oct 18, 2013
(1 votes)

Error installing Find on 7.0 site

Yesterday I found myself in the position to install EPiServer Find on a CMS 7 site but following the eminent blog from Ted I ran in to some issues. When getting the Nuget package I also got the updated CMS dll;s as Find has a dependency to it. When starting up the site I was hit with the YSOD telling me the following:

Error when creating the EPiServer.Configuration.Settings.All list: The <episerver> configuration section could not be found in the configuration file [ConfigurationErrorsException: Error when creating the EPiServer.Configuration.Settings.All list: The <episerver> configuration section could not be found in the configuration file]
   EPiServer.Configuration.EPiServerSection.GetAndValidateSection(Configuration config)

After some hair pulling and some digging around with Reflector I could see that EPi was loading the old EPiServer.Configuration.dll. And looking a the web.config I could see that not all my assembly redirects had been updated. So doing this manually fixed the problem.

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

Just wanted to share incase anyone else ever found themselves in the same situation.

Oct 18, 2013


Eric Oct 18, 2013 04:33 PM

I think using the nuget packages for CMS.Core and the dependency package .Framework will fix that for you. It came with pach 4 I think.

Oct 21, 2013 05:56 PM

My attendees got several different versions of this issue during my EPiServer Find training today.

Tricks I apply:
1) If you use the Alloy Demo templates. Using a notepad to edit your csproj file, remove the ReferencePath tag and Post Build actions that recompile your config files.
2) Using a notepad to view your csproj file, make sure you do not reference any assemblies with a absolute path, directly in your bin or modules bin.
3) Uninstall, reinstall all packages, rebuild, to update all assembly bindings and references to go to the packages folder

valdis Oct 29, 2013 06:32 AM

Eric, Adding EPiServer CMS Core and Framework .24 packages from NuGet do not updates *all* assembly redirects (this includes EPiServer.Licensing, EPiServer.Implementation and others among them).

Please login to comment.
Latest blogs
The 1001st Piece in your 1000 Piece Puzzle: .NET Default Interface Functions

I was recently working with a client who wanted a reasonably large subsystem added to Optimizely that would add automated management to their...

Greg J | Nov 28, 2022 | Syndicated blog

Video Demonstration, creating a CMS12 Alloy Sample Site

Hey All Below you will find a quick video demonstration on how to install a local version of Alloy Sample based on CMS12 / .Net 6. As you will see ...

Minesh Shah (Netcel) | Nov 28, 2022

How to create an admin user I Optimizely CMS – with Episerver CLI

In this blog post I’ll show how to create an admin user for Optimizely CMS in a new environment where you don’t have access to the admin interface.

Ove Lartelius | Nov 28, 2022 | Syndicated blog

Optimizely shortcuts in CMS 12 will get a trailing slash appended!

Not all URLs will work when the trailing slash is added, and that could cause problems. Hopefully it will be fixed soon.

Tomas Hensrud Gulla | Nov 26, 2022 | Syndicated blog