For sharing thank you very much good very beautiful work

thanks, I learn a lot from this Blog. Keep up the good work!!!

hi,

it's me again, Stephen, and I did have a change to try to upgrade my existing DNN 4.6 to 5.0, however, it presents me with errors :( I guess this is pertaining the permissions on the root that is not granted properly. Luckily, I have backup and I can restore my site back.

I like to thank Support Team at asphostdirectory.com who has done excellent job in restoring my site. They even upgrade the DNN for me and certainly, by just paying roughly $6.99/month, I will happy to recommend their service to others :)

One lesson learnt: The permission of the root folder must always be set properly. The READ and WRITE must always be enabled after you uncompress the new DNN installation files. If you have errors during the upgrade, it will take a lot of time to debug and therefore, it is necessary to get it right straight away!

All the best!

Comments from the following blog entry: Installing and Upgrading to Most Current DNN Versions, located at: http://www.mitchelsellers.com/blogs/articletype/articleview/articleid/294.aspx

Comments from the following blog entry: Installing and Upgrading to Most Current DNN Versions, located at: http://www.mitchelsellers.com/blogs/articletype/articleview/articleid/294.aspx

I'm currently using DNN 4.9.1 along with my own custom modules and third party modules. Do you know of any issues with module backward compatibility?

hey mitchel, i have tried to upgrade from 5.0 to 5.0.1 and am having issues. i copied the upgrade files over and left my current web config file which it seems from the post will be upgraded in the process. when i go to the www.mddigest.com address i get the under construction. when i go to the install link that you have in the directions i get Unable to cast object of type 'System.Web.Configuration.ScriptingAuthenticationServiceSection' to type 'System.Web.Configuration.ScriptingAuthenticationServiceSection'.

any thoughts?

Hi Mitchek !
Great post, it works...but, but, but following upgrading 4.9.x to 5.0.1 i can't loging on... nothing... here is my url to test : www-01.altidia.com
thanks to help
Thierry

Followed you procedure and the site worked correctly except for the admin and host menus.
1. Image links were broken- had the skins developer provide a new updated skin set which fixed that.
2. Extensions, Dashboard and whats new are missing from the menus.

/install/install.aspx?mode=install returns nothing.

/install/install.aspx?mode=installresources returned:

00:00:00.015 - Installing Optional Modules:
00:00:00.015 - Installing Optional Skins:
00:00:00.015 - Installing Package File DNN-MinimalExtropySkin_01.00.02_Install: Success
00:00:01.029 - Installing Optional Containers:
00:00:01.029 - Installing Package File DNN-MinimalExtropyContainer_01.00.02_Install: Success
00:00:01.076 - Installing Optional Languages:
00:00:01.076 - Installing Optional Providers:
00:00:01.076 - Installing Package File AspNetMembershipProvider_05.00.01_Install: Success
00:00:01.591 - Installing Package File DatabaseLoggingProvider_05.00.00_Install: Success
00:00:01.637 - Installing Package File DNNMembershipProvider_05.00.01_Install: Success
00:00:01.684 - Installing Package File DNNMenuNavigationProvider_05.00.01_Install: Success
00:00:01.731 - Installing Package File DNNTreeNavigationProvider_05.00.00_Install: Success
00:00:01.762 - Installing Package File FckHtmlEditorProvider_02.00.03_Install: Success
00:00:02.776 - Installing Package File FileBasedCachingProvider_05.00.01_Install: Success
00:00:02.807 - Installing Package File SchedulingProvider_05.00.01_Install: Success
00:00:02.823 - Installing Package File SearchIndexProvider_05.00.00_Install: Success
00:00:02.885 - Installing Package File SearchProvider_05.00.00_Install: Success
00:00:02.917 - Installing Package File SolpartMenuNavigationProvider_05.00.01_Install: Success
00:00:02.948 - Installing Optional AuthSystems:
00:00:02.948 - Installing Package File LiveID_01.00.01_Install: Success
00:00:03.026 - Installing Package File OpenID_02.00.00_Install: Success
00:00:03.088 - Installing Optional Packages:

