Hello Lee and Joe,

Maybe you can help me out here. I have been struggling trying to upgrade my DNN install from 5.2.3 on my local computer running windows 7 ultimate with iis7.5.

Let me tell you what I have done thus far. I have managed to get my site to resolve locally however I find when I upgrade I must upgrade via integrated mode and I mucst view the site in classic mode. I am not sure if I have to view the site in classic mode before I get some sort of upgrade to take but I certainly know I do after the fact.

I have further learned that this is do to something arcaic in either my module, skin, or provider most likely if it is the skin it is some skin object that later DNN versions don't like after 5.3.0.0.

Now I have uploaded for you a couple snapshots of the upgrade I took for both 5.4.0.0 and 5.4.2. They have the txt extension as does the web.config file I uploaded for you to view which reflects the DNN 5.4.2 upgrade just take the txt off that and you can view this as well.

I have stripped some of the stuff out of this web.config file such as the connection string so that the names are generic but just know that the real one does have the correct credentials. I tell you this so that when you take a look at this you won't come to the conclusion that this is why I am getting the error in regards to the config 5.3.0.0.

After this first error I get a few Telerik errors as well as a sitemap error not rendering properly.

I believe that if the config error showing up in the snapshot first was resolved than the rest of the errors would most likely go away.

I know that I do have some older modules and skins on my install hence the need to run in classic mode once I upgraded past 5.3.0.0 but my question is two fold.

1. is there anything in the web.config file that is causing the upgrade to error out
2. If not do you think that the bottom line that is triggering this upgrade issue is in fact a module or skin object or perhaps provider and until I get this ironed out I won't get the config int he 5.3.0.0 to be successful.

Thank you so much for any help you can provide,

Bo

As I was looking at the images I just uploaded for you I realized from 5.4.0 to 5.4.2 I didn't see a config error of 5.3.0 but I am certain this error existed when I jumped from 5.2.3 to the next spot layed out in the DNN upgrade path which was DNN 5.4.4.


As I move up in the upgrade path these errors seen in the snapshots wouldn't just evaporate would they. I would Assume I need to deal with them right from the get go at the first upgrade that came from an install that had no errors during previous upgrades.

I can deal with the integrated vs classic later in regards to not being able to view my site in integrated mode unless as I stated in the question above this is part of the problem for the error seen in the snapshot.

If you look in Providers\DataProviders\SqlDataProvider you will find some .log files. This is where you look to see the errors.

Since these are errors with upgrades to the SQL data providers, these may or may not be related to modules. You will have to look and see.

Since you did a second upgrade, some of this may have been overwritten.

I would recommend that you roll back to the 5.4.0 site and do the upgrade again. Make sure that you locate and copy ALL of the errors and that you not proceed until you have fixed them.

Look here for the suggested upgrade path: http://www.dotnetnuke.com/Resources..._Path.aspx

Since you start at 5.2.3, I'm not quite sure what to suggest. Maybe try to get to 5.4.4 in one step. That will get you to a version that is on the suggested path. If that doesn't work, drop back and do one stable release at a time until you get to 5.4.4.

Let me know how this goes and maybe I can give you some other suggestions. But ... looking at the actual problems as they occur is a good start.

Hay Joseph one last observation I have noticed about this upgrade and that is that I find that I have to upgrade my site in integrated pipeline rather than classic pipeline but I can't view my site in integrated as I either get an error via my localhost or if powerdnn changes the same install pipeline to integrated I run into issues with the DNNnavigationalprovider that the sin object NAV points to in skins.

Now if I try to upgrade my site in classic mode I get numerous errors starting with a Telerik error where one spot in a vb file is referencing one Telerik version whrere another spot (the web.config file) is refrencing a different instance of this. Now in this case if I manually copy both the Telerik.web.ui file from the bin directory and copy and paste the binding redirect line for Telerik from the web.config file found in the full install folder of whatever version I am upgrading to than that error goes away but the next one that follows is that the stored procedure getportaldefaultlanguage cannot be found. When I recreate this procedure in my database than I get that my dbo.portals is not valid and that is where I get stuck if trying to upgrade in classic pipeline and consequently the upgrade process never starts.

Now when I upgrade in integrated mode I get none of this but rather the upgrade engine starts upgrading successfully up to of course this config issue.

I was actually posting this reply just as you were replying to my post and yes I did try to jump from 5.2.3 to 5.3.1 and when I did this there was no telerik errors but only two which were that config 05.03.00 error and a sitemap provider error for 05.02.00 but even using the recommended upgrade path starting from 5.2.3 to 5.3.1 I still get that config error and sitemap provider error.

I haven't really observed what would happen if I hopped from 5.3.1 to 5.4.4 if I would continue to just get the config and sitemap error or if added to that would be all these telerik errors like I was getting when I hopped over 5.3.1 and went to 5.4.4. By the way when I did this hopping I did try to hop from 5.2.3 to 5.4.0 as well as 5.4.2 as can be seen from the snapshots I took but I didn't go from 5.2.3 to 5.3.1 to 5.4.0 or 5.4.4 for that matter.

should it be normal that I have to change pieplines in iis in order to start the upgrade engine properly and than change it back to classic to view the website? This really doesn't make much sense since you can't expect a hosting company like powerdnn to keep changing the pipeline in their app pool for you just so you can get the upgrade engine to start and so it will automatically integrate these telerik lines, and procedures like that getportaldefaultlanguage that never got integrated when upgrading using classic pipeline.

My last question is when I am running under integrated pipeline within powerdnn I find that my menu which is using the dnnnavigational provider seems a bit quirky in that when you hit f5 to refresh the site the dnnnavigational menu disappears and for some it never does appear however when powerdnn switches the pipeline to classic view the menu appears and the quirkiness stops. I am wondering should I be considering switching Navigational providers because of this? Bottom line I guess is should I be trying to get it so my site can run under integrated pipeline without any quirks. I noticed in Lee Sykes Tutorial about fresh install on a windows 7 computer in recommended switching the pool to classic.net which by default changes the pipeline from integrated to classic so I am assuming you guys are recommending the use of classic pipeline.

In conclusion I am wondering when DNN 6 becomes more stable with a realease of 6.0.1 do you have any idea if I site must run under integrated pipeline once migrated to DNN 6. I have heard somewhere that starting with DNN 6 the site will no longer run properly under the classic pipeline which simulates iis5 and iis6 but just curious what your thoughts are on this.

Thanks,

Bo

Hay Joe and others,

I was going to send you a snapshot of the upgrade progress from 5.2.3 to 5.3.1 (the next stepping stone) so you could see the errors I was describing above but when I looked to add the attachment I couldn't find the option. How can I add an attachment to a reply to a thread. Can an attachment only be done when opening a new thread, could I edit the initial thread topic to allow for another attachment not added when first opening a topic.

Thanks let me know and I'll touch base again Joe when I start digging at those log files to see what I can come up with.

Thanks,

Bo

Hello Joe:

I just checked out the log files that were generated just after this 5.2.3 to 5.3.1 upgrade and I can't see that anything was logged. I opened the file found in providers/DataProviders/SqlDataProvider and the two log files that were generated (05.03.00 and 05.3.1.0.0 were empty. Any other suggestions?

I am going to now try to upgrade to 5.4.4 just to see if those telerik errors start up or maybe I would be wiser to try to upgrade to 5.4.0 than 5.4.2 and than 5.4.4 to see if these telerik issues start emerging either way I would suspect that this config file issue would still be problematic as well as the failing of the CoreSitemapProvider_5.2.0.0_Install.

