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...upgrading dnn 5.4.4 to .5.5.1 success then moved db failed.upgrading dnn 5.4.4 to .5.5.1 success then moved db failed.
Previous
 
Next
New Post
9/29/2010 11:52 AM
 
OK, I start a project under version 5.4.4 and noticed a critical updated was need so I backup data and site and updated with success.  I completed the site locally on a vm tied to sql server 2005.  Then I moved the site to the production server running sql 2005, I created the db and restored the database then connected my local vm to the production db to make sure everything is ok.  Now the funny part, the database started to run an update again to 5.5.1, which ran successful, but when I went to the home page all the content was gone!  It's like a fresh build.  I can see the data in the database but can't get to it.  Any idea's?

Thanks
 
New Post
9/29/2010 12:37 PM
 
unfortunately you shouldn't try to execute an upgrade on a database after you've already performed the upgrade on the file system. Any chance you can restore back to your original 5.4.4 backups and start over?

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
9/29/2010 12:41 PM
 
most likely the connection string did not match the database. validate both connection strings in your web.config and make sure, the machinekey value has not been altered.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/29/2010 3:10 PM
 
the only thing I changed in the connection string is from express to 2005/2008.  so your saying that caused the update?  If so I should just continue using the express and point it to the new server?  Or could I just turn off AutoUpgrade in the config file to prevent it from updating?

Thanks
Ross
 
New Post
9/29/2010 5:12 PM
 
if you are running full sql server version, access using database.mdf is not supported, you need to attach the database and specify database name and user credentials.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...upgrading dnn 5.4.4 to .5.5.1 success then moved db failed.upgrading dnn 5.4.4 to .5.5.1 success then moved db failed.


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