Petter Klang
Oct 18, 2013
  4581
(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.

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


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

Oct 18, 2013

Comments

Eric
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
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
Create a multi-site aware custom search provider using Search & Navigation

In a multisite setup using Optimizely CMS, searching for pages can be confusing. The default CMS search regardless of search provider does not...

dada | Jun 12, 2025

Tunning Application Insights telemetry filtering in Optimizely

Application Insights is a cloud-based service designed to monitor web applications, providing insights into performance, errors, and user behavior,...

Stanisław Szołkowski | Jun 12, 2025 |

JavaScript SDK v6: Lightest, Most Efficient SDK Yet

Need a faster site and less frontend bloat? JavaScript SDK v6 is here —and it’s the lightest, smartest SDK we’ve ever released for Optimizely Featu...

Sarah Ager | Jun 11, 2025

Boosting Indexing Efficiency: Reindex Pages Directly from Optimizely’s Navigation Pane

There can be various reasons why you might want to trigger indexing or reindexing of a page/node directly from the navigation pane. In my case, we...

Praful Jangid | Jun 11, 2025