Installation Complete

-Any suggestions?

Larry,

I would roll back to your old version. Update the skin, then try the upgrade again.

If you need further assistance, please move the discussion to the forums.

Thanks!

Thanks Mitchell,
That did the trick!
-Larry

thanks

Hi ,
I am trying to upgrade a DNN Site from 4.9.0 to 5.0.1 and facing a issue. The upgrade is carried out as the normal process and it gives to Upgrade Sucess message and I am able to login to site as Normal user. But when tried to login with Host Account the site is not allowing me login. It gives an error message saying the Dotnetnuke.Modules.Admin namspace missing.

Please help its very urgent.

Hi Mitchel,

I followed your instructions to upgrade a DNN 4.9.2 site to 5.1.0 but when I started the installation procedure, it almost immediately threw the following error:

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

Could not load file or assembly 'RUNN640~' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
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.IO.FileLoadException: Could not load file or assembly 'RUNN640~' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

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.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'RUNN640~' could not be loaded.


WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].



Stack Trace:


[FileLoadException: Could not load file or assembly 'RUNN640~' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]
System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0
System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +43
System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +127
System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +142
System.Reflection.Assembly.Load(String assemblyString) +28
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +46

[ConfigurationErrorsException: Could not load file or assembly 'RUNN640~' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +613
System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +203
System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +105
System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +178
System.Web.Compilation.BuildProvidersCompiler..ctor(VirtualPath configPath, Boolean supportLocalization, String outputAssemblyName) +54
System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed) +8809426
System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories) +128
System.Web.Compilation.BuildManager.CompileResourcesDirectory() +31
System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +304

[HttpException (0x80004005): Could not load file or assembly 'RUNN640~' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]
System.Web.Compilation.BuildManager.ReportTopLevelCompilationException() +58
System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +512
System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters) +729

[HttpException (0x80004005): Could not load file or assembly 'RUNN640~' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +8890735
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +85
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +259




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

I Googled the error with no success and got nowhere with Rackspace (Mosso) support. I found one generalized mention of a similar error on the MS ASP.NET forum that had a reply of:

"ran "c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i" which solved the problem"

Do you have any insight on how to resolve this? I extracted the 5.1.0 Upgrade over the DNN files. If its an IIS issue, I don't know how to get Rackspace to deal with it.

Thanks for any help or clues on this.

Frank

Greetings from Austria

Last weekend I tried to upgrade my site from 4.9.0 to 5.1.0.
Boy-oh-Boy. Now, THAT went wrong. My Database model has been completely corrupted afterwards. (Took a look at the sql-providers, but couldn't figure out exactly what went wrong).
Now trying to go to 4.9.4 first and then to 5.1.0

Cheers,
Martin

Yes, thanks! You have taken the guesswork out of the upgrade process and made this a lot less painful that it would othewise be!

I just upgraded 5.1 to 5.1.1 and it did not go well. I get an error message. Please provide some guidance on getting my site back up.


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

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".











Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL.

This has been a phenomenal guide to upgrading EXCEPT that it doesn't work well for upgrading to any of the 5.X versions, IMHO.

Trying to upgrade to 5.X has been nothing but one horror story after another. My advice is to NOT try to UPGRADE to any current version of 5.X until they have gotten all the bugs worked out and are at version 5.5 or greater! Check out the DNN forums--there are upgrade issues posted everyday. And I have yet to be able to attempt a successful upgrade from 4.x to 5.x.

John,

I can feel your pain, upgrades are easier now with the 5.1.1 release, but the success rate does still seem to vary. I'm still doing testing on internal sites to see exactly the "best" way to upgrade.

thank you!

Nice post, thanks!

Tank you, work perfektly!

The upgrade from DNN 4.9 to 5.01.02 worked perfectly. Thanks for the post.

Comments from the following blog entry: Actualizando a DotNetNuke 5, located at: http://www.dotnetnukeole.com/Blog/tabid/267/ID/73/Actualizando-a-DotNetNuke-5.aspx

How to upgrade to DNN 5.2.0 ? Is the above process sufficient for upgrading from DNN 4.8.x / 5.1.4 Upwards ?

I am attempting to bring a very old DNN 2.0 site to the current version 5.2.0. Would I be better off just moving the content manually?

@bill - It can be done, but depending on the size of the site, a fresh install could be faster.

I am about to upgrade from DNN 4.8.3 to DNN 5.2.2. I will disable PageBlaster and iFinity modules! Are your instructions to just overlay the files using the "Upgrade Kit" still valid?

I have heard recommendations to go to 4.9.5 first, but DNN doesn't seem to keep the old kits online any more.

/Dave Snow

I did my first few attempts that upgrading today. The process was:
1. Backup files and database at PowerDNN
2. Copy zip file to local host (have to stop/restart IIS and sometimes reboot to
Delete files.) Note: I already have a old local copy working on the localhost/ASI3
3. Restore files.
Delete old local database and create/restore the PowerDNN backup database
Add ASPNET as database user with db_owner rights
4. Edit web.config to:
Local database info
Disable PageBlaster and iFinity’s Friendly URL
Enable debugging
5. In Firefox goto http://localhost/asi3 to test that the site works ok, which it does
6. Unzip the Upgrade version of DNN522 in a directory and copy the files into the web root of my localhost site.
7. goto http://localhost/ASI3 and watch the upgrade occur

8. Try to fix errors and loop thru this process as needed = Yuk

My log files show the same error while upgrading:
System.Data.SqlClient.SqlException: Cannot find the object 'NTForums_GetForumsByGroup2', because it does not exist or you do not have permission.
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 Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters)
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText)
at DotNetNuke.Data.SqlDataProvider.GrantStoredProceduresPermission(String Permission, String LoginOrRole)