Here are the exact two errors that appeared when upgrading to 05.03.00:

Updating Config Files: 05.03.00 Error!

CoreSitemapProvider_5.2.0.0_Install: Error!

revision those two errors occured when upgrading to 05.3.1 not 05.03.0.0

In all honesty, I don't know the answer to the integrated/pipeline mode. You might want to ask PowerDNN about that, and you might also want ask over on the DotNetNuke forums.

I don't have any trouble moving sites to and from PowerDNN. But, I'm mostly doing that on Windows Server machines. I don't think, though, that it should depend on the IIS setup.

I'm assuming that you have a site on PowerDNN. What version is that installation?

Might be a good idea to grab a clean copy of that, get it running on your local site, and then start going through the upgrades again.

Ok Joe,

Just went from 5.3.1 to 5.4.0 (after the iteration to 5.3.1 from 5.2.3) and I got the following upgrade details

-------------------------------------------------------------------------------------------------------------------------------------------
00:00:00.023 - Upgrading to Version: 05.04.00
00:00:00.103 - Executing Script: 05.04.00.SqlDataProvider Success
00:00:00.722 - Executing Application Upgrades: 05.04.00 Success
00:00:01.852 - Cleaning Up Files: 05.04.00 Success
00:00:01.855 - Updating Config Files: 05.04.00 Success
00:00:01.855 - Performing General Upgrades
00:00:01.935 - Installing Optional Modules:
00:00:01.940 - Installing Package File HTML_Community_05.02.00_Install: Success
00:00:02.216 - Installing Package File Messaging_01.01.00_Install: Success
00:00:02.446 - Installing Package File Taxonomy_01.01.00_Install: Success
00:00:02.590 - Installing Package File Telerik_05.04.00_Install: Error!
00:00:03.228 - Installing Optional Skins:
00:00:03.228 - Installing Optional Containers:
00:00:03.228 - Installing Optional Languages:
00:00:03.229 - Installing Optional Providers:
00:00:03.229 - Installing Package File AspNetMembershipProvider_05.02.00_Install: Success
00:00:03.261 - Installing Package File CorePermissionProvider_05.01.01_Install: Success
00:00:03.292 - Installing Package File CoreSitemapProvider_5.2.0.0_Install: Error!
00:00:03.358 - Installing Package File DatabaseLoggingProvider_05.01.01_Install: Success
00:00:03.391 - Installing Package File DNNMembershipProvider_05.01.03_Install: Success
00:00:03.425 - Installing Package File DNNMenuNavigationProvider_05.01.00_Install: Success
00:00:03.467 - Installing Package File DNNTreeNavigationProvider_05.01.00_Install: Success
00:00:03.496 - Installing Package File FckHtmlEditorProvider_02.00.04_Install: Success
00:00:05.278 - Installing Package File FileBasedCachingProvider_05.01.03_Install: Success
00:00:05.317 - Installing Package File FileModuleCachingProvider_05.02.01_Install: Success
00:00:05.369 - Installing Package File MemoryModuleCachingProvider_05.02.01_Install: Success
00:00:05.399 - Installing Package File SchedulingProvider_05.02.01_Install: Success
00:00:05.433 - Installing Package File SearchIndexProvider_05.01.00_Install: Success
00:00:05.464 - Installing Package File SearchProvider_05.01.01_Install: Success
00:00:05.488 - Installing Package File SolpartMenuNavigationProvider_05.01.00_Install: Success
00:00:05.524 - Installing Package File TelerikEditorProvider_05.04.00_Install: Error!
00:00:05.708 - Installing Optional AuthSystems:
00:00:05.709 - Installing Package File LiveID_01.00.01_Install: Success
00:00:05.752 - Installing Package File OpenID_02.00.00_Install: Success
00:00:05.799 - Installing Optional Packages:
-------------------------------------------------------------------------------------------------------------------------
When I tried to jump from 5.3.1 to the upgrade path of 5.4.4 I got more errors than seen here.

Again once I jumped to view the log for this upgrade it was blank. Notice however in this case the config file for 5.04.00 was successful unlike the .05.03.0.0 one. Maybe these errors just iron themeselves out as you go up the path but I am concerned about the new Telerik errors that surface from 5.3.1 to 5.4.0 as this could cripple the telerik provider for using the html module

Hello Joe,

I have 5.2.3 running on powerdnn in fact I have already done as you suggested I brought down a backup they specifically made for me manually since the one I did via the backup manager on their Plesk Control Panel got corrupted and they told me this can happen if you aren't using Plesk to interface with your IIS 7.5 so they just went ahead and made this backup for me manually not using Plesk to do it.

At any rate I have tried the upgrade several times and using different version upgrades from 5.2.3 but get these errors anyway.

Now I will say this that I found that when I first downloaded the fresh backup from powerdnn that I did have to go into my site and uninstall two modules as it was interfering with my upgrade and that is the chat module and the xml/xls module. The chat module came off without incident but the xml module had some issues which are seen below

--------------------------------------------------------------------------------------------------------------------------------------------------------------

Info

Reading Component Manifest - Script



Info

Reading Component Manifest - Cleanup



Info

Reading Component Manifest - Cleanup



Info

Reading Component Manifest - Cleanup



Info

Reading Component Manifest - Module



Info

Module Manifest read successfully



Info

Reading Component Manifest - File



Info

Reading Component Manifest - File



StartJob

Starting Package Uninstall



Info

Starting Package Uninstall - DNN_XML



Info

Starting Component Uninstall - Script



Info

Begin Sql UnInstall



Info

Deleted - Providers\DataProviders\SqlDataProvider\03.03.00.SqlDataProvider



Info

Deleted - Providers\DataProviders\SqlDataProvider\03.03.02.SqlDataProvider



Info

Deleted - Providers\DataProviders\SqlDataProvider\04.03.02.SqlDataProvider



Info

Deleted - Providers\DataProviders\SqlDataProvider\04.03.04.SqlDataProvider



Info

Folder Deleted - SqlDataProvider



Info

Folder Deleted - DataProviders



Info

Folder Deleted - Providers



Info

Executing Uninstall.SqlDataProvider



Info

Start Sql execution: Uninstall.SqlDataProvider file



Failure

