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 ...Conflicts in web.configConflicts in web.config
Previous
 
Next
New Post
7/27/2013 11:53 PM
 

I am trying to move a DNN site from a Windows Server 2008 server to Windows Server 2012. The problem is that the web.config from the source (WS 2008) isn't compatible with the target (IIS 8.0). I'm assuming this is an IIS 7.0 -> 8.0 issue.  I can't even load the web.config file in IIS Manager.

 

Anyway, do I REALLY have to start hand-crafting web.config filesDNN drives me crazy with all the manual edits and low-level details necessary for simple, common tasks (move a site from one server to another). Are we still at the point where I have to edit web.config or is there any easier way?

Thanks.

Mark

 
New Post
7/28/2013 4:32 AM
 
Mark,

the only point where you have to edit the web.config file when moving from one server to another are the two connection strings - as long as you have the SQL Server on the same machine.

Best wishes
Michael

Michael Tobisch
DNN★MVP
dnn-Connect.org - The most vibrant community around the DNN-platform
 
New Post
7/28/2013 2:23 PM
 

Thanks for the response. I am very familiar with the need to edit the connection string as I move between machines but that is a simple data issue (wrong machine name, etc). The problem I am seeing seems more about the web.config structure/schema. To reiterate, the web.config file I am restoring comes from a Windows Server 2008 machine and is going on to a Window Server 2012 machine. If this was merely a connection string issue (wrong machine name, for example) I assume I'd be able to at least load the file in IIS Manager. However, IIS Manager complains that it can't load it, which I assume wouldn't happen if I simply has a connection string wrong?

Or am I missing something?

Thanks again.

Mark

 
New Post
7/29/2013 4:47 AM
 
Hi Mark,

I recently moved 5 DNN installations (from 4.9.5 to 7.1) from a Windows 2003/SQL Server 2008 machine to a Windows 2012/SQL Server 2012 machine without running into any issue.

When IISManager complains that it can't read the web.config, I would try to open it using XML Notepad 2007 (http://www.microsoft.com/en-us/download/details.aspx?id=7973) to find out if it contains valid XML (it won't open if there are some issues and asks if the file should be opened using Notepad). If this is the issue, there might have gone something wrong while copying the file from one machine to the other, and I would simply try to re-copy it (or, as I mentioned in your other post, re-zip the original folder and re-unzip it on the new machine).

If this is not the case, there might be some things missing in IIS setup (IIS 6 compatibility needed, etc. - compare with the setup on your old server.

What I would not expect is that for any case the account that IIS uses to start has no permissions in the installation folder, but you could double-check this.

Best wishes
Michael

Michael Tobisch
DNN★MVP
dnn-Connect.org - The most vibrant community around the DNN-platform
 
New Post
7/29/2013 8:23 AM
 
Could you specify the error message? There are some Points that can be Forget on moving a dnn instance.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Conflicts in web.configConflicts in web.config


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.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out