if exists (select * from dbo.sysusers where name='public') begin declare @exec nvarchar(2000) declare @name varchar(150) declare sp_cursor cursor for select o.name as name from dbo.sysobjects o where ( OBJECTPROPERTY(o.id, N'IsProcedure') = 1 or OBJECTPROPERTY(o.id, N'IsExtendedProc') = 1 or OBJECTPROPERTY(o.id, N'IsReplProc') = 1 ) and OBJECTPROPERTY(o.id, N'IsMSShipped') = 0 and o.name not like N'#%%' and (left(o.name,len('')) = '' or left(o.name,7) = 'aspnet_') open sp_cursor fetch sp_cursor into @name while @@fetch_status >= 0 begin select @exec = 'grant EXECUTE on [' + @name + '] to [public]' execute (@exec) fetch sp_cursor into @name end deallocate sp_cursor end

The rest of the log looks ok except that the “Community line” just has an error.

When I goto to the site I get
Line 119: Public Overrides Function GetHtmlText(ByVal moduleId As Integer) As IDataReader
Line 120: Return CType(SqlHelper.ExecuteReader(ConnectionString, DatabaseOwner & ObjectQualifier & "GetHtmlText", moduleId), IDataReader)
Line 121: End Function


Removing Active Forums which I don’t use and “appears” to be part of the database problem doesn’t help.

Any suggestions?

I am running a single dnn 04.09.00 installations with several parent portals attached. Do you think I will have any trouble with the above method of upgrading to 5.0.0?

Hi Mitchel, I am Christian from Argentina.
I want to ask you if you have a post where talk about of upgrading to 5.4.3 (lastest) from 4.7 or this post works for that.
Please can you help me with this?

The process is still the same

I followed your instructions here to upgrade from 4.7 to 5.2 but I've run into some errors. Anything you can tell me from this?

Upgrading DotNetNuke
Current Assembly Version: 05.02.03
Current Database Version: 04.07.00


