Try our conversational search powered by Generative AI!
AI OnAI Off
Could not load type 'EPiServer.Web.InitializationModule' from assembly 'EPiServer'
Do you have any 3rd parties assembly hanging around? They might be the culprit?
Also make sure you have the correct binding redirect in web.config
Edited,
Feb 27, 2018 16:45
<p>I have viewed the assemblies being loaded using FusionLog, and indeed have seen that there are some custom Epi add-onns that were referencing an old Epi version 10.0.1.0. These add-ons were POSSIBLE.RobotsTxtHandler and Geta.Tags. After updating both Nuget packages to their latest version the problem has disappeard (and replaced with another issue which I wont mention here.)</p>
<p>Thanks for the help!</p>
#188631
Feb 28, 2018 8:46
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
After following al upgrade steps from https://world.episerver.com/documentation/upgrading/Episerver-CMS/cms-11/breaking-changes-cms-11/to upgrade from CMS 10 to CMS 11, but I keep getting the following exception on trying to access the CMS via the browser:
Could not load type 'EPiServer.Web.InitializationModule' from assembly 'EPiServer, Version=10.0.1.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7'.
It seems that some code tries to load the type InitializationModule from the wrong assembly, as this specific type was moved from EpiServer.dll to EPiServer.Cms.AspNet, according to the upgrade documentation: EPiServer.Web.InitializationModule has been moved to EPiServer.Cms.AspNet assembly...
Still same issue.
Any ideas are welcome.