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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...how to restore web.config from older backuphow to restore web.config from older backup
Previous
 
Next
New Post
9/21/2010 8:58 AM
 
Hello guys,

I accidently replaced a web.config file in "site A" with the web.config that was supposed to be in "site B". I have files from "A" backed up in a folder, but they're a couple of months old and I have updated site content a couple of times after that old backup. When I tried to replace the web.config, the site still crashed.

I don't know much about DNN programming, but apparently the web.config suffers changes along the updating, etc on site. Is there a way I can solve this? Or do I have to run a full restore from the really old backup I did? Including DB, etc. 
 
New Post
9/21/2010 9:33 AM
 
Unless you have upgraded the DotNetNuke framework, upgraded to a newer version of ASP.Net, changed the SQL database connection information, or installed one of the few modules which makes changes to web.config since your last good backup of the site's web.config, the web.config file from a few months back should be ok to use. Adding or modifying site content does not make changes to web.config.

Please post the exact and complete error message(s) you received when you replaced the incorrect web.config with the backup web.config.

What version of the DNN framework and what ASP.Net version (2.0, 3.5 SP 1 or 4.0) are you using?

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
9/21/2010 9:58 AM
 
Thanx for the answer, Bill.

Regarding the version... it's 3.5 and I think DNN was upgraded, yes. The connection to SQL has not changed at all.

Any suggestions?
 
New Post
9/21/2010 10:44 AM
 
The problem is that any of the changes made to web.config during a DNN framework upgrade done since the backup will not be included in web.config. Ideally it would be helpful to know what version of DNN was running before the upgrade. We'll definitely have to know what version of DNN is currently installed. The best way to obtain the version history will be to look at the Versions table in the database which will contain a row for each version showing Major, Minor, Build, and CreatedDate columns. Any versions having the same CreatedDate will have been part of the same upgrade.

What is the complete and exact error message you are receiving when you try to visit the site?

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
9/23/2010 6:43 AM
 
I finally could see the error and this is it http://polenmedia.net/error.png . I deleted the bidingRedirect of the assembly telerik and now the site displays the "unavailable, come back later" notice.

Any thoughts?
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...how to restore web.config from older backuphow to restore web.config from older backup


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