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 ...Upgrade Questions - 4.02 to 4.34Upgrade Questions - 4.02 to 4.34
Previous
 
Next
New Post
8/5/2006 5:56 PM
 
 
Hi, I upgrading, from 4.02 to 4.34, on a webhost4life account. The post in this forum about Installing/Upgrading says:
 

"In general, the standard method for dealing with config upgrades is to rename your existing web.config to web.config.backup. Rename the release.config to web.config. Then manually copy the following settings from the old web.config.backup to the new web.config file:

    <add key="SiteSqlServer" value="{connection string}"/>
    <add key="MachineValidationKey" value="{your localized key}" />
    <add key="MachineDecryptionKey" value="{your localized key}" />   "

I found the

<add key="SiteSqlServer" value="{connection string}"/>

in my original web.config file, but there is no

 <add key="MachineValidationKey" value="{your localized key}" />

or

<add key="MachineDecryptionKey" value="{your localized key}" />.

I do have a

<machineKey validationKey="C18AA34FD6576A2C51BDDDB8EF80560F35C75674"

and a

decryptionKey="C0BBE510FA7A4F19764A33CC70E332A8AE74FF08FBE8B62B"

am I supposed to do something with those instead?

Also, what about the Portals folder? Do I keep my old one there, or let it be overwritten by the new one?

Is there anything else I need to back up? Are there complete step-by-step instructions anywhere?

Thanks!

 
New Post
8/5/2006 9:28 PM
 

The first form for MachineValidationKey and MachineDecriptionKey was used in DNN 3.1.x and earlier while the validationKey and decriptionKey attributes of the machineKey tag are those used in DNN 4.x.  Copy over the corresponding values for validationKey and decriptionKey.

Any content now in the Portals folder and subfolders will either be left as is currently or overwritten on a file by file basis with new content of the same filename.

A couple of other points to remember:

1. If you can backup your entire database before the upgrade, do so just in case!

2. Make sure that the unused connection string (for either SQL Server Express 2005 or SQL Server is properly commented out.

3. Be sure that the same connection string also has been copied over to the value of the SiteSqlServer under the <appSettings> node.

4. If you used a database objectQualifier for the SqlDataProvider (under the data/providers node), don't forget to copy its value over as well - I forgot to do this on one live site upgrade from 4.0.2 to 4.3.3 and ended up with a horrible mess that took several hours to untangle.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
8/7/2006 11:37 PM
 
Hi - thanks - that was very helpful! Hi, I upgraded to 4.34. The upgrade ran fine, and said it was successful. Now, when I try any of my domains, I get this:
 
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 <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
 

<!-- Web.Config Configuration File -->
 
<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>
 
 
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 <customErrors> configuration tag to point to a custom error page URL.
 

<!-- Web.Config Configuration File -->
 
<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>
 
Do I need to do something else? Thanks
 
New Post
8/8/2006 3:28 AM
 
Hi ksoszka,

Yep, have had the exact same error you had trying to upgrade from DNN 4.0.3 to 4.3.1.

The weirdest part is that only a week or more ago, I upgraded 3 other DNN 4.0.3 sites to 4.3.1 without the error.

Apart from a small 'typo' in one of the web.config files, I am at a total loss as to why it now reports this error.

I see myself as lucky that the 3 other 4.3.1 sites are working, and will work on the other site as 4.0.3 until some of the instabilities have been solved.

Any solutions guys?

Cheers.

 
New Post
8/8/2006 7:18 AM
 

Change (temporarily if this is a live site available to the public) the customErrors mode value to "Off" in Web.Config:

<customErrors mode="Off"/>

then revisit your site.  You should then be able to see more details about the error that is being thrown.  Post the complete error message here in the forum and we'll take a look at it.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade Questions - 4.02 to 4.34Upgrade Questions - 4.02 to 4.34


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