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 ...Problem with upgrade 5.01.04 to 5.02.01 (sqldataprovider)Problem with upgrade 5.01.04 to 5.02.01 (sqldataprovider)
Previous
 
Next
New Post
1/20/2010 3:29 PM
 

Did a standard upgrade install from 5.01.04 to 5.02.01

Got the following:

Upgrade Status Report
00:00:00.015 - Upgrading to Version: 05.02.01
00:00:00.015 -   Executing Script: 05.02.00.SqlDataProvider Error! (see 05.02.00.log for more information)
00:00:09.781 -   Executing Script: 05.02.01.SqlDataProvider Success
00:00:10.140 -   Executing Application Upgrades: 05.02.00 Success
00:00:12.218 -   Executing Application Upgrades: 05.02.01 Success
00:00:12.234 -   Cleaning Up Files: 05.02.00 Success
00:00:12.234 -   Cleaning Up Files: 05.02.01 Success
00:00:12.234 -   Updating Config Files: 05.02.00 Success
00:00:12.265 -   Updating Config Files: 05.02.01 Success
00:00:12.265 - Performing General Upgrades
00:00:12.328 - Installing Optional Modules:
00:00:12.343 -   Installing Package File HTML_Community_05.01.04_Install:  Error!
00:00:13.468 -   Installing Package File HTML_Community_05.02.00_Install:  Error!

00:00:13.843 - Installing Optional Skins:
00:00:13.843 - Installing Optional Containers:
00:00:13.843 - Installing Optional Languages:
00:00:13.843 - Installing Optional Providers:
00:00:13.843 -   Installing Package File AspNetMembershipProvider_05.02.00_Install:  Success
00:00:13.953 -   Installing Package File CorePermissionProvider_05.01.01_Install:  Success
00:00:13.984 -   Installing Package File DatabaseLoggingProvider_05.01.01_Install:  Success
00:00:14.031 -   Installing Package File DNNMembershipProvider_05.01.03_Install:  Success
00:00:14.062 -   Installing Package File DNNMenuNavigationProvider_05.01.00_Install:  Success
00:00:14.109 -   Installing Package File DNNTreeNavigationProvider_05.01.00_Install:  Success
00:00:14.218 -   Installing Package File FckHtmlEditorProvider_02.00.04_Install:  Success
00:00:15.249 -   Installing Package File FileBasedCachingProvider_05.01.03_Install:  Success
00:00:15.281 -   Installing Package File FileModuleCachingProvider_05.02.01_Install:  Success
00:00:15.437 -   Installing Package File MemoryModuleCachingProvider_05.02.01_Install:  Success
00:00:15.578 -   Installing Package File SchedulingProvider_05.02.01_Install:  Success
00:00:15.656 -   Installing Package File SearchIndexProvider_05.01.00_Install:  Success
00:00:15.687 -   Installing Package File SearchProvider_05.01.01_Install:  Success
00:00:15.734 -   Installing Package File SolpartMenuNavigationProvider_05.01.00_Install:  Success
00:00:15.781 - Installing Optional AuthSystems:
00:00:15.781 -   Installing Package File LiveID_01.00.01_Install:  Success
00:00:15.843 -   Installing Package File OpenID_02.00.00_Install:  Success
00:00:15.937 - Installing Optional Packages:

Not sure whether the later HTML_Community installation problem is related to the earlier SQLDataProvider install error so decided to deal with the data provider error first.

Here is the start of the 05.02.00.log file (it is followed by the same error for CacheMethod column in TabModules table, CultureCode column in PortalSettings, and others) :

System.Data.SqlClient.SqlException: Column names in each table must be unique. Column name 'FriendlyName' in table 'parkrun.Schedule' is specified more than once.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL)
   at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)

 

/* Add FriendlyName to Schedule Table */
/**************************************/

ALTER TABLE parkrun.Schedule ADD
 FriendlyName nvarchar(200) NULL

 
New Post
1/20/2010 7:45 PM
 

Have to ask... from what version did you upgrade into 5.1.4?

Have you always used Object Qualifiers in your database? 

Object Qualifiers in the upgrade scenario was tested and this issue was not seen.

 


Ken Grierson
DotNetNuke Corporation
Test Lead
 
New Post
1/20/2010 8:25 PM
 

Started this install with 5.01.01 and patched with all updates since.

I have always used the object qualifier.

 
New Post
1/20/2010 9:52 PM
 

Is there any possibility that the 5.02.00 upgrade had been run previously but failed to complete? Do you recall getting any errors during any of the prior upgrades? The error related to adding the FriendlyName column to the Schedule table (and probably the other errors in the 05.02.00.log file raised when adding columns to tables) indicates that the FriendlyName column already exists in the Schedule table. A quick look through the 05.xx.xx.SqlDataProvider scripts indicates that it is only in the 05.02.00 script that this column could have been added.

If you have access to the database, please look at the design of the parkrun.Schedule table and let us know if it includes a FriendlyName column

Also, did you mean databaseOwner (parkrun) not objectQualifier? I believe that if you had been using an objectQualifier, the 05.02.01.SqlDataProvider script would have shown a known error when modifying the Lists table.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
1/21/2010 12:30 PM
 

Unfortunately I was getting so many 'out of memory exceptions' after yesterday's problemmatic upgrade that I've had to roll back to a previous version.   I wish there were an easier way to do that!  I'll get back to you about the 5.02.00 install once I'm back on my feet.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Problem with upgrade 5.01.04 to 5.02.01 (sqldataprovider)Problem with upgrade 5.01.04 to 5.02.01 (sqldataprovider)


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