Module activation error after import

Posted by Community Admin on 04-Aug-2018 19:53

Module activation error after import

All Replies

Posted by Community Admin on 21-Aug-2012 00:00
I am developing a module with the Module Builder, and it all works fine on my local Sitefinity install. I have uploaded to a QA server an earlier version of the module via the Export structure/import module functionality and it worked fine.

When I try to upload an updated version of the same module (extra fields). The error from error.log is this:
Type : System.Exception, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Message : ContentView control with key 'Telerik.Sitefinity.DynamicTypes.Model.McLarenEvents.MclarenEventBackendDefinition' cannot be added for module 'ModuleBuilder', because it is already used by module 'McLaren Events'
Source : Telerik.Sitefinity
Help link :
Data : System.Collections.ListDictionaryInternal
TargetSite : Void HandleException(System.Exception, Boolean)
Stack Trace :    at Telerik.Sitefinity.DynamicModules.Builder.Install.ModuleInstaller.HandleException(Exception ex, Boolean commitTransaction)
   at Telerik.Sitefinity.DynamicModules.Builder.Install.ModuleInstaller.InstallModule(DynamicModule module, Boolean commitTransaction)
   at Telerik.Sitefinity.DynamicModules.Builder.Web.Services.ContentTypeService.ActivateContentTypeInternal(String moduleId, String providerName)
   at SyncInvokeActivateModule(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
 
Additional Info:
<snip>
FullName : Telerik.Sitefinity.Utilities, Version=5.1.3270.0, Culture=neutral, PublicKeyToken=b28c218413bdf563
AppDomainName : /LM/W3SVC/2/ROOT-1-129900513864500407
ThreadIdentity :
WindowsIdentity : IIS APPPOOL\USER
 
A very similar module went through the same process fine.

I have deleted the old module before importing it again.

Could this be due to a reference to it being used somewhere in the site holding onto the old code?

Any suggestions appreciated,

Regards,
David
This thread is closed