Select the search type
  • Site
  • Web
Search
You are here:  Support/Forums
Support

Bring2mind Forums

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 12/06/2006 9:29 AM by  Peter Donker
DNN 4.3.6 w/ Categories Error
 10 Replies
Sort:
You are not authorized to post a reply.
Author Messages
cstimpson
New Member
New Member
Posts:10


--
11/22/2006 5:22 AM

    Hello,

    I have DNN 4.3.6 running and have installed the latest version of DMX. All seems to work well, even indexing. But, I get an error every time I try to edit the categories.

    A critical error has occurred.
    Object reference not set to an instance of an object.

    Any idea what this means and how I can go about fixing this?

    Regards,
    Christopher

    cstimpson
    New Member
    New Member
    Posts:10


    --
    11/22/2006 4:10 PM
    Follow-up.

    I didn't think to mention that the above error comes from a client browser. When I am on the physical machine I have no errors. All other clients have the error. I am not sure how to turn on verbose errors in the config file. I will work on getting that.

    Regards,
    Christopher
    Peter Donker
    Veteran Member
    Veteran Member
    Posts:4536


    --
    11/23/2006 9:31 PM
    Christopher,
    I'm not sure where to look for the cause of this. Note that the solution uses a fair bit of javascript to function.
    Peter
    gregstout
    New Member
    New Member
    Posts:2


    --
    11/25/2006 8:00 AM
    I am having the same problem with 4.0. when I try to edit the categories
    Peter Donker
    Veteran Member
    Veteran Member
    Posts:4536


    --
    11/29/2006 10:32 AM
    I've identified the issue with DNN 04.00.03. In DNN 04.03.06 I have been unable to reproduce this error using DMX 03.04.08.
    Laverne Douglas
    New Member
    New Member
    Posts:47


    --
    11/29/2006 10:14 PM
    Peter: I am currently using DMX 03.04.07. Does DMX 03.04.08 work on DNN 4.3.5?
    Peter Donker
    Veteran Member
    Veteran Member
    Posts:4536


    --
    11/29/2006 11:52 PM
    It sure does.
    cstimpson
    New Member
    New Member
    Posts:10


    --
    12/05/2006 10:42 PM

    I have been trying to figure this out for some time. Here is the inner stack trace for the error initially presented. Any thoughts?

     

    Christopher Stimpson

    cstimpson
    New Member
    New Member
    Posts:10


    --
    12/05/2006 10:43 PM
    Posted By Christopher Stimpson on 12/05/2006 22:42:10

    I have been trying to figure this out for some time. Here is the inner stack trace for the error initially presented. Any thoughts?

     

    Christopher Stimpson



    DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Bring2mind.DNN.Modules.DMX.Controls.Admin.Categories.c(Object A_0, EventArgs A_1) at System.EventHandler.Invoke(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
    gregstout
    New Member
    New Member
    Posts:2


    --
    12/06/2006 12:21 AM
    As Peter said, he was able to identify the problem in DNN 4.0.3 and was able to fix it.  I can confirm that it works now in 4.0.3.  Doesn't help you, sorry, but it might help others with 4.0.3.
    Peter Donker
    Veteran Member
    Veteran Member
    Posts:4536


    --
    12/06/2006 9:29 AM
    Christopher,
    If you want you can try the 4.0.3 patch to make sure it wasn't that (contact me by email to get that patch). But I'm skeptical it was that as I believe the fix I applied only concerned 4.0.3. Otherwise I'm in the dark about your error. I can't seem to reproduce it here.
    Peter
    You are not authorized to post a reply.