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...SQL Exception on upgrade from 7.0.3 to 7.1.2SQL Exception on upgrade from 7.0.3 to 7.1.2
Previous
 
Next
New Post
10/21/2013 3:58 AM
 
PS: issue might be caused by wrong database compatibility level, if the database has been created originally on a previous version of SQL server, please make sure that it is set to highest value available (100 on SQL Server 2008).
If this caused an issue, other objects might not have been created or updated properly on DNN upgrades as well.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/21/2013 3:24 PM
 

Thank you very much for your suggestions. The db has always been on MS SQL 2008 R2 and the compatibility level is 100. In the log folder are no other problems reported. This Journal issue is the only one. The interesting thing is that all related stored procedures are there. Just the tables are missing.

The Journal module can be uninstalled in version 7.0.3 but not in version 7.1.2. So I uninstalled and reinstalled that module from the extensions. Unfortunately that did not help as the module package did not include the SQL statements, therefore no tables have been created.

So I just ended up creating the tables manually from a valid DNN install of the same version (7.0.3) and then upgraded the system without any error.

Is there any way to check if the DNN install/database is valid?

 

Cheers

Nils

 
New Post
10/22/2013 5:43 AM
 

Best way would be to compare the database with an other of a 2nd instance.  You have to check tables, procedures, views and functions.  I would not recreate existing tables about you loost the data in most times.  But missing tables, procedures, views and functions can recreated using Querys on SQL Management Studio.  Some SQL knowledge and DNN knowledge is needed to fix databases. 

You can also check the xxx.log.resources files on the Providers\DataProviders\SqlDataProvider Folder.  Empty files are ok, files with Content are issues on install.  The Content of this files can help us to solve your issue.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...SQL Exception on upgrade from 7.0.3 to 7.1.2SQL Exception on upgrade from 7.0.3 to 7.1.2


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