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 Questions - 4.02 to 4.34Upgrade Questions - 4.02 to 4.34
Previous
 
Next
New Post
8/8/2006 3:42 PM
 
Hi, thanks - here is what I get after turning customErrors off:
 

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
 
New Post
8/8/2006 10:47 PM
 

As your site is on shared hosting, I'm assuming that you are using the Install version of DNN for both the original 4.0.2 install and the 4.3.4 upgrade.  As there are some major changes between the release.config files of these two versions relating to the MembershipProviders, make certain that it you have used the release.config file from version 4.3.4 and not the one (or the web.config) from version 4.0.2 as the base to which you copied the SiteSQLServer connection strings, machinekeys, and objectQualifer values, that you then renamed the release.config to web.config, and that you uploaded the new web.config to the host server.  In your FTP client, check the date of web.config to confirm that it has been uploaded and that it is not the old one from the original install.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
8/8/2006 11:08 PM
 
Hi, I used the "Upgrade" version for 4.34, on top of the "Install" for 4.02, and for the web.config I modified the release.config from the 4.34 upgrade and renamed it web.config, then uploaded to the server.
 
Could the problem be that I used the upgrade version?
 
New Post
8/9/2006 11:13 PM
 
The upgrade would be the preferred method.  Out of curiosity I compared the release.config files of both the 4.3.4 Upgrade and the 4.3.4 Install and found no differences that would account for the error you are getting.  I'm still guessing that somehow the old web.config or release.config (from 4.0.2) was used rather than the release.config from the 4.3.4 Upgrade (or Install package).  Assuming that all of the files of the extracted Upgrade have been properly uploaded to the server, I would again start with release.config from the 4.3.4 Upgrade, modify it to include the values of the connection strings, machine keys, and (if used) objectQualifier from the old (4.0.2) web.config, rename the modified config file from release.config to web.config, upload it to the server, and then visit the site again.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade Questions - 4.02 to 4.34Upgrade Questions - 4.02 to 4.34


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