There have been numerous reports on DotNetNuke.com about errors encountered after switching to a skin with a vertical menu in DotNetNuke 4.4.1 if using a clean installation. These errors are typically "Null reference exception" errors, however some individuals have received general "an error has occured" messages with a portion of the site still visible.
If you have recently switched to a vertical menu and are receiving these error messages it is quite possible that you are missing a few required .dll files for the vertical menu system. It appears they were left out of the DNN installation files for 4.4.1. To fix this issue you will want to download a copy of DotNetNuke 4.3.7. Once you have downloaded 4.3.7 you will want to copy the following files from 4.3.7's bin folder and place them in your 4.4.1 bin folder.
- DotNetNuke.DNNTreeNavigationProvider.dll- DotNetNuke.ASP2MenuNavigationProvider.dll- DotNetNuke.Caching.BroadcastPollingCachingProvider.dll- DotNetNuke.Caching.BroadcastPollingCachingProvider.SQLDataProvider.dll- DotNetNuke.DNNDropDownNavigationProvider.dll- DotNetNuke.DNNMenuNavigationProvider.dll
After you have copied each of these DLL files over you should notice that your errors will go away.
Good luck! As always, feel free to provide comments below or ask questions in the forums!
Hey Mitchel,I recently move a 4.07.00 dnn site to a win2008 server (64 bit) and upgraded to 5.06.02. I am getting sporadic errors when initially loading a page in the site, upon refresh they go away - odd.here is the error I am seeing:Could not load file or assembly 'DotNetNuke.ASP2MenuNavigationProvider' or one of its dependencies. The module was expected to contain an assembly manifest. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.BadImageFormatException: Could not load file or assembly 'DotNetNuke.ASP2MenuNavigationProvider' or one of its dependencies. The module was expected to contain an assembly manifest.Any help or pointers appreciated!Regards,Allen
You will want to check for those DLL's and also what version of .NET are you running this under? (Post to the forums if you need additional help)
Mitchel, thanks!the site is running .NET Framework v2.0.50727.I will open a thread in the forums.alf
Name (required)
Email (required)
Website
Notify me of followup comments via e-mail
Content provided in this blog is provided "AS-IS" and the information should be used at your own discretion. The thoughts and opinions expressed are the personal thoughts of Mitchel Sellers and do not reflect the opinions of his employer.
Subscribe To Blog RSS Subscribe To Blog Updates by E-Mail * Add to Technorati Favorites
Click here for advertising information.
Content in this blog is copyright protected. Re-publishing on other websites is allowed as long as proper credit and backlink to the article is provided. Any other re-publishing or distribution of this content is prohibited without written permission from Mitchel Sellers.