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 from 2.1.1upgrade from 2.1.1
Previous
 
Next
New Post
7/10/2008 9:22 AM
 

Thanks for the replies!!

I created a test copy of the production site and ran the upgrade.  Now I can't login to the site.  Any suggestions?

Thanks again.

 
New Post
7/10/2008 10:13 AM
 

When you made your web.config changes did you copy the machine keys from the original to the new web.config?

 
New Post
7/10/2008 10:37 AM
 

That's the problem.  I couldn't find any machine keys in the original web.config.  Am I missing something?

 
New Post
7/10/2008 4:19 PM
 

Here is a copy of my original web.config file.  I don't see anything about machinekey in here......

<configuration>

    <!-- register local configuration handlers -->
    <configSections>
        <sectionGroup name="dotnetnuke">
            <section name="data" type="DotNetNuke.ProviderConfigurationHandler, DotNetNuke" />
            <section name="logging" type="DotNetNuke.ProviderConfigurationHandler, DotNetNuke" />
            <section name="scheduling" type="DotNetNuke.ProviderConfigurationHandler, DotNetNuke" />
            <section name="htmlEditor" type="DotNetNuke.ProviderConfigurationHandler, DotNetNuke" />
        </sectionGroup>
    </configSections>

    <!-- Sql Server connection string for support of pre DNN 2.0 Private Assemblies
         The new connection string (for DNN 2.0) is in the section dotnetnuke (providers) -->
    <appSettings>
        <add key="connectionString" value="Server=xxxxxxx;Database=xxxxxxxx;uid=xxxxxxx;pwd=xxxxxxx;" />
    </appSettings>

    <system.web>

        <!-- set debugmode to false for running application -->
        <compilation debug="false" />

        <!-- permits errors to be displayed for remote clients -->
        <customErrors mode="RemoteOnly" />

        <!-- forms or Windows authentication -->
        <authentication mode="forms">
        <forms name=".DOTNETNUKE" protection="All" timeout="60" />
        </authentication>
        <!--
            <identity impersonate="true"/>
            <authentication mode="Windows">
            </authentication>
        -->

        <!-- allow large file uploads -->
        <httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="8192" />
        
        <!--  GLOBALIZATION
        This section sets the globalization settings of the application.
        Utf-8 is not supported on Netscape 4.x
        If you need netscape compatiblity leave iso-8859-1.
        UTF-8 is recommended for complex languages
        -->
        <globalization culture="en-US" uiCulture="en" requestEncoding="UTF-8" responseEncoding="UTF-8" fileEncoding="UTF-8" />
        <!--<globalization culture="en-US" uiCulture="en"  fileEncoding="iso-8859-1" requestEncoding="iso-8859-1" responseEncoding="iso-8859-1"/>-->

        <!-- page level options -->
        <pages validateRequest="false" enablev13wstat3Mac="true" />

    </system.web>

    <dotnetnuke>
        <htmlEditor defaultProvider="FtbHtmlEditorProvider" >
            <providers>
                <clear/>
                <add name = "FtbHtmlEditorProvider"
                        type = "DotNetNuke.HtmlEditor.FtbHtmlEditorProvider, DotNetNuke.FtbHtmlEditorProvider"                    
                        providerPath = "~\Providers\HtmlEditorProviders\FtbHtmlEditorProvider\"
                />
            </providers>
        </htmlEditor>
        <data defaultProvider="SqlDataProvider" >
            <providers>
                <clear/>
                <add name = "SqlDataProvider"
                        type = "DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider"
                        connectionString = "Server=xxxxxx;Database=xxxxxxx;uid=xxxxxxx;pwd=xxxxxxx;"
                        providerPath = "~\Providers\DataProviders\SqlDataProvider\"
                        objectQualifier = ""
                        databaseOwner = "dbo"
                        upgradeConnectionString = ""
                />
                <add name = "AccessDataProvider"
                        type = "DotNetNuke.Data.AccessDataProvider, DotNetNuke.AccessDataProvider"
                        connectionString = "PROVIDER=Microsoft.Jet.OLEDB.4.0;"
                        providerPath = "~\Providers\DataProviders\AccessDataProvider\"
                        objectQualifier = "DotNetNuke"
                        databaseFilename = "DotNetNuke.mdb.resources"
        />
            </providers>
        </data>
        <logging defaultProvider="XMLLoggingProvider" >
            <providers>
                <clear/>
                <add name = "XMLLoggingProvider"
                        type = "DotNetNuke.Logging.XMLLoggingProvider, DotNetNuke.XMLLoggingProvider"
                        configfilename="LogConfig.xml.resources"
                        providerPath = "~\Providers\LoggingProviders\XMLLoggingProvider\"
                />
            </providers>
        </logging>
        <scheduling defaultProvider="DNNScheduler" >
            <providers>
                <clear/>
                <add name = "DNNScheduler"
                        type = "DotNetNuke.Scheduling.DNNScheduler, DotNetNuke.DNNScheduler"
                        providerPath = "~\Providers\SchedulingProviders\DNNScheduler\"
                        debug="false"
                        maxThreads="-1"
                        enabled="true"
                />
            </providers>
        </scheduling>

    </dotnetnuke>
</configuration>


Any suggestions?

 
New Post
7/10/2008 6:20 PM
 

some people are getting a little confused, to clear up the issue - encryptionkey and validationkey were added in 3.0.

Michael,

I'd recommend you back up your site (code and database), download a 3.x copy (upgrade version). Open up the release.config and edit the sitesqlserver value(s) and set them to your connectionstring from your 2.12 web.config. Then rename the release.config to web.config, and copy it and all the other files from the 3.x copy over the 2.12 site. When you now hit the site the upgrade will start up. If everything is succesful, you'll want to update to 4.8.5 (use on the earlier links I've provided to talk you through switching .net versions etc.)

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...upgrade from 2.1.1upgrade from 2.1.1


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