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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Error: Event Viewer is currently unavailable.Error: Event Viewer is currently unavailable.
Previous
 
Next
New Post
6/23/2008 3:35 PM
 

Cathal,

I modified my web.config file based on the development.config.file.  Now my errors are as follows:

Error: Event Viewer is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: The type initializer for 'DotNetNuke.Services.Log.EventLog.LoggingProvider' threw an exception. ---> System.TypeInitializationException: The type initializer for 'DotNetNuke.Services.Log.EventLog.LoggingProvider' threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectProviderName, String ObjectNamespace, String ObjectAssemblyName, Boolean UseCache) at DotNetNuke.Services.Log.EventLog.LoggingProvider.CreateProvider() at DotNetNuke.Services.Log.EventLog.LoggingProvider..cctor() --- End of inner exception stack trace --- at DotNetNuke.Services.Log.EventLog.LogController.AddLog(LogInfo objLogInfo) --- End of inner exception stack trace ---

Unhandled error loading module.
DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled Error Adding Module to ContentPane ---> System.TypeInitializationException: The type initializer for 'DotNetNuke.Services.Log.EventLog.LoggingProvider' threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectProviderName, String ObjectNamespace, String ObjectAssemblyName, Boolean UseCache) at DotNetNuke.Services.Log.EventLog.LoggingProvider.CreateProvider() at DotNetNuke.Services.Log.EventLog.LoggingProvider..cctor() --- End of inner exception stack trace --- at DotNetNuke.Services.Log.EventLog.LogController.GetLogTypeInfo() at DotNetNuke.Modules.Admin.Log.LogViewer.Page_Init(Object sender, EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.UserControl.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at System.Web.UI.ControlCollection.Add(Control child) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

 
New Post
6/23/2008 6:31 PM
 

 

Please check your web.config again, and ensure you've copied all the 4.8.4 files over your existing install, the error shows that it cannot create the correct provider. The 2 relevant web.config nodes should look like this:

<section name="logging" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>

 

  <logging
    defaultProvider="DBLoggingProvider">
   <providers>
    <clear/>
    <add
      name="XMLLoggingProvider"
      type="DotNetNuke.Services.Log.EventLog.XMLLoggingProvider, DotNetNuke.XMLLoggingProvider"
      configfilename="LogConfig.xml.resources"
      providerPath="~\Providers\LoggingProviders\XMLLoggingProvider\"/>
    <add
      name="DBLoggingProvider"
      type="DotNetNuke.Services.Log.EventLog.DBLoggingProvider.DBLoggingProvider, DotNetNuke.Provider.DBLoggingProvider"
      providerPath="~\Providers\LoggingProviders\Provider.DBLoggingProvider\"/>
   </providers>
  </logging>


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
6/23/2008 7:13 PM
Accepted Answer 

Can I suggest that you look at what dotnetnuke.* files you have in your installation?  because you upgraded from 3.x to 4.8.x, you've probably still got a lot of httphandler dlls from back when the handlers were all separate DLLs.  You might want to archive all the dotnetnuke.* files from your bin directory, then copy in the new 4.8.x versions.   You'll need to keep any module-specific versions.

That's what I would expect from your problem - the type initialiser is picking up the wrong DLL version, and matching perhaps the namespace but not the DLL name.

Just a guess though!

 
New Post
6/24/2008 2:44 PM
 

Thanks everyone.  I was at a total lost.

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Error: Event Viewer is currently unavailable.Error: Event Viewer is currently unavailable.


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