YAFLogo

ocortez
  • ocortez
  • 50.2% (Neutral)
  • YAF Forumling Topic Starter
11 years ago
Hello All,

I'm trying to upgrade our install to the latest version but have run into problems going to /install/default.aspx after following the upgrade doc instriction changes to web.conf. The error message is below. Any help would be greatly appriciated! Thanks.

Server Error in '/iforum' Application.

--------------------------------------------------------------------------------

Could not load file or assembly 'Autofac.Configuration' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.BadImageFormatException: Could not load file or assembly 'Autofac.Configuration' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Autofac.Configuration' could not be loaded.

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Stack Trace:

[BadImageFormatException: Could not load file or assembly 'Autofac.Configuration' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.]

System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0

System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +416

System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +166

System.Reflection.Assembly.Load(String assemblyString) +35

System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +190

[ConfigurationErrorsException: Could not load file or assembly 'Autofac.Configuration' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.]

System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +11241896

System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +388

System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +232

System.Web.Configuration.AssemblyInfo.get_AssemblyInternal() +48

System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +210

System.Web.Compilation.BuildProvidersCompiler..ctor(VirtualPath configPath, Boolean supportLocalization, String outputAssemblyName) +76

System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed) +11231074

System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories) +185

System.Web.Compilation.BuildManager.CompileCodeDirectories() +654

System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +658

[HttpException (0x80004005): Could not load file or assembly 'Autofac.Configuration' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.]

System.Web.Compilation.BuildManager.ReportTopLevelCompilationException() +76

System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +1012

System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters) +1025

[HttpException (0x80004005): Could not load file or assembly 'Autofac.Configuration' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.]

System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +11335894

System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +88

System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +11209384

--------------------------------------------------------------------------------

Version Information: Microsoft .NET Framework Version:2.0.50727.5466; ASP.NET Version:2.0.50727.5456

Sponsor
tha_watcha
  • tha_watcha
  • 100% (Exalted)
  • YAF.NET Project Lead 🤴 YAF Version: 4.0.0 rc 2
11 years ago
The latest version is .NET 4 only. If your server supports .net 4, change the application pool to 4.0.
ocortez
  • ocortez
  • 50.2% (Neutral)
  • YAF Forumling Topic Starter
11 years ago
Thanks for the prompt response! I tried that and I get error 500.

Server Error

500 - Internal server error.

There is a problem with the resource you are looking for, and it cannot be displayed.

Thanks,

Ozzy

squirrel
11 years ago
Need to change IIS configuration to allow detailed errors to clients, then change YAF web.config and set customErrors to "Off" - this will give detailed error message --
If you can't find it using the forum search, try my signature link -- searches this site using Google: Google is my Friend 
ocortez
  • ocortez
  • 50.2% (Neutral)
  • YAF Forumling Topic Starter
11 years ago
Thanks for all the help! It turned out that I needed to register .net and once I did that via the cmd prompt and a quick IIS restart the site came up.

Best,

Ozzy