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 <root name> Does Not Exist in the DatabaseDomain name Does Not Exist in the Database
Previous
 
Next
New Post
10/3/2007 8:59 PM
 

I recommended DNN to a friend, and now may end up regretting it.  She upload all of the 4_55 Install files to GoDaddy, altered the Web.Config file, and launched the setup wizard.  During the inital setup of the database, the progress bar kept going and going for hours.  Eventually, she gave up and reloaded the root page of the web in the browser (in a different setup, my database scripts took less than a minute, so something seemed wrong).

Loading the root of the webpage results in the following:

Domain Name www.*****.com 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.

The database does contain many tables and procedures with the prefix she assigned during setup, but neither of us knows if they are all there, nor what they should look llike.  Any suggestions as to what to do?  Does there exist a script which can be run to restore the back-end database on GoDaddy to its original state?  Does it seem like a good idea to blow away the db and restart?  Is there a better strategy?

 

 
New Post
10/5/2007 6:47 PM
 

Nobody has any ideas?  I'm in the middle of requesting GoDaddy reset the entire database and then I'll wipe the website out and try again, I guess.

 
New Post
10/9/2007 7:22 PM
 

did you get a resolution to this

 
New Post
10/11/2007 12:52 PM
 

plismore wrote

did you get a resolution to this

No, and even more disappointingly, not a single suggestion from this board.  Usually this board is quite helpful, but not this time.  If GoDaddy will reset the database, I will probably try again with an older and more proven version, or just do the work to create a straight CSS based site.

 

 
New Post
11/5/2007 12:20 AM
 

I had the same problem and after many hours of work I got it to work properly. 

What I did was to clean all my files from the server. I than ftp my Dot Starter files to the server. After that I went to the browser and enter my url. I think there was an error so I enter http://website.com/install\install.aspx and everything went well.

I hope this helps someone

Pedro
www.walkside.com

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Domain name <root name> Does Not Exist in the DatabaseDomain name Does Not Exist in the Database


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