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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Upgrading DNN production websiteUpgrading DNN production website
Previous
 
Next
New Post
3/9/2009 5:09 AM
 

Dear All

We  have a requirement to upgrade few of our production web sites with a new version(We are not upgrading DNN) with few bugfixes and some new features.
We are planning to make a installed shield program to server our need so that the it could be installed by the customer with minimum amount of fuss
To achieve this we have followed the following steps in a test environment
 
1.Backup the existing DB and the web config
2.Uninstalled the current website
3.Re-install the New  version of the Site
4.Restore the previous DB(So we get back all the existing module settings and of cause the users)
5.Merged the machine key validation key to the new webconfig
But unfortunately after following these steps we are not able to login to the system even as the admin or the super user and when i checked the log files
there is an exception bring raised as "DNN  user authentication Failed"  How can i solved this issue ??
or is there a better way of approching this upgrade
 
Thanks a lot
 
 
 
New Post
3/9/2009 12:06 PM
 

I'm not following what you are actually trying to do.

What are you upgrading if you aren't upgrading DNN?


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
3/10/2009 8:49 AM
 

ahm... i guess he has a different version of the website(with different contents) developed somewhere else and trying to install it  on the same version of the DNN perhaps? not sure.

Rasika, plz write the DNN version here. I would double check machine key (i know you did but just in case).

I would also try this: https://my.re-invent.com/helpdesk/KB/a210/how-do-i-reset-my-dotnetnuke-host-superuser-password.aspx

 
New Post
3/11/2009 1:11 AM
 

Let me just explain further what we are actually trying to do
Our website is kind of a portal which consists of Business modules for a debt collection company. These modules communicate with an API to get the business data. What we have done was we have fixed few bugs in the API as well as in the modules. So we want to update the production site's with those changes. Since installing these fixed modules and the changed api at the customer site involves manual work our ISV(independent software vendor) does not like this option because each time we fix a bug he has to manually install all the customer sites. That why we thought of installing the whole site from the scratch and restore the old DB to get back all the settings and the users

If there is a smarter way to do this please let us know??


The DNN version that we are using is 04.08.00

Thanks

 

 
New Post
3/11/2009 12:24 PM
 

if you are simply changing the api and some modules then why do you have to reinstall the whole site - just update the changed files - I assume you are not changing the DB structure so you only need to over write the changed dll's and aspx files - this leaves all you content and user base intact.

This is the procedure that I use (my framework is not identical to dnn framework) I only have to upload the changes as I am not actually updating the dnn version. No matter which way you go you will still have to upload the changes to all clients any way - you could make that process automatic with an install program but you will still have to upload the changes and run the install on each client.

Basically you are updating the version on the client site (not the dnn version but your own) so just write an install script to do it . I assume that if you are changing the DB structure then you would have sql scripts to do this any way.

You could follow the auto module installation setup built into dnn - modify it so that if there is any thing in say install/updates directory then the site will automatically run them - in this case you would only have to upload the changes to each client and place them into the install/update directory - the scheduler would look after the rest.

Probably also a good idea to carry your changes thro to 4.9.2 and use that as your base framework rather then 4.8.0.

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Upgrading DNN production websiteUpgrading DNN production website


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