Attempting to upgrade to 5.1: "The configuration 'DynamicModulesConfig' is not registered"
I am doing a dry run on upgrading our project to 5.1 and I getting a TargetInvocationException, InnerException=""The configuration 'DynamicModulesConfig' is not registered"" in my custom modules.
The line of code is as follows:
DynamicModuleManager dynamicModuleManager = DynamicModuleManager.GetManager();
OK, I've redone the upgrade from scratch according to the instructions, and it has worked this time.
I am still having a problem that may be related to my previous problem. When I initially try to retrieve data for my Dynamic Module, the following code returns nothing. If I go into the back end and view the Content manager for my module, and then view my live site, I am then able to query data until my application is restarted again, and then it reverts to not working.
DynamicModuleManager dynamicModuleManager = DynamicModuleManager.GetManager();
Type menusettingType = TypeResolutionService.ResolveType("Telerik.Sitefinity.DynamicTypes.Model.MenuSettings.Menusetting");
// This is how we get the collection of MenuSetting items
var myCollection = dynamicModuleManager.GetDataItems(menusettingType);
foreach (var ms in myCollection)
I had this problem too. I have the config stored in the database:
<sitefinityConfig storageMode="Database" />
Thank you for your suggestion. Unfortunately, in my case, I am not using database storagemode. My DynamicModulesConfig.config file does appear to contain all of my modules.
Also, they have now put permissions on dynamic modules so that only Administrators can access items in the dynamic modules.
With help from Boyan from Telerik I solved this.
Thanks, that worked for me also.
I have simular issues. I've also got the error after upgrading to SF 5.1.
But now all my Dynamic Content parts are gone.
I had this as well but if you go to
Administration -> Modules, check to see if Module Builder has been installed.
For some reason mine wasn't and I clicked install and it worked again.
All my modules are now visible.
O.
@Owain:Yes I had to re-install the module. This was only possible after I made some changes to the System.config (had a wrong SF build reference).
I found a solution to my problem.
- Go to: Administration > Module Builder