SQL Execution resulted in following Exceptions: System.Data.SqlClient.SqlException: Cannot drop the procedure 'dbo.stevenson_Xml_Parameter_AddParameter', 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.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) /** Drop Stored Procedures **/ IF EXISTS (SELECT * FROM dbo.sysobjects WHERE id = OBJECT_ID(N'dbo.[stevenson_Xml_Parameter_Add]') AND OBJECTPROPERTY(id, N'IsProcedure') = 1) DROP PROCEDURE dbo.stevenson_Xml_Parameter_AddParameter System.Data.SqlClient.SqlException: Cannot drop the procedure 'dbo.stevenson_Xml_Parameter_GetParameters', 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.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) IF EXISTS (SELECT * FROM dbo.sysobjects WHERE id = OBJECT_ID(N'dbo.[stevenson_Xml_Parameter_GetList]') AND OBJECTPROPERTY(id, N'IsProcedure') = 1) DROP PROCEDURE dbo.stevenson_Xml_Parameter_GetParameters System.Data.SqlClient.SqlException: Cannot drop the procedure 'dbo.stevenson_Xml_Parameter_GetParameter', 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.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) IF EXISTS (SELECT * FROM dbo.sysobjects WHERE id = OBJECT_ID(N'dbo.[stevenson_Xml_Parameter_Get]') AND OBJECTPROPERTY(id, N'IsProcedure') = 1) DROP PROCEDURE dbo.stevenson_Xml_Parameter_GetParameter System.Data.SqlClient.SqlException: Cannot drop the procedure 'dbo.stevenson_Xml_Parameter_UpdateParameter', 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.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) IF EXISTS (SELECT * FROM dbo.sysobjects WHERE id = OBJECT_ID(N'dbo.[stevenson_Xml_Parameter_Update]') AND OBJECTPROPERTY(id, N'IsProcedure') = 1) DROP PROCEDURE dbo.stevenson_Xml_Parameter_UpdateParameter System.Data.SqlClient.SqlException: Cannot drop the procedure 'dbo.stevenson_Xml_Parameter_DeleteParameter', 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.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) IF EXISTS (SELECT * FROM dbo.sysobjects WHERE id = OBJECT_ID(N'dbo.[stevenson_Xml_Parameter_Delete]') AND OBJECTPROPERTY(id, N'IsProcedure') = 1) DROP PROCEDURE dbo.stevenson_Xml_Parameter_DeleteParameter System.Data.SqlClient.SqlException: Incorrect syntax near '*'. at System.Data.SqlClient.SqlConnection.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) DELETE * FROM stevenson_ModuleSettings WHERE SettingName Like N'XML_%' DELETE * FROM stevenson_TabModuleSettings WHERE SettingName Like N'XML_%'



Info

End Sql execution: Uninstall.SqlDataProvider file



Info

Deleted - Uninstall.SqlDataProvider



Info

End Sql UnInstall



Info

Component uninstalled successfully - Script



Warning

Component Uninstalled with Warnings - Script



Info

Starting Component Uninstall - Cleanup



Info

Component uninstalled successfully - Cleanup



Info

Component Uninstall Successful - Cleanup



Info

Starting Component Uninstall - Cleanup



Info

Component uninstalled successfully - Cleanup



Info

Component Uninstall Successful - Cleanup



Info

Starting Component Uninstall - Cleanup



Info

Component uninstalled successfully - Cleanup



Info

Component Uninstall Successful - Cleanup



Info

Starting Component Uninstall - Module



Info

Module un-registered successfully - DNN_XML



Info

Component uninstalled successfully - Module



Info

Component Uninstall Successful - Module



Info

Starting Component Uninstall - File



Info

Deleted - Components\ControllerBase.vb



Info

Deleted - Components\DataProvider.vb



Info

Deleted - Components\GlobalConstants.vb



Info

Deleted - Components\Utils.vb



Info

Deleted - Components\XmlController.vb



Info

Folder Deleted - Components



Info

Deleted - Parameters\ParameterController.vb



Info

Deleted - Parameters\ParameterInfo.vb



Info

Deleted - Parameters\ParameterList.vb



Info

Deleted - Parameters\ParameterType.vb



Info

Folder Deleted - Parameters



Info

Deleted - Providers\DataProviders\SqlDataProvider\SqlDataProvider.vb



Info

Folder Deleted - SqlDataProvider



Info

Deleted - Handlers\download.vb



Info

Folder Deleted - Handlers



Info

Component uninstalled successfully - File



Info

Component Uninstall Successful - File



Info

Starting Component Uninstall - File



Info

Deleted - App_LocalResources\EditXml.ascx.resx



Info

Deleted - App_LocalResources\XmlModule.ascx.resx



Info

Folder Deleted - App_LocalResources



Info

Deleted - Parameters\ParameterEditor.ascx



Info

Deleted - Parameters\ParameterEditor.ascx.vb



Info

Folder Deleted - Parameters



Info

Deleted - download.ashx



Info

Deleted - EditXml.ascx



Info

Deleted - EditXml.ascx.vb



Info

Deleted - XmlModule.ascx



Info

Deleted - XmlModule.ascx.vb



Info

Folder Deleted - XML



Info

Component uninstalled successfully - File



Info

Component Uninstall Successful - File



Warning

Uninstalled with Warnings - DNN_XML



EndJob

Uninstalled with Warnings
--------------------------------------------------------------------------------------------------------------


Now a couple other bizarre things I noticed just this time when I reinstated that fresh backup I had from powerdnn again on my local computer. One is that when I restored the database and my files and tweaked the web.config to reflect the correct connection string to my local computer and a couple other tweaks I noticed that when the site came up it came up logged into my site as host. Maybe I never logged out before I had DNN do the backup for me or perhaps not recycling the app pool locally caused this but it was bizarre never the less.

Anyway the other unique thing that happened locally that did not happen on powerdnn is that if I didn't comment out the module node and the first line of the http nodes I got errors. In the case of the modules I was told by IIS 7.5 that I had a 500.19 internal error and this was do to the fact that I had duplicates in the web.config file and the duplicates were under two different nodes one being modules and the other being httpmodules so I commented out the modules node and than I got another error that said that the first line in my httpmodules had already been added so I commented that out and the site resolved without further incident.

Here is the details of this section of my web.config file so you can see it:

--------------------------------------------------------------------------------------------------------------------------------------------------------------------

<!--








-->


-------------------------------------------------------------------------------------------------------------------------------------------------------------------------'

Here's the other line that I had to comment out in httpmodules node in order to get my install to work on my local computer. I asked powerdnn how come this stuff didn't have to be commented out to work on their server and they didn't have any real good answer for me except that their Plesk Control Panel and admin tools do all the work for them and they really don't know all they are doing behind the scenes so couldn't tell me why this stuff didn't need commenting out on their environmetn. Maybe do to the fact that they had a lot of things under managed where I don't since I have no higher level software like Plesk Control Panel installed that is managing my IIS for me. They also told me that they were running under vmhost or something like that but I don't think that should be a thing I should be concerned about setting up on my local IIS since this is just a development sort of thing that only I do and no other person has to get into.

---------------------------------------------------------------------------------------------------------------

<!-- add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" / -->

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Below is the line I left uncommented and I think this is the line that IIS said was already added so the above was an addition which was unacceptable to the web.config file

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Hopefully this information will be of better service for helping to nail down this upgrade issue. Maybe it wouldn't hurt for me to request from powerdnn another manual backup and insure I am not logged in as host when they do this backup so I can be 100% sure that this was not the case of all these issues.

By the way Joe just wanted to bring this up again in regards to this deal with integrated vs classic pipeline should I have to upgrade under integrated and view my website after upgrade is complete under classic pipeline. I can't imagine I am suppose to have to put in support tickets to powerdnn to make sure they flip the pipeline switch up and down anytime I need to upgrade and than view again. I know under integrated mode my DNNnavigational provider has an issue displaying the menu but under classic mode it does not.

Should I be changing DNN providers and if I upgrade to a newer one should it be able to run under integrated ok. I know in Lee Sykes Tutorial on freshly installing a DNN installation on Windows 7 he switches the app pool to classic.net which also automatically selects the pipeline as classic so I would assume you guys are encouraging running a DNN site on classic piepline which brings me the the next question on this issue.

Starting with DNN 6 when it becomes stable is it true that you are required to be under integrated pipeline when going to DNN 6 or is it still ok to be running your site under classic mode.

