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 ...DNN4 to DNN 481 The type initializer for DNN4 to DNN 481 The type initializer for 'DotNetNuke.Data.DataProvider' threw an exception
Previous
 
Next
New Post
6/21/2008 4:04 PM
 

I was very pleased for a momanet there when I finally won my battle with errors over installing DNN441 but then something hit me and I decided to go further to upgrade into 481, did everything as usually with web config and all then went to my site http://kotenok-gaf.ru/Install/Install.aspx

AND SURE  it was an error.... IF ANYONE KNOWS WHAT THE*** THIS MEANS you are so welcomed to comment

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.Common.Utilities.Config.GetConnectionString(String name) +47
   DotNetNuke.Common.Utilities.Config.GetConnectionString() +38
   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) +268
   System.Activator.CreateInstance(Type type, Boolean nonPublic) +66
   DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectProviderName, String ObjectNamespace, String ObjectAssemblyName, Boolean UseCache) +582
   DotNetNuke.Data.DataProvider.CreateProvider() +47
   DotNetNuke.Data.DataProvider..cctor() +13

[TypeInitializationException: The type initializer for 'DotNetNuke.Data.DataProvider' threw an exception.]
   DotNetNuke.Common.Globals.GetUpgradeStatus() +67
   DotNetNuke.Common.Initialize.CheckVersion(HttpApplication app) +147
   DotNetNuke.Common.Initialize.InitializeApp(HttpApplication app) +413
   DotNetNuke.Common.Initialize.Init(HttpApplication app) +125
   DotNetNuke.HttpModules.RequestFilter.RequestFilterModule.FilterRequest(Object sender, EventArgs e) +177
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

Server Error in '/' Application.

Object reference not set to an instance of an object.

 

 
New Post
6/22/2008 5:28 AM
 

GUUUUYS I know there are people out there who know how to fix this. please help !!!

 
New Post
6/22/2008 12:14 PM
 

anybody??

 right now I went back to DNN441 but it has the text/html module that does not work with this install.. what should I do I know if I upgrade I will have that error that I have shown ubove, and I don't want that since nobody  knows what is it and how to fix it, but I need to upgrade anyways I can't stay with 441 forever... what's the best bet for upgrading 441?

 
New Post
7/22/2008 10:50 PM
 

Hi Julia,

 

Did you find a solution to your problem.  I have just upgraded from 4.5.1 to 4.5.3 the install went OK but when I try to use my custom module its Dataprovider throws the Type Initializer exception.  I have been through the config file twice and checked that all the dll's are compiling.

Linda

 
New Post
7/23/2008 2:05 AM
 

I just fixed my problem with a change to the config file:

<trust level="Full" originUrl=".*" />

It was originally set to medium so I am slightly concerned about the consequences but after a day of pulling my hair out I am going to stick with it.

Hope this can help you too Julia.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN4 to DNN 481 The type initializer for DNN4 to DNN 481 The type initializer for 'DotNetNuke.Data.DataProvider' threw an exception


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