Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 to 4.3.5 problemupgrade to 4.3.5 problem
Previous
 
Next
New Post
9/16/2006 6:08 PM
 
Blake Helms

www.blakehelms.net
Joined: 5/22/2005
Posts: 30
eureka wrote

Hello Shadowpdx

 I don’t have that facility available with my server to take it off line.



ASP.NET 2.0 make it very easy to take your application offline. Simply place an html file in the root called App_Offline.htm. This will take the site offline and allow you to upload the files without worrying about someone hitting the site. You can make the page look however you want to tell the user that you are doing maintenance. When I am finished I rename I add ".BAK" or whatever to the file extension to disable it and bring the site back online.
 
New Post
9/16/2006 6:13 PM
 
Lynn


www.artreach.net
Joined: 8/27/2004
Posts: 338

Hello Shadowpdx

As I said earlier I was following a tutorial/video:

found here: http://www.dnncreative.com/HowtoupgradeDotNetNuke/tabid/202/Default.aspx

The steps of the tutorial are:

  1.  Backup your installation
  2. Backup the web.config file
  3. Backup any other files you may have changed such as the fav.ico file, custom 404 pages, etc.
  4. Edit the web.config file
    <add key="AutoUpgrade" value="true" />
    to
    <add key="AutoUpgrade" value="false" />
  5. Upload this change to the server
  6. Transfer from your server web.config file the settings to the release.config file, covering:
    <add key="SiteSqlServer" value="Server=7.8.2.1,23;Database=audio32xT;uid=Myuid;pwd=usm38fTJ;" />
    <add key="MachineValidationKey" value="DB02CB97BAE1814E49F1310895EC33B22FC70014" />
    <add key="MachineDecryptionKey" value="6E324A6FF2B87D590B71D61FDD95C82A137C980893117CF0"/>
    <add key="InstallationDate" value="11/19/2005" />
  7. If you have made any further changes to your web.config file for third party modules,  HTTP compression, or database object qualifiers, copy these changes across to the release.config file
  8. If you have enabled HTTP compression, disable it until you have completed the upgrade
  9. Save the changes to the release.config file and rename it to web.config
  10. The first file to upload is the dotnetnuke.dll file from the bin folder
    This informs DotNetNuke that you are upgrading the website and it will now display an under construction page
    (You can view the under construction page in the Install folder)
  11. Upload all of the DotNetNuke  installation files over the top of the current installation
  12. Open your browser and enter the following URL:
    http://www.yourwebsiteaddress.com/Install/Install.aspx?mode=Install
  13. This will trigger the installation process
  14. Check that your website is operating correctly and that you can still login

 

According to #10. The first file to upload is the dotnetnuke.dll file from the bin folder

So you don't check the progress of your upgrade untill the end? How do you know that it is going ok?

Thanks

Lynn

 

www.seemalta.net
 
New Post
9/16/2006 6:23 PM
 
Mike Hicks

www.shadowsnetwork.com
Joined: 10/28/2005
Posts: 104
I use DNN Creative  (as a matter of fact, I am doing their skinning tutorial) but have never uploaded any dll.  As for the upgrade, I just follow the steps that I outlined.  When I trigger the upgrade, DNN gives me all the info I need as it does the upgrade - but I ever upload a .dll.   Could it be that the tutorial that you are using if for 3.x and not 4.x?  I noticed that the version mentioned on the page was 3.x
Shadow
 
New Post
9/16/2006 6:35 PM
 
Lynn


www.artreach.net
Joined: 8/27/2004
Posts: 338

Hello Shadowpdx

Hmmm, "Could it be that the tutorial that you are using if for 3.x and not 4.x?  I noticed that the version mentioned on the page was 3.x" Maybe that is what it is. 

 Perhaps I am being over cautious, I am scared of going wrong. However, I am still not seeing the expected message:

This site is currently Unavailable
Please check back later

I Think I might be brave and just go ahead any way, what do you think?

Lynn

www.seemalta.net
 
New Post
9/16/2006 6:38 PM
 
Mike Hicks

www.shadowsnetwork.com
Joined: 10/28/2005
Posts: 104

What is your current version?

+++++++++++++edit+++++++++++

Sorry, I went back to your first post - I upgraded from 4.3.4 to 4.3.5 this morning and had no problems....so far.  I would update.

The steps I used were:

    1. Back up your site ( I didn't but I am known to take chances occasionally)
    2. Unzip the contents of the upgrade version to my website root
    3. Rename your web.config to web.config.old ( I didn't - I usually do when it is a major upgrade)
    4. Transfer the neccessary setting to the release.config file
    5. Rename the release.config to web.config
    6. Trigger the update

Looking at the tutorial, I would elminate #10

 

 

Shadow
 
 Page 3 of 5
Previous12345Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...upgrade to 4.3.5 problemupgrade to 4.3.5 problem


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