Hi,

is possible to upgrade from DNN2.1.2. to DNN 3.0.12 ?
Where I can find instruction in order to do conversion ?

thanks.

I guess, you don't have to do anything. Simply overwrite your site, with the latest version, and it will upgrade if for you

(But, dont forget to take the Site as well as Database backup, first )

Has anyone tried this successfully on a commercial server - or are there any traps to watch for?

The only real hurdle are custom modules. If you have some that have not been rewritten for DNN 3, I would suggest removing them...however, do nothing until you back up your files and database.

I updated from 2.1.2 to 3.12 last thursday at 21:30.   It took me until friday night to get it running correctly.  Some of my problems were self inflicted.

Problem 1

After testing the upgrade on my local machine I uploaded my dnn3 directory to the web and tried to upgrade.  It kept failing stating that a stored procedure could not be found.  I tracked this one down to the existance of \Install\dnn.config.  dnn.config contains the current version number and is used to identify if it is necessary to upgrade the database.  This file seems to be created as part of the upgrade process.  By copying my dnn3 folder to my host I included this file effectively telling dnn that the upgrade had already been done but my db was still ver 2.1.2.  Deleting dnn.config allowed the upgrade of my db and solved this problem.

Problem 2

I encountered some problems but eventually got it sorted.  My main problem was that a number of users on one of my sites were dropped.  They could not sign in.  I tried adding them again but got error messages stating that the username was invlaid.  I looked at the db and found that the usernames existed in the Users table but not in the aspnet_users table.

After scratching my head for a while I deleted the offending usernames from the users table and was then able to add them back into the db.  The problem would appear to have been related to the number of characters in the users passwords.  Those in difficulty had 3 character passwords.  In Web.config there is a setting

<code>

<members

   <providers>

      <add name="DNNSQLMembershipProvider"

               minRequiredPasswordLength="4"

</code>

I suspect if I had set this to "0" before the upgrade the users would have migrated without any difficulty.

One username was only 2 characters and also failed migration.  I can't find any setting for minimum username length.  Have I just missed it?

Problem 3

After migration any subdomains added could not be accessed.

i.e.  subdom.mysite.com always returned www.mysite.com

I had only uploaded the files I thought necessary.  I omitted *.vb and any .resx files associated with ascx files.  I guess I omitted something else that was required, though I don't know what, as everything is now working fine after I uploaded the FULL dnn3 directory.

Is there a list of files that may safely be removed from a hosted environment - to save space?  Solution and project files are not necessary.  What else can we safely remove?

-dw

I have made also change in some file in DNN 2.1.2,

..and if I want to make a fresh installation with DNN 3.0.12 in which way I can move all people subscribe to my old DB (MSSQL)  in the new one ?

"I want to make a fresh installation with DNN 3.0.12 in which way can I move all people subscribing to my old DB (MSSQL)  in the new one ?"

I am looking for this answer also!  Does anyone have an answer for this??????

I try to make an upgrade on my local machine but I received this message:

'Stored procedure 'dbo.GetTabByName' not found.

[InvalidOperationException: Stored procedure 'dbo.GetTabByName' inesistente.] System.Data.SqlClient.SqlCommand.DeriveParameters() +1268 System.Data.SqlClient.SqlCommandBuilder.DeriveParameters(SqlCommand command) +41 Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.DiscoverSpParameterSet(SqlConnection connection, String spName, Boolean includeReturnValueParameter, Object[] parameterValues) Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSetInternal(SqlConnection connection, String spName, Boolean includeReturnValueParameter) Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName, Boolean includeReturnValueParameter) Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName) Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) DotNetNuke.Data.SqlDataProvider.GetTabByName(String TabName, Int32 PortalId) +127 DotNetNuke.Entities.Tabs.TabController.GetTabByName(String TabName, Int32 PortalId, Int32 ParentId) +23 DotNetNuke.Services.Upgrade.Upgrade.UpgradeApplication() +65 DotNetNuke.Services.Upgrade.Upgrade.UpgradeDNN(String strProviderPath, String strDatabaseVersion) +1334 DotNetNuke.Framework.Install.UpgradeApplication() +567 DotNetNuke.Framework.Install.Page_Load(Object sender, EventArgs e) +234 System.Web.UI.Control.OnLoad(EventArgs e) +67 System.Web.UI.Control.LoadRecursive() +35 System.Web.UI.Page.ProcessRequestMain() +750

Any suggestion ?

• Try to delete the dnn.config file from the /Install folder.

because it may be because you have fresh install where a existing installation had been.

DougV wrote:

"I want to make a fresh installation with DNN 3.0.12 in which way can I move all people subscribing to my old DB (MSSQL)  in the new one ?" I am looking for this answer also!  Does anyone have an answer for this??????

I found this in another post. I have not tried it as I'm looking for problems with upgrades before I try it.

"Module Data Exchanger help you to export data of dnn2 module to XML file and import data from XML file to dnn2 module. The name and structure of exported XML file structure follow the definition of DNN 3.x."
http://www.zldnn.com/Default.aspx?tabid=141

tamarabrown wrote:

I'm looking for problems with upgrades before I try it.

Before V2 --> V3 upgrade I am advising to remove all commas in any fields of  RoleName inside Table Roles

Inside Table Roles is column of data RoleName.  In Version 2.0.12 it was Okay to have a comma in this field such as

Publisher, Bulletin

Simply remove the comma before you upgrade to Version 3.

webguru03 wrote:

Has anyone tried this successfully on a commercial server - or are there any traps to watch for?

webguru3,

I was able to successfully upgrade our DNN 2.1.2 portal to DNN 3.0.12 in a production environment. Check out the links below:

http://www.kreko.com/

http://dnn2.kreko.com

I also had to face most of the issues described here and even more. About 70% of the modules I was using were custom modules I purchased from other developers. The migration has been very painful to say the least.

Here is what I ended up doing (after trying all other options including a full migration): I used the Copy Database Wizard in Enterprise Manager (SQL Server, of course) to create a new database based on my old DNN2 database. I then installed a fresh copy of DNN 3.0.12 in a new location, and let DNN to do its magic. Of course, there were problems, but turns out that the only thing I needed to do to get DNN to upgrade my database was deleting the dnn.config file.

How do you deal with your custom modules. I have an updates for my DNN3 modules but do I do I upgrade my DNN 2 site to DNN 3 and then reinstall the new DNN 3 modules or install the DNN3 modules first in my DNN2 site and then upgrade it to DNN3?

Dealing with the upgrade of the modules is not easy.  How I did mine was delete all the third party modules, performed the upgrade, and then reinstalled the new modules.  I had problem with the user migration also.  My problem stemmed from the old users not being added to the registered user's group.  I manually made the databases changes and now up and going.  

It was a painful trip, but well worth the effort!

Phebous... 

 

I'm getting the following error when I attempt to upgrade:

Item has already been added. Key in dictionary: "localhost/dotnetnuke" Key being added: "localhost/dotnetnuke"

I'm not sure why I'm getting this error, any suggestions?