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 ...Loading Default.aspx after successful installLoading Default.aspx after successful install
Previous
 
Next
New Post
1/8/2008 6:09 PM
 

I am getting this error when opening the default.aspx page. Please help !!!

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) +198
   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

Server Error in '/' Application.

Value cannot be null.
Parameter name: path1

 

 
New Post
1/8/2008 6:19 PM
Accepted Answer 

It's because of the Active Directory provider. If you aren't using it, don't need to use it, aren't planning on using it then open up your web.config and comment out all lines that start with <add name="Authentication".... /> under <httpModules>. If you are planning on using it then read this post http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/89/threadid/194161/scope/posts/Default.aspx for information on getting a beta replacement of the provider.

 
New Post
1/15/2008 10:53 AM
 

I had the same problem, and this is exactly the thing that fixed it.  It was the first time I ever selected Active Directory authentication on an install, so it had never occurred for me before.  Thanks for hitting the nail on the head and for the link.

 

 
New Post
1/17/2008 10:06 AM
 

That may fix it, if you needn´t the ad provider. But what´s the solution, if you need it?

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Loading Default.aspx after successful installLoading Default.aspx after successful install


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