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

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationInstalling ProviderInstalling Provider
Previous
 
Next
New Post
12/27/2007 3:45 PM
 

I was having problems installing a clean version of DNN 040800 and thought it was at first maybe the installer wizard. I come to find out that the error i will post later happens when i actually add the AD Provider 1.0.0. Initially i had chosen to select it with a custom install. The site never even comes up. When i do a typical, it works just fine. I add the provider and same problem.

 

Server Error in '/Intranet' Application.

Value cannot be null.
Parameter name: path1

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.ArgumentNullException: Value cannot be null.
Parameter name: path1

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:

[ArgumentNullException: Value cannot be null.
Parameter name: path1]
System.IO.Path.Combine(String path1, String path2) +2686595
DotNetNuke.UI.Skins.SkinDefaults..ctor(SkinDefaultType DefaultType) +127
DotNetNuke.Common.Globals.get_DefaultSkin() +31
DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +2812
DotNetNuke.Common.Globals.GetHostPortalSettings() +216
DotNetNuke.Common.Globals.GetPortalSettings() +79
DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule.Init(HttpApplication application) +213
System.Web.HttpApplication.InitModulesCommon() +66
System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers) +814
System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context) +243
System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +106
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +340

I would really appreciate any help I can get on this.

 
New Post
12/27/2007 4:10 PM
 

When you installed the provider did it show any errors or did this error show up immediately?

 
New Post
12/27/2007 4:22 PM
 

It didnt show up immediately. It showed that the provider had succesfully installed. I got the error as soon as I clicked return.

I was just able to at least get the site working again by commenting out in web.config the last key:

    <httpModules>
      <!-- add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" / -->
      <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
      <add name="Compression" type="DotNetNuke.HttpModules.Compression.CompressionModule, DotNetNuke.HttpModules" />
      <add name="RequestFilter" type="DotNetNuke.HttpModules.RequestFilter.RequestFilterModule, DotNetNuke.HttpModules" />
      <add name="UrlRewrite" type="DotNetNuke.HttpModules.UrlRewriteModule, DotNetNuke.HttpModules" />
      <add name="Exception" type="DotNetNuke.HttpModules.Exceptions.ExceptionModule, DotNetNuke.HttpModules" />
      <add name="UsersOnline" type="DotNetNuke.HttpModules.UsersOnline.UsersOnlineModule, DotNetNuke.HttpModules" />
      <add name="DNNMembership" type="DotNetNuke.HttpModules.Membership.MembershipModule, DotNetNuke.HttpModules" />
      <add name="Personalization" type="DotNetNuke.HttpModules.Personalization.PersonalizationModule, DotNetNuke.HttpModules" />
      <!-- <add name="Authentication" type="DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule, DotNetNuke.Authentication.ActiveDirectory" /> -->
    </httpModules>

 
New Post
12/27/2007 5:32 PM
 

I just did a test on a 4.8 install and go the same error. I'll have to do some debugging and pass on the info to the Core Team.

 
New Post
12/27/2007 7:01 PM
 

I think I've found what's causing the problem and have logged it in Gemini http://support.dotnetnuke.com/Default.aspx?p=23&i=6901. However this means that you can't use the AD Provider with DNN 4.8.0.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationInstalling ProviderInstalling Provider


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