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 ...Brand new install failedBrand new install failed
Previous
 
Next
New Post
12/7/2007 6:29 PM
 

Hi,

I just installed Dotnetnuke 4.7 in two steps. Forst 4.3, then an upgrade. Reason, my provider supplied the 4.3 version in install, then i had to upgrade to 4.7. Once upgraded i get the following error:

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

I have no clue where to look since the message is not very clear about the real problem.

Thanks and regards,

Jerry

 
New Post
12/10/2007 11:38 AM
 

Did you set correct file permissions after you overwrote the files with the upgrade package?


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
12/28/2007 6:39 AM
 

I thought file permissions were set by the installation and upgrade process. Didn't set them explicitly.

I had to do a lot of the installation twice with rewritten scripts since i have troubles with the case-sensitivity issue which is spoken of in some of the other threads. Could this be it?

 

 
New Post
1/2/2008 2:49 PM
 

You do need to set the file permissions explicitly again with each upgrade.  Otherwise, DNN doesn't have access to the files (and, so, couldn't do anything in the install/upgrade process if it wanted to).  That exception seems to be the same that I am used to getting when I forget that step.

I don't have any experience with case-sensitivity issues, could you point to a thread that talks about it, if the above doesn't help?

Hope it helps,


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Brand new install failedBrand new install failed


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