Hi all,

  I hope someone out there can help me, as the title suggests I am running my current site on DNN 3.1.1 and now want to shift over to DNN 4.3.4 and there's the problem.

  Here is what I have so far. 1 backup of my site running on my hosting companies servers. This backup site is an exact mirror of the main site, running from it's own instance of the DNN database. It is this backup site I am trying to upgrade as a test before doing it on the live site.

  So far I have downloaded the DNN 4.3.4 Upgrade .zip file and unzipped this to my backup sites folder, overwriting any files as it goes. Next I changed the .NET version to 2 now came the fun part. I renamed the web.config file to web.config.resource and renamed the release.config file to web.config Now I opened the web.config.release file and the new web.config file (so I had a point of referance for the changes) here is what I have changed in web.config

<connectionStrings>
    <!-- Connection String for SQL Server 2000/2005
    <add
      name="SiteSqlServer"
      connectionString="Server=entered my SQL server addy here;Database=database name here;uid=database UID here;pwd=database Password here;"
      providerName="System.Data.SqlClient" />
   -->
<!-- Connection String for SQL Server 2005 Express -->
    <add
      name="SiteSqlServer"
      connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
      providerName="System.Data.SqlClient" />

  </connectionStrings>
  <appSettings>
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules
    <add key="SiteSqlServer" value="Server=entered my SQL server addy here;Database=database name here;uid=database UID here;pwd=database Password here;"/>
    -->
<!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules   -->
    <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>

Further down the web.config file

<system.web>
    <customErrors mode="Off"/>  <-- This I added to try and get a detail of the error
    <machineKey
      validationKey="Validation key from the original we.config file"
      decryptionKey="decryption key from the original we.config file3"
      decryption="3DES"
      validation="SHA1"/>
    <!-- HttpModules for Common Functionality -->

Now when I try to go to my site address to complete the update I get the wonderful error:

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>

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

Please can anyone help me identify what I am doing wrong here??? 

Thanks.

I officially now feel stupid, you know after a long shift at work and then trying to do this was a bad idea

I did copy the machine keys over, I will now go back and uncomment the sections I need and see what I get.

Thanks

This is directly from the downloads area:

"DotNetNuke 4.0 is designed to be used with ASP.NET 2.0. Please note that there is not an automated upgrade path from the DotNetNuke 3.x Source version to the DotNetNuke 4.0 Source version at this time. Based on the fact the folders/files in the Source version have been completely reorganized, DO NOT extract the DotNetNuke 4.0 Source version over top of an existing DotNetNuke 3.x version. Also note that the web folder in the DotNetNuke 4.0 Source release has changed from the root folder to the /WebSite folder."

"Please can anyone help me identify what I am doing wrong here???"

There is no automated upgrade path from 3.x to 4.x, so what you're doing wrong has nothing to do with the config file.

The best advice for anyone still in 3.x (myself included, I have a few) is to use the 3.3.5 upgrade on 3.x installs, plain and simple.

Please read the instructions more carefully before attempting to upgrade existing installs.