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 ...moving site from development to productionmoving site from development to production
Previous
 
Next
New Post
3/23/2011 10:32 AM
 
I'm trying to move our site from our development server to a production server.  I have followed advice from several posts on how to do this properly, yet i continue to run into problems.

Both servers have the same setup:
Windows Server 2008 R2
SQL Server 2008 R2
IIS 7.5
Dotnetnuke 05.06.01 (238)

I have done the following:
1. backed up my development db
2. created a new db on my production server and restored from development backup
3. created a "dnn" user and mapped to the new production db
4. edited the portal alias and portal settings tables records to reference my new server name
5. zipped the development server website directory
6. unzipped development site to production server
7. granted network service full control on unzipped directory
8. edited my web.config connectionstring settings to reflect the new server
9. restarted IIS

I have tried this a few times and get the same results every time when i navigate to the new site...

Domain Name intranetprod/rrhsweb Does Not Exist In The Database

DotNetNuke supports multiple portals from a single database/codebase. It accomplishes this by converting the URL of the client browser Request to a valid PortalID in the Portals database table. The following steps describe the process:

Web Server Processng

When a web server receives a Request from a client browser, it compares the file name extension on the target URL resource to its Application Extension Mappings defined in IIS.
Based on the corresponding match, IIS then sends the Request to the defined Executable Path ( aspnet_asapi.dll in the case of ASP.NET Requests ).
The aspnet_isapi.dll engine processes the Request in an ordered series of events beginning with Application_BeginRequest.

HttpModule.URLRewrite OnBeginRequest ( UrlRewriteModule.vb )

The Request URL is parsed based on the "/" character
A Domain Name is constructed using each of the relevant parsed URL segments.

Examples:

URL: http://www.domain.com/default.aspx = Domain Name: www.domain.com
URL: http://209.75.24.131/default.aspx = Domain Name: 209.75.24.131
URL:
http://localhost/DotNetNuke/default.aspx = Domain Name: localhost/DotNetNuke
URL:
http://www.domain.com/virtualdirectory/default.aspx = Domain Name: www.domain.com/virtualdirectory
URL: http://www.domain.com/directory/default.aspx = Domain Name: www.domain.com/directory

Using the Domain Name, the application queries the database ( Portals table - PortalAlias field ) to locate a matching record.

Note: If there are multiple URLs which correspond to the same portal then the PortalAlias field must contain each valid Domain Name in a comma seperated list.

Example:

URL: http://localhost/DotNetNuke/default.aspx
URL: http://MACHINENAME/DotNetNuke/default.aspx
URL: http://209.32.134.65/DotNetNuke/default.aspx
PortalAlias: localhost/DotNetNuke,MACHINENAME/DotNetNuke,209.32.134.65/DotNetNuke

Note: If you are installing the application to a remote server you must modify the PortalAlias field value for the default record in the Portals table according to the rules defined above.


 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...moving site from development to productionmoving site from development to production


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