Try our conversational search powered by Generative AI!

Petter Klang
Oct 18, 2013
  4321
(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
Optimizely Web... 6 Game Changing Features in 2024

If you are interested in learning about what's new within Optimizely Web, you are in the right place. Carry on reading to learn about the 6 greates...

Jon Jones | Mar 3, 2024 | Syndicated blog

Headless forms reloaded (beta)

Forms is used on the vast majority of CMS installations. But using Forms in a headless setup is a bit of pain since the rendering pipeline is based...

MartinOttosen | Mar 1, 2024

Uploading blobs to Optimizely DXP via PowerShell

We had a client moving from an On-Prem v11 Optimizely instance to DXP v12 and we had a lot of blobs (over 40 GB) needing uploading to DXP as a part...

Nick Hamlin | Mar 1, 2024 | Syndicated blog

DbLocalizationProvider v8.0 Released

I’m pleased to announce that Localization Provider v8.0 is finally out.

valdis | Feb 28, 2024 | Syndicated blog