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 ...Upgrade to 3.3.3Upgrade to 3.3.3
Previous
 
Next
New Post
8/13/2006 6:06 AM
 

I have multiple DNN sites that I originally installed using 3.1.1 provided by the host - I have just upgraded one site successfully to 3.3.3 without incident.  When I tried to upgrade a second site - after unzipping the files and running the upgrade process - it just displays the main page for the previously upgraded site.  I think this is caused by my using the same SQL DB and username during installation - is there an easy way to rectify this?  Can you change what SQL use a site uses easily just by changing the info in the web.config after creating the appropriate user?

I was able to upgrade another site on the same hosting company which is using a seperate DB and SQL user.

 
New Post
8/13/2006 7:15 PM
 

I am not sure what you are asking or where this went wrong. I can say that each site will need its own connection string attributes set in the web.config.

 


Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
8/16/2006 7:23 AM
 
Sorry - guess I was rambling.  I'll try again.

I upgraded www.domain1.com fine with no problems.  I followed standard upgrade procedures by updating the related lines in release.config from the original web.config, then I renamed the file to web.config and uploaded via FTP this file and the upgrade ZIP, unzipped the filesystem and loaded the domain - this upgrade then ran fine.  Next I attempted to upgrade www.domain2.com - I backed up the SQL DB and the filesystem.  Then copied the related lines to release.config, renamed to web.config and copied the new web.config and the upgrade file up to the server.  When I loaded www.domain2.com instead of getting the upgrade script - I received the home page for www.domain1.com - both of these sites are in the same DB and use the same DB user - just a different table prefix.

After restoring the filesystem for www.domain2.com - the site was functional.  I then went through the same upgrade procedure for www.domain3.com which is in a seperate SQL DB and the upgrade completed without any errors.

I looked through web.config but I did not notice a entry for the table prefix - I think I was mistaken when I first installed the sites by using the same DB and user - is it possible to change this without impacting the site?

Any assistance will be greatly appreciated.

Allan
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade to 3.3.3Upgrade to 3.3.3


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