Upgrading to 2Sex圜ontent version 10.5 fixed that problem. However, 2Sex圜ontent no longer worked, giving an error about not having version 1.1.0 of that file.
Money server could not load file or assembly log4net fix install#
Commenting out that code in the web.config allowed the upgrade install process to work. This is where that version was coming from, 2Sex圜ontent version 10.1.0. The web.config had a binding that pointed to version 1.1.0 of the file (angle brackets replaced below with square braces): NET Framework Version:9 ASP.NET Version.0 (IIS7WorkerRequest wr, HttpContext context) +263 Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException) +590 CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded) +307 GetPreStartInitMethodsFromReferencedAssemblies() +99 GetReferencedAssemblies(CompilationSection compConfig) +176 LoadAllAssembliesFromAppDomainBinDirectory() +229 LoadAssemblyHelper(String assemblyName, Boolean starDirective) +777 LoadAssemblyHelper(String assemblyName, Boolean starDirective) +39 (String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +22 (String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection) +80 (AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurit圜hecks) +159 (AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurit圜hecks) +37 _nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurit圜hecks) +0 To turn this feature off, remove the registry value. Note: There is some performance penalty associated with assembly bind failure logging. To enable assembly bind failure logging, set the registry value (DWORD) to 1. WRN: Assembly binding logging is turned OFF.
Information regarding the origin and location of the exception can be identified using the exception stack trace below.Īssembly Load Trace: The following information can be helpful to determine why the assembly '' could not be loaded. (Exception from HRESULT: 0x80131040)Īn unhandled exception was generated during the execution of the current web request.
The located assembly's manifest definition does not match the assembly reference.
Please review the stack trace for more information about the error and where it originated in the code.Įxception Details: System.IO.FileLoadException: Could not load file or assembly '' or one of its dependencies. Any ideas on the problem?ĭescription: An unhandled exception occurred during the execution of the current web request. In several attempts to upgrade my localhost from 9.3.2 to 9.4 using "DNN_Platform_9.4.0_Upgrade.zip" I get an error when accessing the site after unzipping the files to the server.Ĭould not load file or assembly '' or one of its dependencies.