Forums

 
  Support Forum  Modules  Engage: Publish  module currently unavailable
Previous Previous
 
Next Next
New Post 1/12/2010 12:45 AM
Unresolved
  lindyolsen
3 posts
No Ranking


module currently unavailable 
Modified By lindyolsen  on 1/12/2010 7:50:13 PM)

Hi guys, I am getting the same error and the module was previously working. we are running DNN v 4.9.1 and publish v 04.05.00

we recently installed Ultra Video Gallery which altered the web.config file so i'm not sure if this has anything to do with it. 

Here is the link to the first page which lists all the articles http://www.lindyolsen.com/Members/Articles/StrengthTraining/tabid/4511/language/en-US/Default.aspx

Click on any of the artciles and you'll get the error.  

This is the link to the actual page (without clicking on an article) you still get the error so i am wondering if part of the module has been broken somehow.

thanks so much for your help.

regards

Lindy :)

Lindy :)

 
New Post 1/12/2010 10:35 PM
  Chris Hammond
1110 posts
1st Level Poster


Re: module currently unavailable 

Lindy,

What is the error message you are getting (when logged in as HOST)?

Chris


DotNetNuke Core Team Member
Engage Software
St. Louis, MO
314.966.4000



The leading provider of DotNetNuke support, training and custom development.
 
New Post 1/12/2010 11:18 PM
  lindyolsen
3 posts
No Ranking


Re: module currently unavailable 

Hey Chris,

here it is (and thankyou)

DotNetNuke.Services.Exceptions.ModuleLoadException: Could not load file or assembly 'AjaxControlToolkit, Version=1.0.10920.32880, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.Web.HttpParseException: Could not load file or assembly 'AjaxControlToolkit, Version=1.0.10920.32880, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.IO.FileLoadException: Could not load file or assembly 'AjaxControlToolkit, Version=1.0.10920.32880, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'AjaxControlToolkit, Version=1.0.10920.32880, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' at System.Signature._GetSignature(SignatureStruct& signature, Void* pCorSig, Int32 cCorSig, IntPtr fieldHandle, IntPtr methodHandle, IntPtr declaringTypeHandle) at System.Signature.GetSignature(SignatureStruct& signature, Void* pCorSig, Int32 cCorSig, RuntimeFieldHandle fieldHandle, RuntimeMethodHandle methodHandle, RuntimeTypeHandle declaringTypeHandle) at System.Signature..ctor(RuntimeFieldHandle fieldHandle, RuntimeTypeHandle declaringTypeHandle) at System.Reflection.RtFieldInfo.get_FieldType() at System.Web.UI.Util.GetNonPrivateFieldType(Type classType, String fieldName) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildFieldDeclaration(ControlBuilder builder) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildSourceDataTreeFromBuilder(ControlBuilder builder, Boolean fInTemplate, Boolean topLevelControlInTemplate, PropertyEntry pse) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildSourceDataTreeFromBuilder(ControlBuilder builder, Boolean fInTemplate, Boolean topLevelControlInTemplate, PropertyEntry pse) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildSourceDataTreeFromBuilder(ControlBuilder builder, Boolean fInTemplate, Boolean topLevelControlInTemplate, PropertyEntry pse) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildSourceDataTreeFromBuilder(ControlBuilder builder, Boolean fInTemplate, Boolean topLevelControlInTemplate, PropertyEntry pse) at System.Web.Compilation.TemplateControlCodeDomTreeGenerator.BuildMiscClassMembers() at System.Web.Compilation.BaseCodeDomTreeGenerator.BuildSourceDataTree() at System.Web.Compilation.BaseCodeDomTreeGenerator.GetCodeDomTree(CodeDomProvider codeDomProvider, StringResourceBuilder stringResourceBuilder, VirtualPath virtualPath) at System.Web.Compilation.BaseTemplateBuildProvider.GenerateCode(AssemblyBuilder assemblyBuilder) at System.Web.Compilation.AssemblyBuilder.AddBuildProvider(BuildProvider buildProvider) 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]. --- End of inner exception stack trace --- at System.Web.Compilation.AssemblyBuilder.AddBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at Engage.Dnn.Publish.ItemDisplay.LoadControlType() --- End of inner exception stack trace ---

 
New Post 1/13/2010 6:56 AM
  Chris Hammond
1110 posts
1st Level Poster


Re: module currently unavailable 

You'll need to put that DLL back in the bin folder, unless the UMG module uses the .NET 3.5 version of that DLL, if that is the case you'll have to recompile Publish to use the newer DLL. We don't provide support for the 3.5 version of the DLL as we distribute with the module the DLL that your error message says is now missing.


DotNetNuke Core Team Member
Engage Software
St. Louis, MO
314.966.4000



The leading provider of DotNetNuke support, training and custom development.
 
New Post 1/13/2010 7:36 PM
  lindyolsen
3 posts
No Ranking


Re: module currently unavailable 
Modified By lindyolsen  on 1/13/2010 8:28:01 PM)

Hi Chris, I put the DLL back into the folder and  it brought down the prod server.  but we're back up so all good.

We installed a new skin which updated the AjaxControlToolkit.dll.  we are currently running Publish_Standard_4.5.0_Install.zip on DNN 4.9.1.

Is there an updated version of publish which uses a more recent version of AjaxControlToolkit.dll?

thanks again for all your help.

regards

Lindy :)

 

 
Previous Previous
 
Next Next
  Support Forum  Modules  Engage: Publish  module currently unavailable

Purchase

Please click here to buy now.
Payment will be processed via credit card or PayPal.

Test Drive!

Want to find out how it works? Visit our demo site to see the modules in actions!

Subscribe

Sign up for our newsletter and get the latest product updates!

Online Support

Powered by DotNetNuke