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 ...HELP moving an existing DNN Portal Install/Instance from server A to server BHELP moving an existing DNN Portal Install/Instance from server A to server B
Previous
 
Next
New Post
9/25/2009 4:57 PM
 

This is very interesting....

I was able to successfully port and server the (4.9.0) DNN instance(currently lives on IIS 6.0, Win Server 2003) to a web server running IIS 6.0 and Win Server 2003.  The server that I'm trying to port to is IIS 7 and is running Win Server 2008. 

Howerver, since I am able to host a basic DNN plain vanilla instance on IIS7/WinServ2008 I'm wondering of porting the existing DNN instance (from IIS6/WinServ2003) is running into some type of security issues either with the browser or system.

 
New Post
9/25/2009 5:01 PM
 

Yes, I have updated all webserver string literal instance in the PortalAliases table:

IE.....

From (old table contents - select * from PortalAliases):

- localhost/DNN

- webserverA/DNN

To (new table with updated webserver):

- localhost/DNN

- webserverB/DNN

 
New Post
9/26/2009 1:19 PM
 

"Internet Explorer cannot display the webpage" This is a generic message which IE displays and it's masking one of real errors. You need to have the browser display the exact error from the web server. Use another browser like FF to get the exact message or in IE go to Tools->Advanced. There's an option for displaying friendly messages, change the setting.

Once you know what the error message is, you will probably find out the problem.

Also go to web.config and have the CustomError tag set to 'Off' to display the asp.net message.

You can also start with placing a static HTML page in the root folder and have the browser request it. You want to isolate ASP.NET errors from IIS errors from DNS errors from DNN errors and so forth.

Good luck.


Free DNN 5.2 hosting at FreehostingWithSitebuilder.com
Lots of extra modules and skins - Your domain name or ours
 
New Post
9/28/2009 6:28 PM
 

Hi, thanks for the reply.

I have checked the setting for "Show Friendly HTTP" in IE but I still get the following error (IE error listed below).  I have also tried to brwose to the site, http://localhost/DNN in Firefox and recieve the generc "Unable to Connect" error message (I can connect to msn.com to there is not connection issues).

I have also set CustomError tag = "Off".  One other thing that I did was server a static .html page via http://localhost/index.html and it was served from c:\inetpub\wwwroot\index.html.

Completely at a loss right now....

Internet Explorer cannot display the webpage

 
 
 

Most likely causes:

  • You are not connected to the Internet.
  • The website is encountering problems.
  • There might be a typing error in the address.
 

What you can try:

 

Diagnose Connection Problems

 

More information

"------------- IE Error -------------"

Internet Explorer cannot display the webpage
  
   Most likely causes:
You are not connected to the Internet.
The website is encountering problems.
There might be a typing error in the address.
 
   What you can try:
     Diagnose Connection Problems 
 
     More information

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...HELP moving an existing DNN Portal Install/Instance from server A to server BHELP moving an existing DNN Portal Install/Instance from server A to server B


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