I am asking this because I am quite certain I probably have some ancient modules that would need to be gotten rid of in order to make my site work under integrated mode in my local computer. Oddly enough the same fresh copy I download from powerdnn works with quirks on integrated mode on their servers but when I try it on mine in integrated mode is just simply blows up with that instance of an object not referenced error until I switch back over to Classic mode than it goes away.

So would you suggest before I move to DNN 6 when stable that I update my dnnnavigational provider if it should be a goal to try to get a site to run cleanly in integrated pipeline especially going forward through the DNN 6 platform.

Thanks,

Bo

The errors seem to have to do with things like dbo.stevenson_Xml_Parameter_AddParameter. I assume that "stevenson" is your object qualifier. Can you tell if the Xml_Parameter stuff associated with the XML module, or is it associated with a custom module? Are your using the XML module?

If you are not using the XML module, but it is installed ... try deleting it before doing the upgrade.

I'm pretty sure that you should be running the site on Win 7 using the classic AppPool.

See this re integrated pipeline mode: http://www.efficionconsulting.com/B...fault.aspx

But ... the install errors don't have anything to do with that. The fact that the site is running and communicating with the SQL server speaks to that.

In regards to the object qualifier the answer is yes stevenson is that.

Ok Joe here is the module I deleted in regards to xml that gave me the error I described earlier as far as I can see I have no other module.

-----------------------------------------------------------------------------------------------------------------------------
Module Name DNN_Module
Friendly Name:XML/XSL

This module queries XML Data from a file or an http request, transforms the XML data using an XSL transformation and returns the result back to the user.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I looked in my database and before deleting the xml/xls module I found this in the tables in regards to that module.

------------------------------------------------------------------------
dbo.stevenson_Xml_Parameter
------------------------------------------------------------------------

In the stored procedures I have the following:
--------------------------------------------------------
1. dbo.stevenson_Xml_Parameter_Add
2. dbo.stevenson_Xml_Parameter_Delete
3. dbo.stevenson_Xml_Parameter_Get
4. dbo.stevenson_Xml_Parameter_GetList
5. dbo.stevenson_Xml_Parameter_Update

-------------------------------------------------------------
These ocuured all before deleting the module with all its files. Even when I tried to delete it without deleting all files those xml errors were there.

After I deleted the module I noticed that the only module table that existed was gone however all those stored procedure listed above in the numbered list still existed. I did try to experiment with deleting these stored procedures after the uninstallation of the module but it didn't seem to make any difference in the upgrade issue at hand.

Basically their was no other xml parameter stuff than listed and I didn't notice any other XML module I had installed on this database except that one. I had other third party modules a bunch of them especially onyaktech modules but none about xml.

I was afraid perhaps the onyaktech modules were interferring do to the fact that Onyaktech.library and Onyaktech.Nelson Links partially failed but I had brought these modules through the ringer finding that if I deleted all Onyaktech modules but the Onyaktech.library than if that was the last Onyaktech module I deleted it would delete without incident however the Nelson Links one still had issus uninstalling but this didn't help solve the upgrade problem either.

Where do you think I should go next. I am downloading a fresh copy of the database on my live production site from powerdnn.

I must add to this mix that this installation dates back starting at 5.0.1 via sql 2005 express as I started out with ixwebhosting and that is what they had. Than recently I moved over to powerdnn with this install since ixwebhosting was so slow and they migrated it for me into their sql2008R2 servers. The first migration attempt failed as I could not see the login module when I clicked on login but than I had them take those files again and remigrate and it was flawless without incident.

Up all the way through 5.2.3 I had no upgrade issues it just surfaced as of late. Is there any connection between migrating 2005 to 2008R2 that has to do with this issue. But than again I have to say this theory does not hold water for I did try to upgrade it on the ixwebhosting site under sql2005 since my account hasn't expired with them yet and I ran into similar errors and this was the database that DNN was initially installed on so there goes that idea.

Anyway let me know if you have any more thoughts on this.

Also thank you for verifying the classic.net pool thing for me but tell me why do you think that on my local computer I have to move between iis7 pipelines in order to upgrade and view why can't I successfully upgrade under the classic pipeline without having to manually paste telerik.web.ui files from the version I am installing to into the newsly copied filesystem after using the upgrade folder and why is there a need to manually change the bindingredirect as well as all these stored procedrue and invalid dob.portal errors. I can't imagine this is a normal practice to always have to switch to integrated in order for the upgrade wizard to successfully run do you know if there is any information about this being a problem or do you have any insight into this.

Thanks,

Bo

by the way Joe just got another fresh copy from powerdnn and tried that out but find no difference in regards to this error. I am wondering is it possible to get rid of this 05.02.0.0 site may provider since this is causing errors as well. Not sure if there is a way to delete this upgrade and than reinstate it. Of course not sure if this will take care of the problem with the Telerik editor or not.

Thanks,

Bo

Ok Joe,

At least I am pretty sure my upgrade problem is narrowed down to two things one being the Telerik Editor issue and the other being the core sitemap provider other than that the upgrade is successful.

Now I attempted a leap from 5.2.3 to 5.6.2 which well surprisingly well except for those couple errors than I attempted one from 5.2.3 right to 5.6.3 and interestingly enough no more significant errors so I will paste the results from the upgrade that I went from 5.2.3 to 5.6.3 below:

