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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN 7.4.2 Adding a Portal issueDNN 7.4.2 Adding a Portal issue
Previous
 
Next
New Post
4/6/2016 3:22 PM
 

We used to have 243 portals in one DNN instance.  These have been split into separate DNN instances by client.  They all still go to the same database however.

When I go to add a portal to one of the instances, it all appears to work OK until the end.  Then I get an 'Object Reference not set to an instance of an object' error.

When I look in the database all the settings for the new portal are there and they are complete when compared to an existing portal.

The portal does NOT appear in Site Management when logged in as Host and when I navigate to the portal URL I get the following error:

[NullReferenceException: Object reference not set to an instance of an object.]
   DotNetNuke.HttpModules.UrlRewrite.BasicUrlRewriter.RewriteUrl(Object sender, EventArgs e) +2391
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +91
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +164

This is also shown in the Event Log for DNN

What setting do I need to change to get this to work.  We need to add portals on a weekly basis almost and this is making things difficult to say the least.

Any help would be appreciated.

 
New Post
4/6/2016 3:48 PM
 
Full Disclosure - I don't know the answer. However I have a guess.

I would think that what you are doing is the logical equivalent of setting up a web farm - multiple instances of DNN with shared DB. IIRC that is only supported by the paid for editions. I don't know how the paid for editions are different in this area.

I suggest that you instead do complete separation. Revert to the original unsplit configuration. Close that instance to new portals. Create a brand new DNN install with its own DB. Start using that new instance for future portals.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
4/6/2016 6:21 PM
 
there is NO support for multiple DNN instances sharing a database (besides using objectQualifier, which used to work properly in DNN 1 and 2 only).
If you separate portals from a DNN installation, you need to clone the database as well and remove the unused portals from each clone.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/13/2016 6:02 PM
 

I have broken up the database as well and each DNN instance now has it's own database.  I have removed the other portals from each instance.

I am still getting the same error when I go to add a site.

It doesn't appear in the Site Management list, however, it IS in the database and the folder is created in Portals.

I believe it may have something to do with the URLRewriter component mentioned in the error message - but I have no idea where to go with that.

 
New Post
4/14/2016 4:50 AM
 
could you please provide full stack trace from dnn Eventlog, thanks.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN 7.4.2 Adding a Portal issueDNN 7.4.2 Adding a Portal 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