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 ...Upgrading 02.01.02 to 04.00.03 (GetTabByName)Upgrading 02.01.02 to 04.00.03 (GetTabByName)
Previous
 
Next
New Post
6/13/2006 12:48 PM
 

I'm using just the Install files for installing 04.00.03

I'm having problems upgrading from 02.01.02 to 04.00.03.  I get an exception stating that GetTabByName doesn't exist.  I look at the database and see that this is true.  I looked at my original backed up copy from before the installation and see that it does in fact, exist.  Somewhere along the line, DotNetNuke is dropping this procedure.  Is there a file that I can edit so that this procedure is not dropped during the upgrade?

I've read a few other forums that suggest that a Case-Sensitie Collation could be the problem here.  My collation for this database is Latin1_General_CI_AS.  Also my database user has dbo access to this database, and is also set to this database as there default database.

A clean install of a new .Net site works fine.  In fact, I can see that the procedure (GetTabByName) exists in the clean version as well.  The upgrade process is when I run into this problem.  I'm trying the upgrade process of the .Net code on a Windows XP desktop first, but the database is SQL Server 2000 on a Windows 2003 server.

This is the response that I get when I try to upgrade.  I've tried this several times and get the same results.

Upgrading DotNetNuke
Current Assembly Version: 04.00.03
Current Database Version: 02.01.02

Upgrade Status Report
00:00:00.015 - Upgrading to Version: 3.1.1
00:00:01.046 - Upgrading to Version: 3.2.0
00:00:01.109 - Upgrading to Version: 4.0.0
00:00:01.250 - Upgrading to Version: 4.0.1
00:00:01.296 - Upgrading to Version: 4.0.2
00:00:01.296 - Upgrading to Version: 4.0.3
00:00:01.312 - Performing General Upgrades

--------------------------------------------------------------------------------

Server Error in '/DotNetNuke' Application.
--------------------------------------------------------------------------------

The stored procedure 'dbo.GetTabByName' doesn't exist.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: The stored procedure 'dbo.GetTabByName' doesn't exist.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. 

Stack Trace:
[InvalidOperationException: The stored procedure 'dbo.GetTabByName' doesn't exist.]
   System.Data.SqlClient.SqlCommand.DeriveParameters() +878680
   System.Data.SqlClient.SqlCommandBuilder.DeriveParameters(SqlCommand command) +88
   Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.DiscoverSpParameterSet(SqlConnection connection, String spName, Boolean includeReturnValueParameter, Object[] parameterValues) +212
   Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSetInternal(SqlConnection connection, String spName, Boolean includeReturnValueParameter) +303
   Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName, Boolean includeReturnValueParameter) +154
   Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName) +36
   Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) +200
   DotNetNuke.Data.SqlDataProvider.GetTabByName(String TabName, Int32 PortalId) +129
   DotNetNuke.Entities.Tabs.TabController.GetTabByName(String TabName, Int32 PortalId, Int32 ParentId) +24
   DotNetNuke.Services.Upgrade.Upgrade.UpgradeApplication() +63
   DotNetNuke.Services.Upgrade.Upgrade.UpgradeDNN(String strProviderPath, String strDatabaseVersion) +1259
   DotNetNuke.Framework.Install.UpgradeApplication() +507
   DotNetNuke.Framework.Install.Page_Load(Object sender, EventArgs e) +388
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +47
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061

 --------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

 
New Post
6/13/2006 4:42 PM
 
The simple answer was that I needed to upgrade to 3.x first before upgrading to 4.x code.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrading 02.01.02 to 04.00.03 (GetTabByName)Upgrading 02.01.02 to 04.00.03 (GetTabByName)


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