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 ...Installing Fresh in old DBInstalling Fresh in old DB
Previous
 
Next
New Post
11/11/2006 7:53 PM
 
I'm trying to install a fresh version of DNN into a database with old data; DNN tables and such.

I set an object qualifier for the fresh version so that it would try to use new tables/procedures.

When I loaded the page, it said that there was nothing to upgrade, and stopped. Now I am unable to get DNN installed with the objectqualifer so I can not destroy the old data.

Is there a way to get a fresh version to install in a DB where a previous version was without destroying the previous data?

 
New Post
11/18/2006 10:44 AM
 

I have also tried this (on 4.3.5) using an objectqualifier with the same outcome.  I connected to the database via visual studio and found that only the versions table had been created, having the qualifier, and all versions were represented in it.  I performed 'delete from mynew_versions' which left it empty, and browsed again to the site; this time it went thru a full install, creating tables and procs etc with the qualifier.  However i think there must be a bug in the installation because it fell at the last hurdle: could not create a user as one already existed : please register under another name.

it failed to create users and portals, and so when i then tried to access the site, i continue to get the error message, object reference not set to an instance of an object, which i interprete as to do with the lack of users and portals in the mynew_portals and mynew_users tables.

Not sure how to fix this.  Any one else?

 
New Post
2/7/2009 11:32 AM
 

2 years later I can answer my own question!

The error about user already exists is due to the file webroot, install\dotnetnuke.install.config containing the instructions for creating the new portal and users, which in dotnetnuke have to be unique across objectqualified versions of the installation - because all installations use aspnet_membership etc which do not distinguish between separate installations.

See http://www.mitchelsellers.com/forums/forumid/2/postid/1429/view/topic.aspx where this is described in detail.

There was also on upgrade to 4.9.1 an omitted {objectqualifier} reference in the dotnetnuke.schema.sqldataprovider script , which caused a failure on setting up a database constraint which because of the missing objectqualifier was pointing at the wrong object.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installing Fresh in old DBInstalling Fresh in old DB


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