Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...problem upgrading from 5.05.00 to 5.06.00problem upgrading from 5.05.00 to 5.06.00
Previous
 
Next
New Post
11/17/2010 6:34 PM
 
No manual web.config edits beyond pointing it at my hosted sql server 2008 R2 instance back when I first installed it.  I do seem to remember having a problem with the telerik stuff back when I upgraded to 5.05.00 from 4.x.  I seem to remember having to manually copy the telerik assembly and manually edit web.config back then to get it to load after installing the upgrade package.  That's what made me think to manually upload the full install without web.config and then when it gave a different error I manually fixed the redirect in web.config.  The upgrade from 5.5.0 to 5.5.1 went flawlessly if memory serves.

Bryan Johns
K4GDW

"There are 10 types of people. Those who understand binary and those who do not."
 
New Post
11/17/2010 8:06 PM
 
Yes, can you post the area of your web.config between:

<dependentAssembly>

</dependentAssembly>

Have you changed the line in there to what Brian posted?

<bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.02.0929.35" />

Ken Grierson
DotNetNuke Corporation
Test Lead
 
New Post
11/17/2010 8:47 PM
 
Prior to the upgrade (v05.05.00):

<dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
</dependentAssembly>
<dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
</dependentAssembly>
<dependentAssembly>
        <assemblyIdentity name="Telerik.Web.UI" publicKeyToken="121fae78165ba3d4" />
        <!--Upgraded by DotNetNuke.Telerik.Web version 5.4.0 - Date: 5/4/2010 3:08:29 PM-->
        <!--<bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.01.309.35" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <!--Upgraded by DotNetNuke.Telerik.Web version 5.5.0 - Date: 8/19/2010 11:40:24 PM-->
        <!--<bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.01.309.35" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.02.0713.35" />
</dependentAssembly>

After the failed upgrade to v05.06.00:

<dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
</dependentAssembly>
<dependentAssembly>
        <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
</dependentAssembly>
<dependentAssembly>
        <assemblyIdentity name="Telerik.Web.UI" publicKeyToken="121fae78165ba3d4" />
        <!--Upgraded by DotNetNuke.Telerik.Web version 5.4.0 - Date: 5/4/2010 3:08:29 PM-->
        <!--<bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.01.309.35" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <!--Upgraded by DotNetNuke.Telerik.Web version 5.5.0 - Date: 8/19/2010 11:40:24 PM-->
        <!--<bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.01.309.35" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <!--Upgraded by DotNetNuke.Telerik.Web version 5.6.0 - Date: 11/17/2010 3:25:05 PM-->
        <!--<bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.02.0713.35" xmlns="urn:schemas-microsoft-com:asm.v1" />-->
        <bindingRedirect oldVersion="2008.0.0.0-2020.0.0.0" newVersion="2010.02.0929.35" />
</dependentAssembly>

So it looks like the upgrade got as far as updating the <bindingRedirect> tag.  As I said, it looks like the web site is working OK but I'm not left with any sense of confidence that all is well given that the installation did fail.



 
New Post
11/17/2010 9:39 PM
 
I had backed up my v05.05.00 files and database, so I decided to do the upgrade to v05.06.00 on localhost.  It worked perfectly!  Why did it fail on my remote version?  Maybe it timed out (it was taking a long time to process).  But there was no message about that.  Something else mysterious I guess.

Now I compared my localhost v05.06.00 files against my broken v05.06.00 files at my web hosting service.  Of course the web.config files were a bit different because for localhost I'm point to the local database but otherwise web.config is the same on both the working localhost and broken remote versions.

But there were differences -- specifically some files were present on the broken remote version.  In the \Install\AuthSystem folder on the remote, there are the files LiveID_01.00.01_Install.zip and OpenID_02.00.00_Install.zip.  In the Install\Provider folder there is TelerikEditorProvider_05.06.00_Install.zip.

There are also a handful of templates in the \Portals\0\Templates\ folder (htmlEditorTemplates.css, ImageAndTitle.css, ImageAndTitle.htmtemplate, SimpleTableAndHeader.css, SimpleTableAndHeader.htmtemplate, TwoColumnAndTitle.css, TwoColumnAndTitle.htmtemplate).

And finally the SecurityRoles.ascx.resx file in \DestopModules\Admin\Security\App_LocalResources folder is empty in the broken remote version.

I realize there is one modificaton to the web.config file for my website, namely, I set <add key="AutoUpgrade" value="false" />.
 
New Post
11/18/2010 12:02 AM
 
Problem fixed!

I ran the following:

http://mywebsiteurl/install/install.aspx?mode=installresources

and the rest of the installation completed without incident.  I still have no idea why the installation failed initially but this seems to have fixed the problem.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...problem upgrading from 5.05.00 to 5.06.00problem upgrading from 5.05.00 to 5.06.00


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out