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 ...Domain Name Does Not Exist In The Database - Issue migrating DNN backup filesDomain Name Does Not Exist In The Database - Issue migrating DNN backup files
Previous
 
Next
New Post
8/25/2011 6:40 AM
 
Hi all,

I've been having problem trying to setup DNN backup files on the server.

The backup database was restored to the server, and PortalAlias is not empty.

Can anyone help suggest what might be the problem?

Thanks
Jean

(the follow error occured after dnn tried to do a fresh installation
Domain Name 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:

  1. Web Server Processing
    • 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.


  2. 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.
 
New Post
9/21/2011 10:38 AM
 
Hello,

Did you ever find the fix for this problem?  I am getting the same "Domain Does Not Exist in the Database".
 
New Post
11/10/2011 10:22 AM
 
Anyone researching this problem may come across various postings saying that all portal aliases must be listed seperated by commas. This is not correct, each alias requires a new row in the database.
Richard

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Domain Name Does Not Exist In The Database - Issue migrating DNN backup filesDomain Name Does Not Exist In The Database - Issue migrating DNN backup files


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