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...errors  upgrading 5.6.0 to 5.6.1errors upgrading 5.6.0 to 5.6.1
Previous
 
Next
New Post
2/9/2011 9:50 AM
 
Thanks Richard . . . the error you posted did include the stack trace. Here's the actual error:

Object reference not set to an instance of an object.at DotNetNuke.Services.Installer.XmlMerge.UpdateNode(XmlNode . . .

The last part of the Telerik install and of the other providers which gave error messages as well is to make modifications to the site's web.config file. Either access to web.config was denied due to insufficient file permissions for the ASP.Net worker process account on the site's root install folder or, more likely, a section of the web.config file is corrupted so that the XmlMerge method could not find the point at which to make the modification. If your web.config file uses a <location> . . .  </location> section wrapped around the <system.web> section, that can also be a cause of this issue.

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
3/11/2011 11:17 AM
 
Richard,

I've been trying to upgrade a 5.6.0 installation to 5.6.1 with the same failures trying to install Telrik 5.6.0, CoreSiteMapProvider and TelerikEditorProvider 5.6.1.

I've restored, reset permissions, made sure my download was good, everything that has worked in the past. Finally I thought maybe it was the we.config file, so I used a known good download of the 5.6.1 install, tweaked the web.config for the database location, machinekey and install date and uploaded the install.

Everything was installed properly, however after everything was installed, it tried to create the website and failed with a user already created. When I tried to go to the website, it said that the domain did not exist.

How do we use the full install to upgrade a website now?

Cheers

Dave

-----
Cheers
Dave
 
New Post
3/12/2011 7:39 AM
 
when using full install package for upgrading, make sure you are not overwriting existing web.config file or database.mdf inside app_data folder. If you did, please restore from a previous backup.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/12/2011 12:48 PM
 
Sebastian,

Don't I make the necessary changes to the web.config file? Does it just use the other one and tweak the appropriate changes automatically?

-----
Cheers
Dave
 
New Post
3/12/2011 12:49 PM
 
Oops, also, I'm not using the database.mdf file, I'm using a SQL server.

-----
Cheers
Dave
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...errors  upgrading 5.6.0 to 5.6.1errors upgrading 5.6.0 to 5.6.1


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