object reference error install 4.4 VWD!

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

Home All Forums

Home

Getting Started

Installing DNN ...

object reference error install 4.4 VWD!

8/24/2006 12:24 PM

Gail T

Joined: 4/6/2005

Posts: 13

object reference error install 4.4 VWD!

I keep getting an object reference not set to instance of an object when trying create a new DNN site. I can build the Site in VWD, but when it runs the default page to do the install it dies after the configuring superuser then i get the object error (see below).
My DB gets created just fine so far as i can tell.
I had an error like this a few months ago, I remember finding something to the effect that the install was basically timing out. I can't remember what i did to correct it. I remember reading something about changing the mode=?? i forgot what to change it too. If that is even correct.
Any ideas?
Thanks!!
......
00:00:07.343 - Performing General Upgrades
00:00:07.781 - Loading Host Settings:
00:00:07.828 - Configuring SuperUser:

Server Error in '/DotNetNuke Website1' 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.Entities.Users.UserInfo.get_Membership() +62
   DotNetNuke.Services.Upgrade.Upgrade.ParseSuperUser(XmlNode node) +242
   DotNetNuke.Services.Upgrade.Upgrade.InstallDNN(String strProviderPath) +1184
   DotNetNuke.Framework.Install.InstallApplication() +1183
   DotNetNuke.Framework.Install.Page_Load(Object sender, EventArgs e) +280
   System.Web.UI.Control.OnLoad(EventArgs e) +80
   System.Web.UI.Control.LoadRecursive() +49
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3749

Version Information: Microsoft .NET Framework Version

Page 1 of 1