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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade issue from 4.0 to 4.3.3Upgrade issue from 4.0 to 4.3.3
Previous
 
Next
New Post
7/24/2006 2:13 PM
 

I am trying to upgrade from 4.0.0 to 4.3.3. I configured the web.config file and uploaded. The site comes up fine. However, when i try to log in I get this error. I am not exactly sure what the problem is. Can anyone help.

P.S. Sorry for the length of this post.

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.Membership.AspNetMembershipProvider.UserLogin(Int32 portalId, String username, String password, String verificationCode, UserLoginStatus& loginStatus) +82
   DotNetNuke.Entities.Users.UserController.ValidateUser(Int32 portalId, String Username, String Password, String VerificationCode, String PortalName, String IP, UserLoginStatus& loginStatus) +41
   DotNetNuke.Modules.Admin.Security.Signin.cmdLogin_Click(Object sender, EventArgs e) +228
   System.Web.UI.WebControls.Button.OnClick(EventArgs e) +105
   System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +107
   System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7
   System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11
   System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +174
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5102

[PageLoadException: Object reference not set to an instance of an object.]
   DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +354
   DotNetNuke.Framework.PageBase.Page_Error(Object Source, EventArgs e) +377
   System.Web.UI.TemplateControl.OnError(EventArgs e) +105
   System.Web.UI.Page.HandleError(Exception e) +73
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6944
   System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +154
   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() +154
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64


Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

 
New Post
8/4/2006 6:09 AM
 
Did you ever find a solution to this problem? I have the same issue upgrading from 3.3.2 to 3.3.4.
 
New Post
8/23/2006 11:26 PM
 

I am experiencing the same issue going from a 3.2.2 install to a 4.3.4.

The upgrade didn't report any errors and I can actually get to the portal but just can't log in.

If I find the solution I will post my findings.


Shawn W Knight
www.knightshawn.com
DNN Module Development and other stuff
 
New Post
8/24/2006 10:40 PM
 

Well after many hours of digging, I finally came across this post-

http://dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/63243/threadpage/1/scope/posts/Default.aspx

BlueFrog's solution works like a charm.

Once I performed the operation and realized what it does, it all kind of makes sense now.

I hope this helps.


Shawn W Knight
www.knightshawn.com
DNN Module Development and other stuff
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade issue from 4.0 to 4.3.3Upgrade issue from 4.0 to 4.3.3


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