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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade to 5.6 aok - But Default Domain Name IssueUpgrade to 5.6 aok - But Default Domain Name Issue
Previous
 
Next
New Post
11/23/2010 9:32 AM
 
I do not see the setting "runAllManagedModulesForAllRequests" in my web.config.
 
New Post
11/23/2010 9:40 AM
 
Jeremy.. Believe this is IIS 7.0 specific, so it won't be of any help for those with IIS 6.0

Well so my research says anyway..
 
New Post
11/23/2010 11:50 AM
 

I have resolved the issue, atleast for my sites, by recompiling the DotNetNuke.HttpModules.dll. Under UrlRewriteModule.vb I changed the following line:

If New PortalController().GetPortals().Count = 1 Then

to:

If New PortalController().GetPortals().Count >= 1 Then

The error occurs because the sub does not know the portal ID, the portalID is set to the host portalID via:
        'the domain name was not found so try using the host portal's first alias
        PortalId = Host.HostPortalID

If the portalID is not null then a PortalController returns the number of portals and only if there is 1 portal is the PortalAliasInfo object created and assigned to "objPortalAliasInfo". However my site has more portals so the PortalAliasInfo is never assigned.

So we leave this section of the sub and continue to an if statement block thats asks if the portalID is known (not -1). The portalID is now known because it was set above, however the PortalAliasInfo isn't known. A New PortalSettings object is created using the PortalAliasInfo that is not assigned which causes the exception.

I did run into an issue that was not existant on my 05.05.01 installation after resolving this issue. I run a web application using iframes through DNN and some of the pages are named similarly to my Friendly URL pages (home.aspx for example). If they have the same name the IFrame will now display the DNN page rather than my application's page. I worked around this by simply adding an underscore to my application's page's names.

 
New Post
11/23/2010 12:21 PM
 
RE: Errors generated when opening URL http://portalname (without default.aspx or home.aspx explicitely specified).
 
I  reported this issue right after 5.06 (Pro, trial) was released but so far no one has responded to me. Here is the error as I saw it:

Server Error in '/' Application.

Object reference not set to an instance of an object.

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.NullReferenceException: Object reference not set to an instance of an object.

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:

 

[NullReferenceException: Object reference not set to an instance of an object.]

   DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabID, PortalAliasInfo objPortalAliasInfo) +49

   DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +2332

   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +148

   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

 

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

This is running on a Windows Server 2003 machine, IIS 6.0, ASP.NET 4.0. This was a fresh install with no add-on skins or components. A side by side test with 5.05.01 (community) could not reproduce the error.

Ross
 
New Post
11/23/2010 2:35 PM
 
Expanding on my previous post:

After some testing I realized a portal alias was getting added for each folder of any file that would experience the exception, which I would consider less than desirable. I have no use for the alias addition so I just diabled it by commenting out the following lines in the same file as before:
 

'objPortalAliasController.AddPortalAlias(objPortalAliasInfo)
'If app.Request.Url.AbsoluteUri.StartsWith("https://", StringComparison.InvariantCultureIgnoreCase) Then
    'strURL = "https://" & objPortalAliasInfo.HTTPAlias.Replace("*.", "")
'Else
    'strURL = "http://" & objPortalAliasInfo.HTTPAlias.Replace("*.", "")
'End If
'Response.Redirect(app.Request.Url.ToString(), True)

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade to 5.6 aok - But Default Domain Name IssueUpgrade to 5.6 aok - But Default Domain Name Issue


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