DotNetNuke

Re: Upgrade from DNN 2.1.2 to DNN 3.0.12

IndianGuru — Fri, 27 Jan 2006 05:39:47 GMT

I think, it is relatively easy, However do take care of Machine Keys

Besides, think over to upgrade to 4.0.2 at the earliest :)

Re: Upgrade from DNN 2.1.2 to DNN 3.0.12

lilryno — Fri, 27 Jan 2006 01:57:01 GMT

Thread revival for anybody stil using 2.1.2. I'm getting ready to attempt to upgrade my site from 2.1.2 to the latest DNN3 version. Does anyone know if the latest DNN3 makes the upgrade any smoother? Is an upgrade from 2.1.2 to 3.2.2 even feasible? Thanks for any help!

Re: Upgrade from DNN 2.1.2 to DNN 3.0.12

webguru03 — Wed, 15 Jun 2005 02:57:47 GMT

It seems that upgrades should work "out of the box" but the one I did last from 2.0.12 to 3.1.0 did not. I have done these steps:
1/ Copied the db using DTS to new location
2/ Expanded fresh 3.1.0 files to new location
3/ Changed web.config to point to new db
4/ Made sure there is no dnn.conmfig in the Install folder
5/ Started the new location's URL
I must point out that the new location URL has been setup as the same used and stored in the old 2.0.12 db's portal alias list. The URL is sample.borderemail.com and gives me the following error:

Server Error in '/' Application.

Object reference not set to an instance of an object.

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.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]
   DotNetNuke.Framework.Reflection.CreateObjectNotCached(String ObjectProviderType) +26
   DotNetNuke.Services.Cache.CachingProvider.CreateProvider() +11
   DotNetNuke.Services.Cache.CachingProvider..cctor() +15

[TypeInitializationException: The type initializer for "DotNetNuke.Services.Cache.CachingProvider" threw an exception.]
   DotNetNuke.Services.Cache.CachingProvider.Instance() +0
   DotNetNuke.Framework.Reflection.CreateObject(String TypeName, String CacheKey) +46
   DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectNamespace, String ObjectAssemblyName) +295
   DotNetNuke.Services.Log.EventLog.LoggingProvider.CreateProvider() +22
   DotNetNuke.Services.Log.EventLog.LoggingProvider..cctor() +15

Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032

Any clues about why this has happened? What did I do wrong or miss???

Re: Upgrade from DNN 2.1.2 to DNN 3.0.12

dstruve — Tue, 03 May 2005 16:39:42 GMT

Im curious how collation is causing this problem?

Re: Upgrade from DNN 2.1.2 to DNN 3.0.12

count_ur_blessings — Tue, 03 May 2005 15:50:52 GMT

i am also trying to upgrade DNN from my developement server to a test environment but having no luck...after following some of your steps above, i still encounter an error in the upgrade and i also notice that the dnn.config still gets generated even after i have deleted it from the Install directory...here's what i get...can anyone help me out on this???

Object reference not set to an instance of an object.
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.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]
   DotNetNuke.Services.Localization.Localization.GetString(String name, String ResourceFileRoot, PortalSettings objPortalSettings)
   DotNetNuke.Services.Localization.Localization.GetString(String name, PortalSettings objPortalSettings)
   DotNetNuke.UI.Skins.SkinController.UploadSkin(String RootPath, String SkinRoot, String SkinName, Stream objInputStream)
   DotNetNuke.UI.Skins.SkinController.UploadSkin(String RootPath, String SkinRoot, String SkinName, String Path)
   DotNetNuke.Modules.Admin.ResourceInstaller.ResourceInstaller.Install(Boolean status, Int32 indent)
   DotNetNuke.Services.Upgrade.Upgrade.InstallDNN(String strProviderPath)
   DotNetNuke.Framework.Install.InstallApplcation()
   DotNetNuke.Framework.Install.Page_Load(Object sender, EventArgs e)
   System.Web.UI.Control.OnLoad(EventArgs e) +67
   System.Web.UI.Control.LoadRecursive() +35
   System.Web.UI.Page.ProcessRequestMain() +750

The installation status report always stops at the same line...

