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 ...Problem on First Run of DNNProblem on First Run of DNN
Previous
 
Next
New Post
9/10/2012 9:15 AM
 

Hi Folks,

I am hoping someone has seen this before.  I download the latest DNN install package and installed it on my development machine - Windows Server 2008/ II 7.0/SQL Server 2008.  The "Auto" install went fine (note, I modified the two connection strings in the web.config to point to an empty DNN databaes I created in my local SQL Server 2008) and I see no errors in the install process.  However, when I click the link at the bottom of the page to go to launch DNN for the first time I get the following error after a few moments:

===================================================================

Server Error in '/HIPOMDNN' Application.

Unable to load default file registration provider

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.Configuration.Provider.ProviderException: Unable to load default file registration provider

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:

[ProviderException: Unable to load default file registration provider] ClientDependency.Core.Config.ClientDependencySettings.LoadProviders(ClientDependencySection section, HttpContextBase http) +2789 ClientDependency.Core.Config.ClientDependencySettings..ctor() +298 ClientDependency.Core.Config.ClientDependencySettings.get_Instance() +211 ClientDependency.Core.Module.ClientDependencyModule.LoadFilterTypes() +68 ClientDependency.Core.Module.ClientDependencyModule.System.Web.IHttpModule.Init(HttpApplication app) +134 System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +575 System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +352 System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +407 System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +375 [HttpException (0x80004005): Unable to load default file registration provider] System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +11700512 System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +141 System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +4868709 

 


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.276 

 ============================================================================

Note that I only have the one "clientDependency" section in my web.config file (see Configuration section below).  Am I suppose to have more??

Note that DNN is installed under the Default Web Sites in IIS as an Application, and the application is running under a .Net 4.0 AppPool with identity NetworkService, and I have given NetworkService Full access to the root of the physical path of the DNN site.  The fact that the intial install worked fine would seem to suggest that IIS is happy, however.

Really stumped on this.  Does anyone know what the problem is?

Thanks,
Rod

<configSections>
    <sectionGroup name="dotnetnuke">
      <!-- the requirePermission attribute will cause a syntax warning - please ignore - it is required for Medium Trust support-->
      <section name="data" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="logging" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="scheduling" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="htmlEditor" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="navigationControl" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="searchIndex" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="searchDataStore" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="friendlyUrl" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="caching" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="authentication" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="members" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="roles" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="profiles" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="permissions" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="moduleCaching" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="outputCaching" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="folder" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="clientcapability" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
      <section name="sitemap" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
    </sectionGroup>
    <section name="clientDependency" type="ClientDependency.Core.Config.ClientDependencySection, ClientDependency.Core" requirePermission="false" />
  </configSections>

 

 
New Post
9/10/2012 9:58 AM
 

UPDATE:

I tried switching to a .NET 2.0 AppPool and relaunch the site but that just to other different errors.

So I decided to repeat the etnire exercise above again (I had already tried it multiple times) using a .NET 2.0 AppPool from the begining instead of a .NET 4.0 AppPool.  That is - run the entire "install process" with a .NET 2.0 AppPool.

This time evreything installed fine as belfore, and I was able to launch the DNN site for the first time.   I noted that there were now many refernces to "clientDependency" in my web.config rather than just the one I had before.

Then I decided to shutdown the AppPool and switch it to .Net 4.0 and restart it, and then relauch my DNN site.  The site came up fine.

So in summary, it would appear that DNN has to be "installed" under an AppPool of 2.0 but can then later be switched to run under a .NET 4.0 AppPool.

Hope this helps someone else!

Rod

 
New Post
9/11/2012 4:53 AM
 
Hi Rod,
I have no issues installing DNN 6 websites on ASP.Net 4.0 application pools in integrated mode. Be aware, that switching asp.net version might require running a merge script in configuration manager to adopt web.config settings.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Problem on First Run of DNNProblem on First Run of DNN


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