HomeHomeDotNetNuke Forg...DotNetNuke Forg...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 6: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 1: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 6: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/18/2009 9:43 PM
 

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 8: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
HomeHomeDotNetNuke Forg...DotNetNuke Forg...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


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

Attend A Webinar
Free Demo Site
Download DotNetNuke Professional Edition Trial
Have Someone Contact Me
Have Someone Contact Me

Like Us on Facebook Join our Network on LinkedIn Follow DNN Corporate on Twitter Follow DNN on Twitter

Advertisers

DotNetNuke Scoop!

Sponsors

DotNetNuke Corporation

DotNetNuke Corp. is the steward of the DotNetNuke open source project, the most widely adopted Web Content Management Platform for building web sites and web applications on Microsoft. Organizations use DotNetNuke to quickly develop and deploy interactive and dynamic web sites, intranets, extranets and web applications. The DotNetNuke platform is available in a free Community and subscription-based Professional and Enterprise Editions with an Elite Support option. DotNetNuke Corp. also operates the DotNetNuke Store where users purchase third party apps for the platform.