----------------------------------------------------------------------------------------------------------------------------
00:00:00.053 - Upgrading to Version: 05.06.03
00:00:00.102 - Executing Script: 05.03.00.SqlDataProvider Success
00:00:01.600 - Executing Script: 05.03.01.SqlDataProvider Success
00:00:01.628 - Executing Script: 05.04.00.SqlDataProvider Success
00:00:02.064 - Executing Script: 05.04.01.SqlDataProvider Success
00:00:02.098 - Executing Script: 05.04.02.SqlDataProvider Success
00:00:02.264 - Executing Script: 05.04.03.SqlDataProvider Success
00:00:02.328 - Executing Script: 05.04.04.SqlDataProvider Success
00:00:02.334 - Executing Script: 05.05.00.SqlDataProvider Success
00:00:04.975 - Executing Script: 05.05.01.SqlDataProvider Success
00:00:04.995 - Executing Script: 05.06.00.SqlDataProvider Success
00:00:06.110 - Executing Script: 05.06.01.SqlDataProvider Success
00:00:06.182 - Executing Script: 05.06.02.SqlDataProvider Success
00:00:07.186 - Executing Script: 05.06.03.SqlDataProvider Success
00:00:07.218 - Executing Application Upgrades: 05.03.00 Success
00:00:09.765 - Executing Application Upgrades: 05.03.01 Success
00:00:09.765 - Executing Application Upgrades: 05.04.00 Success
00:00:10.018 - Executing Application Upgrades: 05.04.01 Success
00:00:10.018 - Executing Application Upgrades: 05.04.02 Success
00:00:10.018 - Executing Application Upgrades: 05.04.03 Success
00:00:10.033 - Executing Application Upgrades: 05.04.04 Success
00:00:10.033 - Executing Application Upgrades: 05.05.00 Success
00:00:10.217 - Executing Application Upgrades: 05.05.01 Success
00:00:10.217 - Executing Application Upgrades: 05.06.00 Success
00:00:10.330 - Executing Application Upgrades: 05.06.01 Success
00:00:10.331 - Executing Application Upgrades: 05.06.02 Success
00:00:10.355 - Executing Application Upgrades: 05.06.03 Success
00:00:10.358 - Cleaning Up Files: 05.03.00 Success
00:00:10.366 - Cleaning Up Files: 05.03.01 Success
00:00:10.366 - Cleaning Up Files: 05.04.00 Success
00:00:10.367 - Cleaning Up Files: 05.04.01 Success
00:00:10.367 - Cleaning Up Files: 05.04.02 Success
00:00:10.367 - Cleaning Up Files: 05.04.03 Success
00:00:10.367 - Cleaning Up Files: 05.04.04 Success
00:00:10.367 - Cleaning Up Files: 05.05.00 Success
00:00:10.368 - Cleaning Up Files: 05.05.01 Success
00:00:10.368 - Cleaning Up Files: 05.06.00 Success
00:00:10.371 - Cleaning Up Files: 05.06.01 Success
00:00:10.371 - Cleaning Up Files: 05.06.02 Success
00:00:10.371 - Cleaning Up Files: 05.06.03 Success
00:00:10.373 - Updating Config Files: 05.03.00 Error!
00:00:10.389 - Updating Config Files: 05.03.01 Success
00:00:10.389 - Updating Config Files: 05.04.00 Success
00:00:10.390 - Updating Config Files: 05.04.01 Success
00:00:10.390 - Updating Config Files: 05.04.02 Success
00:00:10.390 - Updating Config Files: 05.04.03 Success
00:00:10.390 - Updating Config Files: 05.04.04 Success
00:00:10.390 - Updating Config Files: 05.05.00 Error!
00:00:10.395 - Updating Config Files: 05.05.01 Success
00:00:10.395 - Updating Config Files: 05.06.00 Success
00:00:10.398 - Updating Config Files: 05.06.01 Success
00:00:10.406 - Updating Config Files: 05.06.02 Success
00:00:10.407 - Updating Config Files: 05.06.03 Success
00:00:10.412 - Performing General Upgrades
00:00:10.511 - Installing Optional Modules:
00:00:10.516 - Installing Package File HTML_Community_05.06.03_Install: Success
00:00:11.227 - Installing Package File Messaging_05.06.03_Install: Success
00:00:11.300 - Installing Package File Taxonomy_05.06.03_Install: Success
00:00:11.399 - Installing Package File Telerik_05.06.03_Install: Error!
00:00:12.168 - Installing Optional Skins:
00:00:12.168 - Installing Optional Containers:
00:00:12.168 - Installing Optional Languages:
00:00:12.169 - Installing Optional Providers:
00:00:12.169 - Installing Package File AspNetMembershipProvider_05.06.03_Install: Success
00:00:12.225 - Installing Package File CorePermissionProvider_05.06.03_Install: Success
00:00:12.272 - Installing Package File CoreSitemapProvider_05.06.03_Install: Error!
00:00:12.324 - Installing Package File DatabaseLoggingProvider_05.06.03_Install: Success
00:00:12.374 - Installing Package File DNNMembershipProvider_05.06.03_Install: Success
00:00:12.427 - Installing Package File DNNMenuNavigationProvider_05.06.03_Install: Success
00:00:12.473 - Installing Package File DNNTreeNavigationProvider_05.06.03_Install: Success
00:00:13.012 - Installing Package File FckHtmlEditorProvider_02.00.04_Install: Success
00:00:23.712 - Installing Package File FileBasedCachingProvider_05.06.03_Install: Success
00:00:23.758 - Installing Package File FileModuleCachingProvider_05.06.03_Install: Success
00:00:23.808 - Installing Package File MemoryModuleCachingProvider_05.06.03_Install: Success
00:00:23.867 - Installing Package File SchedulingProvider_05.06.03_Install: Success
00:00:23.912 - Installing Package File SearchIndexProvider_05.06.03_Install: Success
00:00:23.961 - Installing Package File SearchProvider_05.06.03_Install: Success
00:00:24.010 - Installing Package File SolpartMenuNavigationProvider_05.06.03_Install: Success
00:00:24.113 - Installing Package File TelerikEditorProvider_05.06.03_Install: Error!
00:00:24.388 - Installing Optional AuthSystems:
00:00:24.389 - Installing Package File LiveID_01.00.01_Install: Success
00:00:25.495 - Installing Package File OpenID_02.00.00_Install: Success
00:00:25.734 - Installing Optional Packages:
---------------------------------------------------------------------------------------------------------------------------------------------

Notice pretty much everything was a success except for getting those providers to take. Now I will say the one small thing I noticed about taking the big upgrade leap from 5.2.3 to 5.6.3 is that when I clicked on go to my portal I got the notorious error in regards to the telerik.webu.dll file being of an earlier version than it ought and that the vb file was pointing to a newer version where as the web.config file was pointing to an older version.

Of course I guess this is do to the fact that updating the 5.3.0 config and the 5.5 failed but notice how some of the config versions were updated successfully where one just before and one after failed. In order to fix the error below that I always seem to get when going past version 5.4.0 or so I just simply find the install folder for the appropriate version I used the upgrade package for strip out the the Telerik.Web.UI from the bin file and go to the web.config file from this full installation folder and copy the following line: from that file



and paste in place of



This seems to get me up and running again here is that error in its entirety:

--------------------------------------------------------------------------------------------------------------------------------------

Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: BC32206: The project currently contains references to more than one version of Telerik.Web.UI, a direct reference to version 2009.3.1104.35 and an indirect reference (through 'DotNetNuke.Web.UI.WebControls.DnnWindowManager') to version 2011.1.519.35. Change the direct reference to use version 2011.1.519.35 (or higher) of Telerik.Web.UI.

Source Error:



Line 30: <input id="ScrollTop" runat="server" name="ScrollTop" type="hidden" />
Line 31: <input id="__dnnVariable" runat="server" name="__dnnVariable" type="hidden" />
Line 32: nnWindowManager ID="DnnWindowManager" runat="server" Visible="False">
Line 33: nnWindowManager>
Line 34:

--------------------------------------------------------------------------------------------------------------------------------

Now what I want you to look at is the providers that show up on two instances of DNN 5.6.3 one being the one I am now working on that is not upgrading successfully and one that has been upgraded successfully.

The one that did upgrade successfully was started at version I think it was either 5.4.2 or 5.4.4 and this one I am having issues with was actually started on 5.0.0 or 5.0.1 as a fresh install.

Anyway here are the providers that are seen from another one of my clients whose upgrade was successful to this same 5.6.3 version starting at around 5.4.2 or such a matter.

------------------------------------------------------------------------------------------------------------------------
Provider
DotNetNuke ASP.NET Membership Provider

DotNetNuke ASP.NET Membership Provider Project provides a membership service based on the core ASP.NET Membership components.

5.6.3

DotNetNuke Core Permission Provider
DotNetNuke Core Permission Provider Project provides a core permisisons.
5.6.3

DotNetNuke Core Sitemap Provider
Provides the sitemap for the core of a DotNetNuke portal
5.6.3

DotNetNuke Database Logging Provider

DotNetNuke Database Logging Provider Project provides a database logging service.

5.6.3

DotNetNuke DNN Menu Navigation Provider

DotNetNuke DNN Menu Navigation Provider Project provides a navigation system based on the DNNMenu Control

5.6.3

DotNetNuke DNN Tree Navigation Provider

DotNetNuke DNN Tree Navigation Provider Project provides a navigation system based on the DNNTree Control.

5.6.3

DotNetNuke Fck Html Editor Provider

