Products

Solutions

Resources

Partners

Community

About

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!

Diagnosing database errors

Return to previous page

  • 4/7/2015
  • 4141 Views

Comments

4141 Views

Diagnosing database errors

Last updated long time ago

Comments

Common

(Enter the content of this article below)

Advanced

 

Background

DotNetNuke can experience database errors for a number of reasons e.g. incorrect database requirments e.g. running DotNetNuke 5.2.0 under SQL 2000), database integrity issues (caused by previous failed installs/upgrades or clashes with 3rd party modules that alter DotNetNuke core tables) or the database having issues itself (e.g. the database is down, full or doesn't support remote connections)

If you experience database errors there are a number of places to look.

Install/upgrade logfiles

If sites experience database errors during install/upgrade the errors are logged. These log files can be found in the Providers\DataProviders\SqlDataProvider folder. Early versions of DotNetNuke created log files with a *.log extension, but since DotNetNuke 5.5.0 these files are in the form *.log.resources. If the files are empty that indicates that that script executed succesfully, otherwise the error will be in the file.

These files include (names are all in DotNetNuke 5.5.0+ format, for earlier versions remove .resources):
  • DotNetNuke.Data.log.resources - errors are logged in this file if errors occur during install with adding data
  • DotNetNuke.Schema.log.resources - errors are logged in this file if errors occur during install when creating objects (tables, stored procedures etc.)
  • Individual files can also show errors if a version file fails e.g. 06.00.00.log.resources




Contents
No sections defined
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out