Upgrade Status Report
00:00:00.015 - Upgrading to Version: 05.02.03
00:00:00.062 - Executing Script: 04.08.00.SqlDataProvider Error! (see 04.08.00.log for more information)
00:00:12.344 - Executing Script: 04.08.01.SqlDataProvider Error! (see 04.08.01.log for more information)
00:00:13.954 - Executing Script: 04.08.02.SqlDataProvider Error! (see 04.08.02.log for more information)
00:00:15.688 - Executing Script: 04.09.00.SqlDataProvider Error! (see 04.09.00.log for more information)
00:00:17.392 - Executing Script: 04.09.01.SqlDataProvider Error! (see 04.09.01.log for more information)
00:00:19.017 - Executing Script: 05.00.00.SqlDataProvider Error! (see 05.00.00.log for more information)
00:00:23.689 - Executing Script: 05.00.01.SqlDataProvider Error! (see 05.00.01.log for more information)
00:00:25.924 - Executing Script: 05.01.00.SqlDataProvider Error! (see 05.01.00.log for more information)
00:00:29.393 - Executing Script: 05.01.01.SqlDataProvider Error! (see 05.01.01.log for more information)
00:00:31.205 - Executing Script: 05.01.02.SqlDataProvider Error! (see 05.01.02.log for more information)
00:00:32.784 - Executing Script: 05.01.03.SqlDataProvider Error! (see 05.01.03.log for more information)
00:00:34.315 - Executing Script: 05.01.04.SqlDataProvider Error! (see 05.01.04.log for more information)
00:00:35.893 - Executing Script: 05.02.00.SqlDataProvider Error! (see 05.02.00.log for more information)
00:00:39.409 - Executing Script: 05.02.01.SqlDataProvider Error! (see 05.02.01.log for more information)
00:00:41.081 - Executing Script: 05.02.02.SqlDataProvider Error! (see 05.02.02.log for more information)
00:00:42.581 - Executing Script: 05.02.03.SqlDataProvider Error! (see 05.02.03.log for more information)
00:00:44.457 - Executing Application Upgrades: 04.08.00 Success
00:00:44.457 - Executing Application Upgrades: 04.08.01 Success
00:00:44.457 - Executing Application Upgrades: 04.08.02 Success
00:00:44.472 - Executing Application Upgrades: 04.09.00 Success
00:00:44.472 - Executing Application Upgrades: 04.09.01 Success
00:00:44.472 - Executing Application Upgrades: 05.00.00 Error!
00:00:50.754 - Executing Application Upgrades: 05.00.01 Success
00:00:50.770 - Executing Application Upgrades: 05.01.00 Success
00:00:55.036 - Executing Application Upgrades: 05.01.01 Success
00:00:55.098 - Executing Application Upgrades: 05.01.02 Success
00:00:55.098 - Executing Application Upgrades: 05.01.03 Success
00:00:55.551 - Executing Application Upgrades: 05.01.04 Success
00:00:55.551 - Executing Application Upgrades: 05.02.00 Success
00:00:55.708 - Executing Application Upgrades: 05.02.01 Success
00:00:55.723 - Executing Application Upgrades: 05.02.02 Success
00:00:55.723 - Executing Application Upgrades: 05.02.03 Success
00:00:55.723 - Cleaning Up Files: 04.08.00 Success
00:00:55.723 - Cleaning Up Files: 04.08.01 Success
00:00:55.754 - Cleaning Up Files: 04.08.02 Success
00:00:55.770 - Cleaning Up Files: 04.09.00 Success
00:00:56.489 - Cleaning Up Files: 04.09.01 Success
00:00:56.489 - Cleaning Up Files: 05.00.00 Success
00:01:00.364 - Cleaning Up Files: 05.00.01 Success
00:01:00.630 - Cleaning Up Files: 05.01.00 Success
00:01:01.958 - Cleaning Up Files: 05.01.01 Success
00:01:01.958 - Cleaning Up Files: 05.01.02 Success
00:01:01.958 - Cleaning Up Files: 05.01.03 Success
00:01:01.958 - Cleaning Up Files: 05.01.04 Success
00:01:01.958 - Cleaning Up Files: 05.02.00 Success
00:01:01.958 - Cleaning Up Files: 05.02.01 Success
00:01:01.958 - Cleaning Up Files: 05.02.02 Success
00:01:01.958 - Cleaning Up Files: 05.02.03 Success
00:01:01.958 - Updating Config Files: 04.08.00 Success
00:01:01.958 - Updating Config Files: 04.08.01 Success
00:01:01.958 - Updating Config Files: 04.08.02 Success
00:01:01.958 - Updating Config Files: 04.09.00 Success
00:01:01.974 - Updating Config Files: 04.09.01 Success
00:01:01.974 - Updating Config Files: 05.00.00 Success
00:01:01.974 - Updating Config Files: 05.00.01 Success
00:01:01.974 - Updating Config Files: 05.01.00 Success
00:01:01.974 - Updating Config Files: 05.01.01 Success
00:01:01.974 - Updating Config Files: 05.01.02 Success
00:01:01.974 - Updating Config Files: 05.01.03 Success
00:01:01.974 - Updating Config Files: 05.01.04 Success
00:01:01.974 - Updating Config Files: 05.02.00 Success
00:01:01.974 - Updating Config Files: 05.02.01 Error!
00:01:02.036 - Updating Config Files: 05.02.02 Success
00:01:02.036 - Updating Config Files: 05.02.03 Success
00:01:02.036 - Performing General Upgrades
00:01:02.396 - Installing Optional Modules:
00:01:02.396 - Installing Package File HTML_Community_05.02.00_Install: Error!
00:01:04.990 - Installing Optional Skins:
00:01:04.990 - Installing Optional Containers:
00:01:04.990 - Installing Optional Languages:
00:01:05.005 - Installing Optional Providers:
00:01:05.005 - Installing Package File AspNetMembershipProvider_05.02.00_Install: Success
00:01:05.271 - Installing Package File CorePermissionProvider_05.01.01_Install: Success
00:01:06.084 - Installing Package File DatabaseLoggingProvider_05.01.01_Install: Success
00:01:06.287 - Installing Package File DNNMembershipProvider_05.01.03_Install: Success
00:01:06.974 - Installing Package File DNNMenuNavigationProvider_05.01.00_Install: Success
00:01:07.240 - Installing Package File DNNTreeNavigationProvider_05.01.00_Install: Success
00:01:07.381 - Installing Package File FckHtmlEditorProvider_02.00.04_Install: Success
00:01:53.994 - Installing Package File FileBasedCachingProvider_05.01.03_Install: Success
00:01:54.119 - Installing Package File FileModuleCachingProvider_05.02.01_Install: Success
00:01:54.322 - Installing Package File MemoryModuleCachingProvider_05.02.01_Install: Success
00:01:54.572 - Installing Package File SchedulingProvider_05.02.01_Install: Success
00:01:54.666 - Installing Package File SearchIndexProvider_05.01.00_Install: Success
00:01:54.775 - Installing Package File SearchProvider_05.01.01_Install: Success
00:01:54.994 - Installing Package File SolpartMenuNavigationProvider_05.01.00_Install: Success
00:01:55.182 - Installing Optional AuthSystems:
00:01:55.182 - Installing Package File LiveID_01.00.01_Install: Success
00:01:55.791 - Installing Package File OpenID_02.00.00_Install: Success
00:01:56.026 - Installing Optional Packages:

Nancy - You will need to look at the details in each of the script error files referenced.

It works great! No problems at all.

Hi Mithcel,

I am having a similar problem with upgrading from 4.9.5 to 5.2.0. Using the upgrade package, the process has worked fine apart from this error
Installing Package File HTML_Community_05.02.00_Install: Error!

Any advice will be highly appreciated.
Thanks

Rajesh,

You will need to review the error log file that was created during the upgrade to see why the HTML module install failed.