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 to 4.3.3 failureUpgrade to 4.3.3 failure
Previous
 
Next
New Post
7/25/2006 12:30 PM
 

Did a normal upgrade from 4.0.2 to 4.3.3 and everything looked just fine during the install process.  When I first access the site though, all I get is the following error.  Any ideas?  I have taken care of a bunch of issues before, but this one has me stumped.

 

Server Error in '/DotNetNuke' 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:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]
   DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectProviderName, String ObjectNamespace, String ObjectAssemblyName, Boolean UseCache) +465
   DotNetNuke.Security.Membership.MembershipProvider.CreateProvider() +38
   DotNetNuke.Security.Membership.MembershipProvider..cctor() +13

[TypeInitializationException: The type initializer for 'DotNetNuke.Security.Membership.MembershipProvider' threw an exception.]
   DotNetNuke.Security.Membership.MembershipProvider.Instance() +0
   DotNetNuke.Entities.Users.UserController..cctor() +5

[TypeInitializationException: The type initializer for 'DotNetNuke.Entities.Users.UserController' threw an exception.]
   DotNetNuke.Entities.Users.UserController.GetCurrentUserInfo() +0
   DotNetNuke.Services.Exceptions.BasePortalException.InitilizePrivateVariables() +245


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

 
New Post
8/7/2006 11:48 AM
 
I'm getting the exact same results. Any idea how to fix this problem?
 
New Post
8/7/2006 5:20 PM
 

I got this exact same error.

My history is this . .

My original DNN install was DNN 3.1.1 then I upgraded to DNN 4.0.3

This upgrade was significant because it pulled me off the .Net 1.1 framework into the .Net 2.0 framework.

I was very happy and very suprised it worked !  (I had a few errors but nothing significant)

 But then I got greedy and thought "Hey, what's a small upgrade to DNN 4.3.4 be ?"

I don't know where to start.  Any ideas ?

 
New Post
8/8/2006 12:14 PM
 

Update !

I got it work.  I guess the release.config is different from v4.0.3 to v4.3.4

Since the upgrade to v4.3.4 didn't copy over a new web.config nothing was changed.

Therefore, the web.config for v4.0.3 was not touched or re-written.

At this point I was getting the error . . . then I *GASP* followed directions and copied over the release.config from the v4.3.4

and updated it with my DB Connection String as well as the Machine Key and Install Key.

I recycled the application pool (ASP.NET V2.0), stopped and restarted IIS.

And  . .voila . .it came up.

I pulled up my ExamDiff and compaired the release.config between v4.0.3 and v4.3.4 and there is a big difference.

Anyways, this helped for me.

 

 
New Post
8/15/2006 5:55 PM
 
I'm getting the exact same error!  I've upgraded from 3.2.2 to 3.3.4 and go this.  I've tried locotx's trick by updating the SireSqlServer, MachineValidationKey, and MachineDecryptionKey values in my release.config file, but I still get the error.  I'm running the site on ASP.NET v1.x, and I'm with a hosting company.  I have the ability to "bounce" the site under my Plesk control panel, but I'm not sure if that re-initializes the site properly.  Thoguhts? (BTW, I'm still getting the error: http://www.chewbode.com)
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade to 4.3.3 failureUpgrade to 4.3.3 failure


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