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 ...The type initializer for The type initializer for 'DotNetNuke.Data.DataProvider' threw an exception.
Previous
 
Next
New Post
1/13/2008 9:18 AM
 

Hi,

I've managed to get v.04.06.02 installed now, but starting it up is still a problem.

Am getting the following error:

DotNetNuke

DotNetNuke Error: - Version 04.06.02


The type initializer for 'DotNetNuke.Data.DataProvider' threw an exception.

Thanks for any help ...

 
New Post
7/9/2008 6:36 AM
 

hi, did you find the solution to that prob.?

 

i'm building a provider, i'm using the dlls of Dotnetnuke, i copied all of them into my bin, and it's giving me the same exception when calling the function getPortals from the dll. "The type initializer for 'DotNetNuke.Data.DataProvider' threw an exception."

Any idea what i shall do? thanks

 
New Post
7/27/2008 3:34 PM
 

This is a very common problem as I have also found, and extremely frustrating as it seems no-one has identified a reason,at least none that I could find.

I have encountered this error frequently when doing upgrades, even when following the recommended procedures. The cause is most likely a conflicting dll when the site is first loaded. A problem with loading the dlls in the bin causes some to not load, including the base DNN DataProvider dll. As this is required on the opening page it causes a total site failure.

What I found worked was the following procedure - note that this works when doing an upgrade but the principle still applies to other scenarious when a page is asked to load.

  1. Delete everything in the \bin directory of the destination site. (scary but necessary, make sure you have a copy of everything first)
  2. Copy the contents of the bin directory of the version of DNN that should be running, for example C:\DotNetNuke\Version4.6.2\DotNetNuke_04.06.02_Install\Bin
  3. Now run the site. When doing a site upgrade this will allow the site upgrade process to proceed. Hopefully it will load after the upgrade process even though it might look funny.
  4. Now copy the dlls for the modules that are registered into the bin of your destination site. See that the site still loads up.
  5. Now copy the dlls for any other tools that you need, one at a time. Check each time.

By doing the gradual approach you may be able to find which dll causes a conflict and work out a resoution for that one.

HTH.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...The type initializer for 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