Installation Status Report
00:00:00.109 - Installing Version: 3.0.12
00:00:00.124 - Installing Script: DotNetNuke.SetUp.SqlDataProvider
00:00:00.140 - Installing Script: DotNetNuke.Schema.SqlDataProvider
00:00:03.296 - Installing Script: DotNetNuke.Data.SqlDataProvider
00:00:06.265 - Installing MemberRole Provider:
00:00:06.281 - Executing InstallCommon.sql
00:00:06.718 - Executing InstallMembership.sql
00:00:07.218 - Executing InstallProfile.sql
00:00:07.453 - Executing InstallRoles.sql
00:00:07.781 - Executing FixNames.sql
00:00:08.953 - Performing General Upgrades
00:00:09.156 - Loading Host Settings:
00:00:09.281 - Configuring SuperUser:
00:00:09.484 - Installing Desktop Modules:
00:00:09.484 -   Installing Announcements:
00:00:09.531 -   Installing Contacts:
00:00:09.546 -   Installing Discussions:
00:00:09.578 -   Installing Documents:
00:00:09.593 -   Installing Events:
00:00:09.609 -   Installing FAQs:
00:00:09.624 -   Installing Feedback:
00:00:09.656 -   Installing IFrame:
00:00:09.671 -   Installing Image:
00:00:09.687 -   Installing Links:
00:00:09.718 -   Installing News Feeds (RSS):
00:00:09.734 -   Installing Text/HTML:
00:00:09.749 -   Installing User Defined Table:
00:00:09.781 -   Installing XML/XSL:
00:00:09.796 -   Creating Portal: DotNetNuke Default Portal
00:00:12.812 -   Successfully Installed Portal 0:
00:00:12.812 - Installing Optional Resources:
00:00:12.812 -   Installing Coontainer File c:\virtualroot\mydirectory\Install\Container\X-CHRON C BLACK.zip:

Re: Upgrade from DNN 2.1.2 to DNN 3.0.12

bradels — Fri, 01 Apr 2005 20:56:32 GMT

Hey Guys,

I recently did a migration of several sites from v2 to v3 and had a few hiccups, but nothing major. Good to see people helping out others when something crops up. I was just wondering whether you guys had come across something like this which has happened on one of my sites which has been upgraded from v1 to v2 in the past, and now made the step to v3:

Everything works except for one thing- There are several Host pages do not appear in the menu.
These are- SuperUser Accounts, Lists, and Skins (in the Host menu). I actually really need the Lists functionality at the moment.

I have searched the DNN DB for tabs, thinking that they may be in the DB but not appearing on the menu. However there are no tabs relating to the Superuser Accounts, Lists or, Host Skins pages. Hence I cant just pass the tabid into the URL to arrive at the page. Any idea what could be causing this? Or a way to get these tabs back?

I have searched the forum for this problem, but have been unable to find something similar. Any Ideas?

Re: Upgrade from DNN 2.1.2 to DNN 3.0.12

fatatiba — Fri, 01 Apr 2005 17:10:54 GMT

I got it solved,

CAUSE:

I copy my database from the production server to the development server, however, both have different collation. When I tryied to upgrade the DotNetNuke from 2.1.4 to 3.0.12 I got the error.

SOLUTION:

1. delete my development database

2. create an empty database on my development server

3. Copy my database from the production server using DTS Export Wizard

4. Using SQL Query Ananlyzer, I execute the following SQL statments to change the collation to reflect what I have on my production server database:

USE Tempdb
GO
ALTER DATABASE Pubs COLLATE SQL_Latin1_General_CP1_CI_AS
GO

5. I create a new folder for DotNetNuke on my development server and extract DNN 3.0.12 into.

6. fire up Internet Explorer and point to my local copy of DNN and the upgrade went great.

except of course for Custom Modules which are not supported by the DNN v3.0.

I think my next step is to do the upgrade on my production server once I finilize the custom modules to be compatabile with DNN v3.0.

Re: Upgrade from DNN 2.1.2 to DNN 3.0.12

klunde — Fri, 01 Apr 2005 10:15:41 GMT

I found that on my network my two servers I was using to test the upgrade didn't have the same default collation and that was the problem. Here's how I created a copy on another server and avioded this collation error:

Cleaned my production server by emptying recycle bin and removing obsolete modules
Have an existing DNN 2.1.2 running on my test server and production server
Delete all files from c:\inetpub\dotnetnuke on my test server
Delete the sql database DotNetNuke on my test server
Execute SELECT DATABASEPROPERTYEX('dotnetnuke', 'Collation') AS 'Database Level Collation' on my production server
Manually create database DotNetNuke on my test server with the collation found above
Use SQL Enterprice Manager and export the database from production server to test server with DTS Export Wizard:

