Error when copying DNN installs with ModuleActionsMenu

Mar 14, 2011 at 7:08 PM

Hello,

We have been running this module on all installs of DNN and to make our deployments faster, we created a core DNN install and just copy that with all starter modules in place. This all worked fine except for on recent copies, the install throws the following error:

An error has occurred.
DotNetNuke.Services.Exceptions.ModuleLoadException: Could not load file or assembly 'System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. ---> System.IO.FileNotFoundException: Could not load file or assembly 'System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. File name: 'System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' ---> System.IO.FileNotFoundException: Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. File name: 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' 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]. at WatchersNET.SkinObjects.ModuleActionsMenu.Menu.RegisterJavaScript() at WatchersNET.SkinObjects.ModuleActionsMenu.Menu.LoadMenu() --- End of inner exception stack trace ---

Everything looks fine in the files and the web.config as far as I can tell (though I am still rather new to DNN). Everything matches from a working install to the newer installs. the DNN installs are 5.6.1, the module version is 1.2.3.

Any help with this would be appreciated.

Thanks,

Jeremy Close

Mar 15, 2011 at 9:11 AM
Edited Mar 15, 2011 at 9:11 AM

Looks like the same Problem Posted here:

http://www.dotnetnuke.com/tabid/795/forumid/48/postid/409915/scope/posts/default.aspx

In the <runtime><assemblyBinding . . . > section of the site's web.config file do you have the following binding redirects:

<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
</dependentAssembly>
<dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1">
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
</dependentAssembly>

If you had either developed the site in an application pool running ASP.Net 4.0 and then migrated the site to the present server where .Net Framework 3.5 and not 4.0 is installed or if you had switched the application pool of the present site to 4.0 then back to 2.0/3.5, it is likely that you'll see newVersion="4.0.0.0" instead. If that is the case, other areas of web.config may have references to 4.0 that will cause other issues.