Upgrade from dnn 5.6.7 to dnn 6.1.3 eror when login
Last Post 04/27/2012 2:25 PM by Joseph Craig. 1 Replies.
Author Messages
andriama yanto
Nuke Newbie
Nuke Newbie
Posts:1


--
04/26/2012 2:35 AM
    please help if to know error about this message below?!








    Server Error in '/' Application.
    Object reference not set to an instance of an object.
    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.NullReferenceException: Object reference not set to an instance of an object.

    Source Error:

    The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

    1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

    <%@ Page Language="C#" Debug="true" %>

    or:

    2) Add the following section to the configuration file of your application:







    Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

    Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

    Stack Trace:

    [NullReferenceException: Object reference not set to an instance of an object.]
    DotNetNuke.UI.Containers.ActionBase.get_ModuleContext() +10
    DotNetNuke.UI.Containers.ActionBase.OnLoad(EventArgs e) +82

    [ModuleLoadException: An error has occurred.]
    DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, Control ctrl, Exception exc, Boolean DisplayErrorMessage) +361

    [PageLoadException: An error has occurred.]
    DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +558
    DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, Control ctrl, Exception exc, Boolean DisplayErrorMessage) +1045
    DotNetNuke.UI.Containers.ActionBase.OnLoad(EventArgs e) +350
    DotNetNuke.UI.WebControls.SolPartActions.OnLoad(EventArgs e) +16
    System.Web.UI.Control.LoadRecursive() +71
    System.Web.UI.Control.LoadRecursive() +190
    System.Web.UI.Control.LoadRecursive() +190
    System.Web.UI.Control.LoadRecursive() +190
    System.Web.UI.Control.LoadRecursive() +190
    System.Web.UI.Control.LoadRecursive() +190
    System.Web.UI.Control.LoadRecursive() +190
    System.Web.UI.Control.LoadRecursive() +190
    System.Web.UI.Control.LoadRecursive() +190
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3064

    [PageLoadException: An error has occurred.]
    DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +558
    System.Web.UI.Page.HandleError(Exception e) +182
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +11439478
    System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +11439006
    System.Web.UI.Page.ProcessRequest() +269
    System.Web.UI.Page.ProcessRequest(HttpContext context) +167
    ASP.default_aspx.ProcessRequest(HttpContext context) in c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\441c83cf\1d96321e\App_Web_yvuiswqe.7.cs:0
    System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +625
    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +270


    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272
    Joseph Craig
    DNN MVP
    Posts:11667


    --
    04/27/2012 2:25 PM
    Because of the reference to Containers in the first few lines, it may be that the containers you are using are causing the problem.

    Temporarily rename the folders that contain the Containers and Skin that you are using. This will force the site to load using the default skin and containers. If that happens, it also tells you that the skin or containers have a problem, so you can set about trying to fix that. (Often, this requires only minor modifications to containers. We can deal with that when you get to the point that the site will load, even if it has the wrong skin. Attaching a copy of one of the container .ascx files to a post will let me look at it.)

    Joe Craig, Patapsco Research Group
    Complete DNN Support


    ---