DotNetNuke Html Editor Provider Project provides a Rich Text Editor based on the FCK Rich Text Editor.

2.0.4
DotNetNuke File Based Caching Provider

DotNetNuke File Based Caching Provider Project provides a File based Caching service.

5.6.3
DotNetNuke Module Caching File Provider

DotNetNuke Module Caching Provider that uses a File as its persistence medium.

5.6.3

DotNetNuke Module Caching Memory Provider

DotNetNuke Module Caching Provider that uses a Memory as its persistence medium.

5.6.3

DotNetNuke Profile Provider

DotNetNuke Profile Provider Project provides an extensible profile service.

5.6.3
DotNetNuke Scheduling Provider

DotNetNuke Scheduling Provider Project provides a scheduling service

5.6.3
DotNetNuke Search Indexer Provider
DotNetNuke Search Indexer Provider Project provides a module indexing service.
5.6.3
DotNetNuke Search Provider
DotNetNuke Search Provider Project provides a search service.

5.6.3

DotNetNuke Solpart Menu Navigation Provider

DotNetNuke Solpart Menu Navigation Provider Project provides a navigation system based on the SolpartMenu Control.

5.6.3
Telerik Editor Provider
DotNetNuke Html Editor Provider for Telerik Text Editor.
5.6.3

here are the providers I now have for this installation I am trying to work the kinks out of after it was "upgraded" to 5.6.3

--------------------------------------------------------------------------------------------------------------------------

Provider

DotNetNuke ASP.NET Membership Provider

DotNetNuke ASP.NET Membership Provider Project provides a membership service based on the core ASP.NET Membership components.

5.6.3

DotNetNuke ASP2 Menu Navigation Provider



DotNetNuke ASP2 Menu Navigation Provider Project provides a navigation system based on the menu included in ASp.NET v2.

5.0.0

DotNetNuke Broadcast Polling Caching Provider

DotNetNuke Broadcast Polling Caching Provider Project provides a database broadcast polling caching service.

5.0.0

DotNetNuke Core Permission Provider

DotNetNuke Core Permission Provider Project provides a core permisisons.

5.6.3

DotNetNuke Database Logging Provider

DotNetNuke Database Logging Provider Project provides a database logging service.

5.6.3
DotNetNuke DNN DropDown Navigation Provider

DotNetNuke DNN DropDown Navigation Provider Project provides a navigation system based on the ASP.NET Drop Down control.

5.0.0

DotNetNuke DNN Menu Navigation Provider

DotNetNuke DNN Menu Navigation Provider Project provides a navigation system based on the DNNMenu Control

5.6.3

DotNetNuke DNN Tree Navigation Provider

DotNetNuke DNN Tree Navigation Provider Project provides a navigation system based on the DNNTree Control.

5.6.3
DotNetNuke Fck Html Editor Provider
DotNetNuke Html Editor Provider Project provides a Rich Text Editor based on the FCK Rich Text Editor.

2.0.4

DotNetNuke File Based Caching Provider

DotNetNuke File Based Caching Provider Project provides a File based Caching service.

5.6.3
DotNetNuke Module Caching File Provider

DotNetNuke Module Caching Provider that uses a File as its persistence medium.

5.6.3
DotNetNuke Module Caching Memory Provider

DotNetNuke Module Caching Provider that uses a Memory as its persistence medium.

5.6.3

DotNetNuke Profile Provider

DotNetNuke Profile Provider Project provides an extensible profile service.

5.6.3
DotNetNuke Scheduling Provider

DotNetNuke Scheduling Provider Project provides a scheduling service

5.6.3
DotNetNuke Search Indexer Provider

DotNetNuke Search Indexer Provider Project provides a module indexing service.

5.6.3
DotNetNuke Search Provider

DotNetNuke Search Provider Project provides a search service.

5.6.3
DotNetNuke Solpart Menu Navigation Provider

DotNetNuke Solpart Menu Navigation Provider Project provides a navigation system based on the SolpartMenu Control.

5.6.3

DotNetNuke XML Logging Provider

DotNetNuke XML Logging Provider Project provides an Xml file based logging service.

5.0.0
-----------------------------------------------------------------------------------------------------------
Notice that the main differences between the items listed under the providers section from the failed and good upgrades is simply the core site map and the telerik editor stuff that is all. What I am scratching my head about is what possibly could be the cause of the Telerik editor and the core site map to fail. I did notice that in my DNN 5.2.3 which was my last successful upgrade from its original 5.0.0.1 was that the two things that seem to be failing miserably are the very things that were not available back in the 5.0.0.1 up to 5.2.3 days. Now true the Telerik Provider I don't think officially came on the seen until 5.4.0 and I did have that update config file errro even when upgrading to 5.3.1 but for some odd reason the Telerik and Site map providers which again seem to have come on the seen since 5.2.3 just don't want to migrate into my installation upon upgrade.

What could it possibly be, what might cause this problem. do you think it could be something about a module, provider, skin, or skin object that is the culprit here? I hate to have to delete most all my modules and such to find out what one gives. Is there a way to possibly disable a module if it comes down to this in order to the process of elimination find the sticking point here.

Anyway I hope all this info will help in coming to the conclusion of what can be tried that hasn't already been tried.

Thanks,

Bo

Since the SiteMapProvider and the TelerikEditorProvider are in the "optional" category, that means that there are zip files in the upgrade package that can be extracted and then installed like regular modules. Look for them in the Install/Provider folder of the upgrade package. Then, login as administrator, visit the Extensions page and try to install these, one at a time. You should see more detailed errors this way. If you get a message that the package is already installed, check the box to "repair" and continue.

You should at least have some additional errors to report here.

Ok Joe,

I did what you suggested and I will post the results below this is in regards to the coresitemap provider after upgrading to 5.3.1 remember the first error I got during this upgrade was that the config files could not be updated for 05.03.0.0

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Error loading files from temporary folder - see below
StartJob

Starting Installation
Info

Starting Installation - DotNetNuke.CoreSitemapProvider

Info

Starting Installation - Assembly

Info

Assembly registered - bin\Providers\DotNetNuke.SitemapProviders.CoreSitemapProvider.dll

Info

Creating backup of previous version - bin\Providers\DotNetNuke.SitemapProviders.CoreSitemapProvider.dll

Info

Created - bin\Providers\DotNetNuke.SitemapProviders.CoreSitemapProvider.dll

Info

Component installed successfully - Assembly

Info

Starting Installation - File

Info

Creating backup of previous version - license.txt

Info

Created - license.txt

Info

Component installed successfully - File

Info

Starting Installation - Config

Info

Creating backup of previous version - web.config

Failure

Exception - Object reference not set to an instance of an object.

Failure

Installation Failed - Config

Info

Rolling back component install - Assembly

Info

Restored backup of previous version - bin\Providers\DotNetNuke.SitemapProviders.CoreSitemapProvider.dll

Info

Component rolled back successfully - Assembly

Info

Rolling back component install - File

Info

Restored backup of previous version - license.txt

Info

Component rolled back successfully - File

Info

Installation Failed - DotNetNuke.CoreSitemapProvider

Info

Deleted temporary install folder

EndJob

Installation Failed

-------------------------------------------------------------------------------------------------------------------------------

Here is what I got in regards to the event viewer on dnn about this install of this provider

