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 ...Is it possible to upgrade from ver 3 to ver 4?Is it possible to upgrade from ver 3 to ver 4?
Previous
 
Next
New Post
12/31/2007 8:47 AM
 

Thank you Erik :-)
You are my hero :))

 

I have decided to stay with my SQL 2000

I took the release.config after the ver 4.x upgrade and updated the following tags as below:

********************************

 <connectionStrings>
  <!-- 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" />
  <!-- Connection String for SQL Server 2000/2005
    <add
      name="SiteSqlServer"
      connectionString="Server=drori;Database=ctware;uid=ctware;pwd=ctware;"
      providerName="System.Data.SqlClient" />
   -->
 </connectionStrings>
 <appSettings>
  <!-- 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;"/>
  <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules
    <add key="SiteSqlServer" value="Server=drori;Database=ctware;uid=ctware;pwd=ctware;"/>
    <add key="MachineValidationKey" value="DC4B39ECC39F242CAB3F2E12074F96AC387BFCA5" />
    <add key="MachineDecryptionKey" value="B372C9427F1C8DE249A6AA0C1DD670884634D280F9848E9C" />
    -->
  <add key="InstallTemplate" value="DotNetNuke.install.config" />
  <add key="AutoUpgrade" value="true" />
  <add key="UseInstallWizard" value="true"/>
  <add key="InstallMemberRole" value="true" />
  <add key="ShowMissingKeys" value="false" />
  <add key="EnableWebFarmSupport" value="false" />
  <add key="EnableCachePersistence" value="false"/>
  <add key="HostHeader" value="" />
  <!-- Host Header to remove from URL so "www.mydomain.com/johndoe/Default.aspx" is treated as

"www.mydomain.com/Default.aspx" -->
  <add key="RemoveAngleBrackets" value="false" />
  <!--optionally strip angle brackets on public login and registration screens-->
  <add key="PersistentCookieTimeout" value="0" />
  <!--use as persistent cookie expiration. Value is in minutes, and only active if a non-zero figure-->
  <!-- set UsePortNumber to true to preserve the port number if you're using a port number other than 80 (the

standard)
    <add key="UsePortNumber" value="true" /> -->
 </appSettings>
***********************************************************

Somehow it is still not working :-(

The default.aspx page display the following:

An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

What should i do? Did i forgot something? (i switched to framework 2 in the IIS section as recomended)

 
New Post
1/1/2008 11:48 AM
 

you made a couple of mistakes:

  • the machine key nodes have moved to another section (system.web) in dnn 4, so please do not add them yourself to the appsettings section, but instead modify the proper section already present in web.config
  • you forget to change the comments for the connection strings (<!-- and --> ), the way you changed it now, the connectionstrings are commented out in the web.config.

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
1/2/2008 3:01 AM
 

Erik van Ballegoij wrote

you made a couple of mistakes:

  • the machine key nodes have moved to another section (system.web) in dnn 4, so please do not add them yourself to the appsettings section, but instead modify the proper section already present in web.config
  • you forget to change the comments for the connection strings ( ), the way you changed it now, the connectionstrings are commented out in the web.config.

Thanks again dear Erik.

It is working now!

What about all the modules (some of them are DNN core modules) that can not work now?

The upgarde procedure is not supposed to replace it automatically?

Should i upgarde them one by one?

 

 

 
New Post
1/2/2008 4:22 AM
 

All your modules should still work (if they don't, you might have missed the legacy connection string)

If you want to upgrade all your modules you can do 2 things:

  • download and install them one by one
  • download the latest DNN Core install package, unzip somewhere, and copy all files from the directory /install/modules/ (or only those you really need)
  • copy those files to the install/modules/ directory of your upgraded installation
  • browse to your upgraded installation, log on as host, go to host > module definitions, and install the modules you want (find them at the bottom of the page)

 


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
1/2/2008 7:14 AM
 

You are right Erik. I made another mistake with the connection string. It's fixed now.

I was looking for the media new version but i saw that 3.x is the lastest.

Thanks again and best regards,

Dror

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Is it possible to upgrade from ver 3 to ver 4?Is it possible to upgrade from ver 3 to ver 4?


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