IIS 7 and Above
Configuration & Scripting
Application Error - System.Web.Helpers
Last post Feb 13, 2018 04:12 AM by cheezefrog
Feb 13, 2018 01:41 AM|cheezefrog|LINK
So I recently upgraded my Windows Server from 2008 to 2016 and now my website is showing this error when browsing.
Does anyone have any suggestions? I assume it has to do with ASP.NET being out of date or something like that. If it is fixable via re publishing it through Visual Studio is there
a write-up step by step to resolve this?
thanks in advance
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific
error details below and modify your configuration file appropriately.
Parser Error Message: Could not load file or assembly 'System.Web.Helpers, Version=188.8.131.52, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
Line 19: <assemblies>
Line 20: <add assembly="System.Web.Abstractions, Version=184.108.40.206, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
Line 21: <add assembly="System.Web.Helpers, Version=220.127.116.11, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
Line 22: <add assembly="System.Web.Routing, Version=18.104.22.168, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
Line 23: <add assembly="System.Web.Mvc, Version=22.214.171.124, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
Source File: C:\inetpub\wwwroot\sosariaonline.net\httpdocs\web.config Line: 21
Assembly Load Trace: The following information can be helpful to determine why the assembly 'System.Web.Helpers, Version=126.96.36.199, Culture=neutral, PublicKeyToken=31bf3856ad364e35' 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].
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.2623.0
Feb 13, 2018 03:18 AM|Yuk Ding|LINK
What version of your system.web.helpers did you see in visual studio properties? On my side, it is 188.8.131.52. So you need to check whether the newversion attribute is using the correct version. If the version of system.web.helps is displaying 184.108.40.206 then
you should modify the attribute to 220.127.116.11. First of all, please ensure it just works fine in IIS.
In addition, please ensure IIS asp.net feature has been installed and deploy the MVC application following this link:
Then you need to check whether the bin folder under your application's root folder have the system.web.helper.
Considering you were deploying the application to the subfolder under IIS, please try to convert it to application instead of a signal virtual directory.
Finally, please ensure the application pool identity ' IIS Apppool\<app pool name>' have enough permission to load the dll.
Feb 13, 2018 04:12 AM|cheezefrog|LINK
I really appreciate your time to reply. I believe I have managed to fix the issue. The project was pretty old (deployed in VS2010) so I reloaded it into VS2017 w/ updated references and .NET 4.5 and now it seems to load just fine after republishing.