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 ...Object reference not set to an instance of an objectObject reference not set to an instance of an object
Previous
 
Next
New Post
2/20/2007 12:40 AM
 

I am doing an installation for the first time.  I believe I followed the steps diligently.  When I actually open a browser to do the installtion  process, I get the following:

  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:

Line 73: 
Line 74:             'Determine the Upgrade status and redirect to Install.aspx
Line 75:             Select Case GetUpgradeStatus()
Line 76:                 Case Globals.UpgradeStatus.Install, Globals.UpgradeStatus.Upgrade
Line 77:                     If AutoUpgrade Then

Source File: c:\inetpub\wwwroot\dotnetnuke\website\App_Code\Global.asax.vb    Line: 75

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]
   DotNetNuke.Common.Utilities.Config.GetConnectionString(String name) +47
   DotNetNuke.Common.Utilities.Config.GetConnectionString() +78
   DotNetNuke.Data.SqlDataProvider..ctor() +83

[TargetInvocationException: Exception has been thrown by the target of an invocation.]
   System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck) +0
   System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache) +103
   System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache) +261
   System.Activator.CreateInstance(Type type, Boolean nonPublic) +66
   DotNetNuke.Framework.Reflection.CreateObject(String TypeName, String CacheKey, Boolean UseCache) +232
   DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectProviderName, String ObjectNamespace, String ObjectAssemblyName, Boolean UseCache) +571
   DotNetNuke.Data.DataProvider.CreateProvider() +39
   DotNetNuke.Data.DataProvider..cctor() +13

[TypeInitializationException: The type initializer for 'DotNetNuke.Data.DataProvider' threw an exception.]
   DotNetNuke.Common.Globals.GetUpgradeStatus() +67
   DotNetNuke.Common.Global.CheckVersion() in c:\inetpub\wwwroot\dotnetnuke\website\App_Code\Global.asax.vb:75
   DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E) in c:\inetpub\wwwroot\dotnetnuke\website\App_Code\Global.asax.vb:252

Server Error in '/' Application.

Object reference not set to an instance of an object.

 

 
New Post
2/20/2007 10:44 AM
 

I had this trouble when I was trying to install DNN in Vista Ultimate. Eventually I ditched it and went back to XP Pro as I could not fix it. Only to find that xp-pro was behaving exactly the same

My setup is this

xp pro servicepackII, IIS6, .net2, SQL 2005

I have now managed to get it to run, and the only thing extra I did that made it able to run was to go to SQL Server Configuration Manager and in SQL Server 2005 Services, ensure that all services are running. I did not have SQL Server Agent running.

Any how it is now working fine. So I assume it was the last thing I did. Having said that I dont have an explanation for this behaviour as I never had this issue on countless of installs on other servers.

Salar

 
New Post
2/20/2007 9:53 PM
 

I appreciate the help.

I got it figured out and I'm feeling pretty stupid.  I'm such a newbie that I didn't realize that the SiteSqlServer keys in <appSettings> and <connectionStrings> were commented out.  I was just following the installation steps verbatim and they didn't mention this change since the documentation.

Andy

 
New Post
3/5/2007 2:58 AM
 

My 2 pence:

I had this  problem when my IIS virtual dotnetnuke directory was 'looking' at the wrong directory (of an older dotnetnuke version) in my file system

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Object reference not set to an instance of an objectObject reference not set to an instance of an object


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