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...Skin incompatibility after upgrade?Skin incompatibility after upgrade?
Previous
 
Next
New Post
11/12/2010 6:59 PM
 
I get a BC32206 error, like others mentioned on various posts, but skin related (XD Media Blue).  I have been fighting with this for some time, and have the site still at 4.8.4 as a result [actually I'm rolling back to 4.8.4, again, as we speak because the site flat won't run after another  'successful' GoDaddy upgrade].  How do I get out of the Catch 22??  I can update my skin in 5.5.1 (5.X); I know this from test on a different 5.5.1 site.  I can't ever get to that point on this live site because I cannot get the site to even come up to let me do that in 5.X ...  I'll be an SOB if I'm going to throw all my in-site work away because of a stupid skin incompatibility...

The fight seems to be direct 2.2.0.7 vs. indirect 2.2.2.0 of a dotnetnuke.webcontrol.dll and a need to update some Nav.ascx.vb file to call 2.2.2.0; I'm not a novice but this is more than a user should need to know/do...  Can I just convert my skin on the side somehow and plug it in and have it work (either before or after the upgrade/conversion)?
 
New Post
11/12/2010 9:09 PM
 
Correction; I was/am using DNN-Blue skin; I think that's the problem...  Rolled back to 4.9.0 and changed defaults and 'converted'/reinstalled skin package; we'll see.  GoDaddy doesn't let me go forward one step at a time to it's 5.5.1 or bust...
 
New Post
11/13/2010 5:35 PM
 
Here is where I am... After a trip back to 4.9.0, I was able to fix (convert) the skin. I was then able to run the site when I got back to 5.5.1 [keep in mind GoDaddy rolls forward only in one step, but rolls back one version at a time so my only step from 4.9.0 forward was to 5.5.1] Everything worked except the HTML module. It gave me the same direct 2.2.0.7 vs indirect 2.2.2.0 BC32206 dotnetnuke.webcontrol.dll error as before, but only returned for the HTML module call so all else ran !! At the suggestion from a different/earlier post on the same error, I performed the following except using the 5.5.1 install package: " .vb files are no longer needed for HTML module, it has been converted to WAP format using a dll. if you have problems to run HTML on your site: delete content of folder /app_code/html/ delete content of folder /desktopmodules/html/ (if present) delete file /bin/dotnetnuke.modules.html.dll (if present) delete file /bin/dotnetnuke.modules.html.sqldataprovider.dll (if present) unzip dnn_html_05.02.00.zip from /install/module in DNN 5.2.0 upgrade package in Host :: Extensions menu item, use command "extensions installation wizard" to re-install html module. HTH " I get the following error on install; the html module is obviously now gone go it throws no error but I need an HTML module to install... : Package Installation Report See below for the results of the package installation Error loading files from temporary folder - see below StartJob Starting Installation Info Starting Installation - DNN_HTML Info Starting Installation - Script Info Begin Sql execution Info Folder Created - d:\hosting\ilborough\dotnetnuke\DesktopModules\HTML\Providers\DataProviders\SqlDataProvider Info Created - Providers\DataProviders\SqlDataProvider\03.00.00.SqlDataProvider Info Executing 03.00.00.SqlDataProvider Info Start Sql execution: 03.00.00.SqlDataProvider file Failure SQL Execution resulted in following Exceptions: System.Data.SqlClient.SqlException: Invalid column name 'DesktopHtml'. Invalid column name 'DesktopSummary'. Invalid column name 'CreatedByUser'. Invalid column name 'CreatedDate'. 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) /** Create Stored Procedures **/ create procedure dbo.AddHtmlText @ModuleId int, @DesktopHtml ntext, @DesktopSummary ntext, @UserID int as insert into HtmlText ( ModuleId, DesktopHtml, DesktopSummary, CreatedByUser, CreatedDate ) values ( @ModuleId, @DesktopHtml, @DesktopSummary, @UserID, getdate() ) System.Data.SqlClient.SqlException: Invalid column name 'DesktopHtml'. Invalid column name 'DesktopSummary'. Invalid column name 'CreatedByUser'. Invalid column name 'CreatedDate'. 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) create procedure dbo.UpdateHtmlText @ModuleId int, @DesktopHtml ntext, @DesktopSummary ntext, @UserID int as update HtmlText set DesktopHtml = @DesktopHtml, DesktopSummary = @DesktopSummary, CreatedByUser = @UserID, CreatedDate = getdate() where ModuleId = @ModuleId Info End Sql execution: 03.00.00.SqlDataProvider file Info Finished Sql execution Failure Installation Failed - Script I can roll back again, but I figured I might be better off setting at 5.5.1 and trying to recover the HTML module. Ideas??
 
New Post
11/14/2010 2:47 PM
 
Solved, with lessons learned.  Two problems:

One was a skin that worked in 4.8.4 but not 5.5.1.  Had I been able to 'step forward' through the version upgrades it would have gotten 'corrected' at 4.9.0.  I had to 'peel back' my upgrades one at a time, got to 4.9.0 and fixed it, then upgraded forward and the site came up (95%; all but HTML).  Two lessons:  One is upgrade one rev at a time (GoDaddy does not let you do this..., but they do let you roll back one rev at a time...).  Second is you can 'neutralize' your site (default skins, etc) before an upgrade.  Both helped me get to a point where I could 'convert' my offending skins.

Second problem was the HTML module changed drastically between 4.8.4 and 5.5.1, and I used that module extensively.  Other posts led me to 'peel back' my site and I found that, at 5.4.1, if I stopped and ran my site there that the HTML module got updated; if I did not stop there and run the site, the HTML module was not updated properly (at least on GoDaddy).

GoDaddy could help themselves and their users by allowing a step-wise forward upgrade.  Of course users can do this on their own with diligence...

Thanks to Sebastian Leopuld (sp?), whose posts on other issues provided the insight and courage to try all this on my own...
 
New Post
11/15/2010 9:16 PM
 
I don't think any hosting provider actually allows you to pick and choose which version to upgrade to, definitely not each and every small upgrade version. You would have to do that on your own by means of ftp'ing each version upgrade on your own and letting each install itself. You can do that on Godaddy and I presume on any host. Most hosts will offer the latest version and that's it. I'm actually surprised that Godaddy has a current version available, they were always way, way behind on that. They were also years behind on most of their security updates and protocols which raised a red flag and caused the one client using Godaddy to switch to a new hosting provider that did keep current with security protocols. I will never host there and will never let a client do so either. There are far better, and more affordable web hosts out there than to waste your time and money on subpar hosting like Godaddy. Upgrade issues with DNN happen on any and all web hosting platforms, too, btw, so unfortunately you'll never be free of that no matter where you host.

JOHN GIESY
DotNetNuke Hosting Expert

DotNetNuke 7 Hosting $70 /year
DNN4Less.com Team DotNetNuke  

Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Skin incompatibility after upgrade?Skin incompatibility after upgrade?


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