----------------------------------------------------------------------------------------------------------------------------------------------
Install Package:: CoreSitemapProvider
Info:: Starting Installation
Info:: Starting Installation - DotNetNuke.CoreSitemapProvider
Info:: Starting Installation - Assembly
Info:: Assembly registered - bin\Providers\DotNetNuke.SitemapProviders.CoreSitemapProvider.dll
Info:: Creating backup of previous version - bin\Providers\DotNetNuke.SitemapProviders.CoreSitemapProvider.dll
Info:: Created - bin\Providers\DotNetNuke.SitemapProviders.CoreSitemapProvider.dll
Info:: Component installed successfully - Assembly
Info:: Starting Installation - File
Info:: Creating backup of previous version - license.txt
Info:: Created - license.txt
Info:: Component installed successfully - File
Info:: Starting Installation - Config
Info:: Creating backup of previous version - web.config
Info:: Exception - Object reference not set to an instance of an object.
Info:: Installation Failed - Config
Info:: Rolling back component install - Assembly
Info:: Restored backup of previous version - bin\Providers\DotNetNuke.SitemapProviders.CoreSitemapProvider.dll
Info:: Component rolled back successfully - Assembly
Info:: Rolling back component install - File
Info:: Restored backup of previous version - license.txt
Info:: Component rolled back successfully - File
Info:: Installation Failed - DotNetNuke.CoreSitemapProvider
Info:: Deleted temporary install folder
Info:: Installation Failed
-------------------------------------------------------------------------------------------------------------------------------------------

Next I wanted to stay on the upgrade path from 5.3.1 so I went to 5.4.4 and when I did this of course I got the telerik failures which I will be posting below but I wanted to note that upon upgrading to 5.4.4 I noticed that I got that message again about the fact that the vb file was pointing to a different version of telerik than the web.config file was. Of course I didn't jump from 5.3.1 to 5.4.0 maybe I'll try that next and report back to you if I run into this issue of manually copying this dll file of Telerik from the full install folder of the same version I was upgrading to to my files where it never got transferred to not to mention the bindingredirect being auotmatically changed for the Telerik Editor.

Anyway I will post the install details below anyway for now and will post back about this other issue when I try a 5.3.1 to 5.4.0 uggrade.

Here is the snippet of attempting to manually install the telerik provider that includes where it errored out

------------------------------------------------------------------------------------------------------------------------------------------

Error loading files from temporary folder - see below
Info

Starting Installation - Config

Info

Creating backup of previous version - web.config

Failure

Exception - Object reference not set to an instance of an object.
Failure

Installation Failed - Config

Info

Rolling back component install - Provider
Info

Component rolled back successfully - Provider

Info

Rolling back component install - Assembly
Info

Restored backup of previous version - bin\DotNetNuke.HtmlEditor.TelerikEditorProvider.dll

Info

Component rolled back successfully - Assembly

Info

Rolling back component install - File

