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 ...Server Error in Server Error in '/DotNetNuke Website2' Application.
Previous
 
Next
New Post
1/5/2006 10:28 AM
 

Hi. I had this error when installing DNN 4.0.2 . Can anyone help me on this?  Also, my email is p7gray@hotmail.com. Thanks.

Server Error in '/DotNetNuke Website2' 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.Common.Utilities.Config.GetConnectionString(String name) +49
   DotNetNuke.Data.SqlDataProvider..ctor() +126

[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) +233
   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() +331
   DotNetNuke.Common.Global.CheckVersion() +188
   DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E) +322


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

 
New Post
1/5/2006 3:28 PM
 
This error is caused by an incompatability between the DotNetNuke core and the SQLDataprovider assembly.  Rebuild the solution and make sure that both the DotNetNuke dll and the SqlDataProvider are rebuilt.

Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here
MVP (ASP.NET) and
ASPInsiders Member
View my profile on LinkedIn
 
New Post
1/5/2006 6:35 PM
 
Ok. I had this SAME problem. I fixed it though, because I noticed something. The "Object reference not set to an instance of an object." means that the object it's refering to is missing. If you pick through, you'll find that you most likely didn't copy the SiteUrls.Config file from your /Config/ folder in the root of the project.

Copy that over and you should be all set.
 
New Post
1/29/2006 11:54 PM
 

Copying SiteUrls.config solved my problem too.

I wonder why it is not doen by the installer itself??

Regards

Jerzy,

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Server Error in Server Error in '/DotNetNuke Website2' Application.


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