Used Copy Objects and Data
Include extended properties
checked use collation

Changed the table Portals on my test server to reflect my alias for DotNetNuke on the test server
Copy all files from c:\inetpub\dotnetnuke on my production server to c:\inetpub\dotnetnuke on my test server
apply all files from DotNetNuke_3.0.12.zip to c:\inetpub\dotnetnuke on my test server
Edited web.config
Upgrade OK!

</Morten>

Re: Upgrade from DNN 2.1.2 to DNN 3.0.12

fatatiba — Fri, 01 Apr 2005 00:42:39 GMT

I finally got it.

I opened Providers\DataProviders\SqlDataProvider folder in my DotNetNuke installition after the upgrade faild and I found 03.00.04.log file which cotains a log of all the exceptions occured during the upgrade for version 03.00.04 script.

it seems that errors are related to collation coflect issue :

These are the errors and the stored procedures that are not copyed:

System.Data.SqlClient.SqlException: Code page translations are not supported for the text data type. From: 1256 To: 1252.

CREATE procedure dbo.DotNetNuke_AddVendor

CREATE procedure dbo.DotNetNuke_UpdateVendor

System.Data.SqlClient.SqlException: Cannot resolve collation conflict for column 19 in SELECT statement.

CREATE procedure dbo.DotNetNuke_GetVendor

System.Data.SqlClient.SqlException: Cannot resolve collation conflict for column 3 in SELECT statement.

CREATE procedure dbo.DotNetNuke_GetPortal

System.Data.SqlClient.SqlException: Cannot resolve collation conflict for column 3 in SELECT statement.

CREATE procedure dbo.DotNetNuke_GetPortalByPortalAliasID

System.Data.SqlClient.SqlException: Cannot resolve collation conflict for column 3 in SELECT statement.

CREATE PROCEDURE dbo.DotNetNuke_GetPortals

System.Data.SqlClient.SqlException: Cannot resolve collation conflict for column 19 in SELECT statement.

CREATE procedure dbo.DotNetNuke_GetModule

System.Data.SqlClient.SqlException: Cannot resolve collation conflict for column 20 in SELECT statement.

CREATE procedure dbo.DotNetNuke_GetPortalTabModules

and the lest goes on ...

Can any one tell me .. what is this collation coflect means .. and how it can be resolved ?

Re: Upgrade from DNN 2.1.2 to DNN 3.0.12

fatatiba — Fri, 01 Apr 2005 00:22:02 GMT

I am having the same issue.

DNN Core Team ...... PLEASE HEEEEEEEEEEEEEEEELP ....

why the GetTabByName procedure get deleted from the database and then used in while the upgrade is still ongoing.

Re: Upgrade from DNN 2.1.2 to DNN 3.0.12

klunde — Thu, 31 Mar 2005 06:31:22 GMT

I'm also facing this ( 'Stored procedure 'dbo.GetTabByName' not found.) error during my upgrade test.

I have no dnn.config files anywhere.
I've tried to install the new files on top of the old ones.
I've tried to install the new files without the old ones.

The install log indicates that this happens during "Performing General Upgrades"

00:00:12.640 - Upgrading to Version: 3.0.12
00:00:12.812 - Performing General Upgrades

A check in my database shows me that the procudere GetTabByName no longer exists so it seems to me that it either is deleted to soon or another procedure should be used at this point.

Any suggestions on how to get around this error?

Re: Upgrade from DNN 2.1.2 to DNN 3.0.12

dandrade — Wed, 30 Mar 2005 19:02:06 GMT

I have had the "'Stored procedure 'dbo.GetTabByName' not found." in the past. It happened while upgrading from 1.x to 2.x. I can see I am having the same problem now in 2.x to 3.x upgrade.

I have not been able to upgrade. But, I know now my problem have to do with Collation. So, that is what I am dealing with now. Check your DB. It could also have collation problems.

Re: Upgrade from DNN 2.1.2 to DNN 3.0.12

darthrichburg — Wed, 30 Mar 2005 16:54:14 GMT

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?

Re: Upgrade from DNN 2.1.2 to DNN 3.0.12

phebous — Tue, 29 Mar 2005 17:54:54 GMT

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...

Re: Upgrade from DNN 2.1.2 to DNN 3.0.12

adefwebserver — Tue, 29 Mar 2005 16:50:49 GMT

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?