--------------------------------------------------------------------------------------------------
Install Package:: TelerikEditorProvider
Info:: Starting Installation
Info:: Starting Installation - DotNetNuke.TelerikEditorProvider
Info:: Starting Installation - Provider
Info:: Component installed successfully - Provider
Info:: Starting Installation - Assembly
Info:: Assembly registered - bin\DotNetNuke.HtmlEditor.TelerikEditorProvider.dll
Info:: Creating backup of previous version - bin\DotNetNuke.HtmlEditor.TelerikEditorProvider.dll
Info:: Created - bin\DotNetNuke.HtmlEditor.TelerikEditorProvider.dll
Info:: Component installed successfully - Assembly
Info:: Starting Installation - File
Info:: Creating backup of previous version - EditorOverride.css
Info:: Created - EditorOverride.css
Info:: Creating backup of previous version - license.txt
Info:: Created - license.txt
Info:: Creating backup of previous version - releaseNotes.txt
Info:: Created - releaseNotes.txt
Info:: Creating backup of previous version - Telerik.Web.UI.DialogHandler.aspx
Info:: Created - Telerik.Web.UI.DialogHandler.aspx
Info:: Creating backup of previous version - Telerik.Web.UI.SpellCheckHandler.ashx
Info:: Created - Telerik.Web.UI.SpellCheckHandler.ashx
Info:: Creating backup of previous version - LinkClickUrlHandler.ashx
Info:: Created - LinkClickUrlHandler.ashx
Info:: Component installed successfully - File
Info:: Starting Installation - File
Info:: Creating backup of previous version - FileManager.resx
Info:: Created - FileManager.resx
Info:: Creating backup of previous version - RadEditor.Dialogs.resx
Info:: Created - RadEditor.Dialogs.resx
Info:: Creating backup of previous version - RadEditor.Main.resx
Info:: Created - RadEditor.Main.resx
Info:: Creating backup of previous version - RadEditor.Modules.resx
Info:: Created - RadEditor.Modules.resx
Info:: Creating backup of previous version - RadEditor.Tools.resx
Info:: Created - RadEditor.Tools.resx
Info:: Creating backup of previous version - RadListBox.resx
Info:: Created - RadListBox.resx
Info:: Creating backup of previous version - RadProgressArea.resx
Info:: Created - RadProgressArea.resx
Info:: Creating backup of previous version - RadScheduler.Main.resx
Info:: Created - RadScheduler.Main.resx
Info:: Creating backup of previous version - RadSpell.Dialog.resx
Info:: Created - RadSpell.Dialog.resx
Info:: Creating backup of previous version - RadUpload.resx
Info:: Created - RadUpload.resx
Info:: Component installed successfully - File
Info:: Starting Installation - File
Info:: Creating backup of previous version - ConfigDefault.xml
Info:: Created - ConfigDefault.xml
Info:: Creating backup of previous version - ConfigDocumented.xml
Info:: Created - ConfigDocumented.xml
Info:: Creating backup of previous version - ToolsDefault.xml
Info:: Created - ToolsDefault.xml
Info:: Creating backup of previous version - ToolsMinimal.xml
Info:: Created - ToolsMinimal.xml
Info:: Component installed successfully - File
Info:: Starting Installation - File
Info:: Creating backup of previous version - SaveTemplate.resx
Info:: Created - SaveTemplate.resx
Info:: Component installed successfully - File
Info:: Starting Installation - File
Info:: Creating backup of previous version - About.ascx
Info:: Created - About.ascx
Info:: Creating backup of previous version - AccessibleTable.ascx
Info:: Created - AccessibleTable.ascx
Info:: Creating backup of previous version - CellProperties.ascx
Info:: Created - CellProperties.ascx
Info:: Creating backup of previous version - DocumentManager.ascx
Info:: Created - DocumentManager.ascx
Info:: Creating backup of previous version - FileBrowser.ascx
Info:: Created - FileBrowser.ascx
Info:: Creating backup of previous version - FindAndReplace.ascx
Info:: Created - FindAndReplace.ascx
Info:: Creating backup of previous version - FlashManager.ascx
Info:: Created - FlashManager.ascx
Info:: Creating backup of previous version - FormatCodeBlock.ascx
Info:: Created - FormatCodeBlock.ascx
Info:: Creating backup of previous version - Help.ascx
Info:: Created - Help.ascx
Info:: Creating backup of previous version - ImageEditor.ascx
Info:: Created - ImageEditor.ascx
Info:: Creating backup of previous version - ImageManager.ascx
Info:: Created - ImageManager.ascx
Info:: Creating backup of previous version - ImageMap.ascx
Info:: Created - ImageMap.ascx
Info:: Creating backup of previous version - LinkManager.ascx
Info:: Created - LinkManager.ascx
Info:: Creating backup of previous version - MediaManager.ascx
Info:: Created - MediaManager.ascx
Info:: Creating backup of previous version - MozillaPasteHtmlDialog.ascx
Info:: Created - MozillaPasteHtmlDialog.ascx
Info:: Creating backup of previous version - MozillaPasteTextDialog.ascx
Info:: Created - MozillaPasteTextDialog.ascx
Info:: Creating backup of previous version - PageProperties.ascx
Info:: Created - PageProperties.ascx
Info:: Creating backup of previous version - RenderTemplate.aspx
Info:: Created - RenderTemplate.aspx
Info:: Creating backup of previous version - SaveTemplate.aspx
Info:: Created - SaveTemplate.aspx
Info:: Creating backup of previous version - SetImageProperties.ascx
Info:: Created - SetImageProperties.ascx
Info:: Creating backup of previous version - SilverlightManager.ascx
Info:: Created - SilverlightManager.ascx
Info:: Creating backup of previous version - StyleBuilder.ascx
Info:: Created - StyleBuilder.ascx
Info:: Creating backup of previous version - TableBorder.ascx
Info:: Created - TableBorder.ascx
Info:: Creating backup of previous version - TableDesign.ascx
Info:: Created - TableDesign.ascx
Info:: Creating backup of previous version - TableProperties.ascx
Info:: Created - TableProperties.ascx
Info:: Creating backup of previous version - TableWizard.ascx
Info:: Created - TableWizard.ascx
Info:: Creating backup of previous version - TemplateManager.ascx
Info:: Created - TemplateManager.ascx
Info:: Creating backup of previous version - TrackChangesDialog.ascx
Info:: Created - TrackChangesDialog.ascx
Info:: Creating backup of previous version - XhtmlValidator.ascx
Info:: Created - XhtmlValidator.ascx
Info:: Component installed successfully - File
Info:: Starting Installation - File
Info:: Creating backup of previous version - SaveTemplate.gif
Info:: Created - SaveTemplate.gif
Info:: Component installed successfully - File
Info:: Starting Installation - File
Info:: Creating backup of previous version - RegisterDialogs.js
Info:: Created - RegisterDialogs.js
Info:: Component installed successfully - File
Info:: Starting Installation - Config
Info:: Creating backup of previous version - web.config
Info:: Exception - Object reference not set to an instance of an object.
Info:: Installation Failed - Config
Info:: Rolling back component install - Provider
Info:: Component rolled back successfully - Provider
Info:: Rolling back component install - Assembly
Info:: Restored backup of previous version - bin\DotNetNuke.HtmlEditor.TelerikEditorProvider.dll
Info:: Component rolled back successfully - Assembly
Info:: Rolling back component install - File
Info:: Restored backup of previous version - EditorOverride.css
Info:: Restored backup of previous version - license.txt
Info:: Restored backup of previous version - releaseNotes.txt
Info:: Restored backup of previous version - Telerik.Web.UI.DialogHandler.aspx
Info:: Restored backup of previous version - Telerik.Web.UI.SpellCheckHandler.ashx
Info:: Restored backup of previous version - LinkClickUrlHandler.ashx
Info:: Component rolled back successfully - File
Info:: Rolling back component install - File
Info:: Restored backup of previous version - FileManager.resx
Info:: Restored backup of previous version - RadEditor.Dialogs.resx
Info:: Restored backup of previous version - RadEditor.Main.resx
Info:: Restored backup of previous version - RadEditor.Modules.resx
Info:: Restored backup of previous version - RadEditor.Tools.resx
Info:: Restored backup of previous version - RadListBox.resx
Info:: Restored backup of previous version - RadProgressArea.resx
Info:: Restored backup of previous version - RadScheduler.Main.resx
Info:: Restored backup of previous version - RadSpell.Dialog.resx
Info:: Restored backup of previous version - RadUpload.resx
Info:: Component rolled back successfully - File
Info:: Rolling back component install - File
Info:: Restored backup of previous version - ConfigDefault.xml
Info:: Restored backup of previous version - ConfigDocumented.xml
Info:: Restored backup of previous version - ToolsDefault.xml
Info:: Restored backup of previous version - ToolsMinimal.xml
Info:: Component rolled back successfully - File
Info:: Rolling back component install - File
Info:: Restored backup of previous version - SaveTemplate.resx
Info:: Component rolled back successfully - File
Info:: Rolling back component install - File
Info:: Restored backup of previous version - About.ascx
Info:: Restored backup of previous version - AccessibleTable.ascx
Info:: Restored backup of previous version - CellProperties.ascx
Info:: Restored backup of previous version - DocumentManager.ascx
Info:: Restored backup of previous version - FileBrowser.ascx
Info:: Restored backup of previous version - FindAndReplace.ascx
Info:: Restored backup of previous version - FlashManager.ascx
Info:: Restored backup of previous version - FormatCodeBlock.ascx
Info:: Restored backup of previous version - Help.ascx
Info:: Restored backup of previous version - ImageEditor.ascx
Info:: Restored backup of previous version - ImageManager.ascx
Info:: Restored backup of previous version - ImageMap.ascx
Info:: Restored backup of previous version - LinkManager.ascx
Info:: Restored backup of previous version - MediaManager.ascx
Info:: Restored backup of previous version - MozillaPasteHtmlDialog.ascx
Info:: Restored backup of previous version - MozillaPasteTextDialog.ascx
Info:: Restored backup of previous version - PageProperties.ascx
Info:: Restored backup of previous version - RenderTemplate.aspx
Info:: Restored backup of previous version - SaveTemplate.aspx
Info:: Restored backup of previous version - SetImageProperties.ascx
Info:: Restored backup of previous version - SilverlightManager.ascx
Info:: Restored backup of previous version - StyleBuilder.ascx
Info:: Restored backup of previous version - TableBorder.ascx
Info:: Restored backup of previous version - TableDesign.ascx
Info:: Restored backup of previous version - TableProperties.ascx
Info:: Restored backup of previous version - TableWizard.ascx
Info:: Restored backup of previous version - TemplateManager.ascx
Info:: Restored backup of previous version - TrackChangesDialog.ascx
Info:: Restored backup of previous version - XhtmlValidator.ascx
Info:: Component rolled back successfully - File
Info:: Rolling back component install - File
Info:: Restored backup of previous version - SaveTemplate.gif
Info:: Component rolled back successfully - File
Info:: Rolling back component install - File
Info:: Restored backup of previous version - RegisterDialogs.js
Info:: Component rolled back successfully - File
Info:: Installation Failed - DotNetNuke.TelerikEditorProvider
Info:: Deleted temporary install folder
Info:: Installation Failed
--------------------------------------------------------------------------------------------------
Hopefully this is enough info to start with. I have attached a copy of the web.config file that I had from 5.2.3 which was the last good upgrade in my original post. If you want another copy of my web.config file from one of my upgrade attempts let me know. I couldn't figure out how to attach a file after I attached one on the initial post but if you can attach a file to a reply let me know.

Bo

Ok Joe,

I just tried a 5.2.3 to 5.3.1 and than a 5.3.1 to 5.4.0 and I still am forced to manually copy over that telerik file from the bin directory and replace the bindingredirect node for Telerik to get my site up and running.

It almost seems like the problem is somehow wired to my web.config file or some other config file on the site and it seems to only be effecting these two providers because the config file for what ever reason can't be updated in various iterations.