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""Domain Name Does Not Exist In The Database"
Previous
 
Next
New Post
12/20/2011 1:31 AM
 

I'm getting this error after creating a copy of my database and a copy of the website dir and using them as a test site.

I created the new folder and changed the web.confiig to point to the new db. Then I started getting this error. I am on Windows 2003 so I also had to add the Host Header values in the website properties.

I'm using DNN 6.1.1 but it looks like this error page is still from long ago because it says to add the portal alias to the PortalAlias field in the Portal table by using a comma separated list, instead of putting it in the PortalAlias table.

What causes this?

 
New Post
12/20/2011 3:36 AM
 
This error is occured because none of the Portal Alias matches the URL you've used to access to your test site.

You only have to add the corresponding entry in the PortaAlias table or modify the existing. You could do this by using SQL Server Management Studio.

For information, I've just verified the Portal table and I didn't find any PortalAlias field.



Stéphane TETARD
ARICIE - Member of DotNetNuke France
 
New Post
12/20/2011 11:19 PM
 

I suppose I should have mentioned that I checked the PortalAlias table and the names of the Aliases where in there. I read the error message and was able to interpret it. The problem was that the solution in the error message didn't fix my problem.

As I looked into it farther I found that the portal properties had the DefaultAlias still set to the production site name and the other setting said 'REDIRECT'. These settings, combined with some other setting I must have fixed, led to that error message from the days before the PortalAlias table.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ..."Domain Name Does Not Exist In The Database""Domain 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