All of a sudden our production DNN 3.22 installation broke and we are no longer able to log in. The actual error we get is stated below. We haven't changed any settings except for some content being added here and there. The actual problem seems to be the portal calls the stored procedure "aspnet_Profile_GetProperties" and sends a "-1" as the applicationId, instead of "DotNetNuke". Looking through the aspnet tables, it looks like all our users are mapped to the applicationId of "DotNetNuke". The rest of the site works perfectly from a public, non-user aspect.
Has anyone experienced a portal just randomally changing this? How can we go about making the portal send the correct ApplicationID? Thanks!
Here is the exact error when we try to log in:
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:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
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.Security.Authentication.Configuration..ctor() +108
DotNetNuke.Security.Authentication.Configuration.GetConfig() +70
DotNetNuke.Security.Authentication.AuthenticationController..ctor() +37
DotNetNuke.Modules.Admin.Security.Signin.cmdLogin_Click(Object sender, EventArgs e) +1238
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +105
System.Web.UI.WebControls.Button.RaisePostBackEvent(String EVENT_ARGUMENT) +107
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String EVENT_ARGUMENT) +7
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String EVENT_ARGUMENT) +11
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +177
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1746
[PageLoadException: Object reference not set to an instance of an object.]
DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +368
DotNetNuke.Framework.PageBase.Page_Error(Object Source, EventArgs e) +377
System.Web.UI.TemplateControl.OnError(EventArgs e) +2085460
System.Web.UI.Page.HandleError(Exception e) +71
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +7341
System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +213
System.Web.UI.Page.ProcessRequest() +86
System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +18
System.Web.UI.Page.ProcessRequest(HttpContext context) +49
ASP.default_aspx.ProcessRequest(HttpContext context) +4
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +358
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64
|