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 ...My Default.aspx file came out to thisMy Default.aspx file came out to this
Previous
 
Next
New Post
2/8/2008 6:00 PM
 

Everything in the install process went through just fine.  When I finished it went to the "Default.aspx" I got this.

Server Error in '/DotNetNuke_2' 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) +2717803
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.InitModules() +267
System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers) +1251
System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context) +243
System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +106
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +214


Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

 
New Post
2/9/2008 11:40 AM
 

Please see the following forum thread:

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/89/threadid/192745/scope/posts/Default.aspx

Also look at Mike Horton's blog on Authentication Providers for recent updates/workaround for the situation.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
2/14/2008 1:36 PM
 

Ok I fallowed the link and finally came to a fix.  How do I apply the fix? Besides the fix is there a way to just turn off AD authentication?  I dont care to use if its necessary. The message says to edit this code but where is it? Should I just re-install the entire application without AD support or can I go back un-install this service.

 

"This was a change required in order to support IIS7 "Integrated Pipeline" mode.

The 4.8.0 code has been nmodified so that most of the "App Start" code occurs on the first request - instead of in Application Start.  This is because there is no Request object until "Begin Request" when using Integrated Pipeline.

This means that there is no gurantee that the portal has completed its initialisation - until BeginRequest.

I therefore suggest the following (especially as the Init code in the provider uses the request object and would fail in IIS7 IP mode as well).

Modify the Init method to the following:

        Public Sub Init(ByVal application As HttpApplication) Implements IHttpModule.Init
                AddHandler application.AuthenticateRequest, AddressOf Me.OnAuthenticateRequest
        End Sub

Move the code that checks for the cookie to the beginning of OnAutheticateRequest, as follows

            'Cookies have to be enabled or DNN goes into infinite loop
            If Request.ServerVariables("HTTP_COOKIE") = "" Then
                Exit Sub
            End If

I am not sure why the rest of the code is there - but this may need to be moved to OnBeginRequest - if it is the method would need to include a call to Initialize.Init() to ensure that the startup code is run before accessing the portal settings. "

 
New Post
2/14/2008 3:22 PM
 

If you don't want to use the AD Provider then just comment out all the <add name="Authentication".... /> lines in the <httpModules> section of your web.config.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...My Default.aspx file came out to thisMy Default.aspx file came out to this


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