Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogBlog Error after upgrading from 4.8 to version 5.01.01Blog Error after upgrading from 4.8 to version 5.01.01
Previous
 
Next
New Post
8/15/2009 9:33 PM
 

Hi,

 

I am getting the following error on my blog module I have tried over installing the module, this has not helped after upgrading from version 4.8 to 5.01.01. Your help would be much appreciated if anyone knows what the fix is?

 

Regards

Richard

An error has occurred.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.NavigationControl.SolpartMenuNavigationProvider.Bind(DNNNodeCollection objNodes) at DotNetNuke.UI.WebControls.SolPartActions.BindMenu(DNNNodeCollection objNodes) at DotNetNuke.UI.WebControls.SolPartActions.BindMenu() at DotNetNuke.UI.WebControls.SolPartActions.Page_PreRender(Object sender, EventArgs e) --- End of inner exception stack trace ---

 

 
New Post
8/18/2009 4:25 PM
 

Richard Gush wrote

I am getting the following error on my blog module I have tried over installing the module, this has not helped after upgrading from version 4.8 to 5.01.01. Your help would be much appreciated if anyone knows what the fix is?

 An error has occurred.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.NavigationControl.SolpartMenuNavigationProvider.Bind(DNNNodeCollection objNodes) at DotNetNuke.UI.WebControls.SolPartActions.BindMenu(DNNNodeCollection objNodes) at DotNetNuke.UI.WebControls.SolPartActions.BindMenu() at DotNetNuke.UI.WebControls.SolPartActions.Page_PreRender(Object sender, EventArgs e) --- End of inner exception stack trace ---

I got the same error and noticed it when I upgraded from 4.9.4 to 5.1.1.  Any solutions?  I see this in the View_Blog section in EDIT mode.

 
New Post
8/18/2009 9:29 PM
 

I didn't upgrade but in my newly created 5.1.1 portal, I receive the following:

An error has occurred.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.NavigationControl.SolpartMenuNavigationProvider.Bind(DNNNodeCollection objNodes) at DotNetNuke.UI.WebControls.SolPartActions.BindMenu(DNNNodeCollection objNodes) at DotNetNuke.UI.WebControls.SolPartActions.BindMenu() at DotNetNuke.UI.WebControls.SolPartActions.Page_PreRender(Object sender, EventArgs e) --- End of inner exception stack trace ---

Need be, I can start over and use 4.9.4 as my portal version. I was just trying to start in 5.x.x since that is probably where the future lies.

 
New Post
8/19/2009 12:43 AM
 

The error your seeing is due to a missing attribute that is required in DNN 5.1.x - this is easy to fix!

If your site is on your local machine open Windows Explorere or if on a Server located away from your office, using your favorite FTP tool do the following...

  1. Navigate to: "Root Folder Name"/Portals/_default/Containers/"The name of the container your using"
  2. or if not loocated at the step #1 location, navigate to: "Root Folder Name"/Portals/0/Containers/"The name of the container your using" 
  3. Copy the container that is throwing the error
  4. Place the copy in a safe place
  5. Back at the folder where you copied the container from, open the container using notepad, notepad ++, textpad, ultraedit (whichever tool you prefer) by right clicking the container and selecting "open with."
  6. Once you have the file open and you are looking at the HTML find the "<dnn:ACTIONS runat="server" ID="dnnACTIONS" />" tag and modify it by adding the ProviderName attribute so it looks like this: <dnn:ACTIONS runat="server" ID="dnnACTIONS" ProviderName="DNNMenuNavigationProvider"/>
  7. Save the file and move it back into the folder you found it in (if you moved it out of the folder)
  8. Reload the page, your error should be gone.


NOTE: This should be done for all the container's loaded into your site 

Cheers!


Wisconsins DNN User Group: www.WIDNN.com
Visit my home page: www.HerbBenton.com
 
New Post
8/19/2009 11:00 AM
 

Herb Benton wrote

The error your seeing is due to a missing attribute that is required in DNN 5.1.x - this is easy to fix!

If your site is on your local machine open Windows Explorere or if on a Server located away from your office, using your favorite FTP tool do the following...

  1. Navigate to: "Root Folder Name"/Portals/_default/Containers/"The name of the container your using"
  2. or if not loocated at the step #1 location, navigate to: "Root Folder Name"/Portals/0/Containers/"The name of the container your using" 
  3. Copy the container that is throwing the error
  4. Place the copy in a safe place
  5. Back at the folder where you copied the container from, open the container using notepad, notepad ++, textpad, ultraedit (whichever tool you prefer) by right clicking the container and selecting "open with."
  6. Once you have the file open and you are looking at the HTML find the "<dnn:ACTIONS runat="server" ID="dnnACTIONS" />" tag and modify it by adding the ProviderName attribute so it looks like this: <dnn:ACTIONS runat="server" ID="dnnACTIONS" ProviderName="DNNMenuNavigationProvider"/>
  7. Save the file and move it back into the folder you found it in (if you moved it out of the folder)
  8. Reload the page, your error should be gone.


NOTE: This should be done for all the container's loaded into your site 

Cheers!

Herb, thank you for the detailed instructions.  That did work for me.  The only difference is the HTML file you refererence in STEP 6 is an .ascx file.  I just wanted to make sure for others, just in case.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogBlog Error after upgrading from 4.8 to version 5.01.01Blog Error after upgrading from 4.8 to version 5.01.01


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out