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 ...DotNetNuke Upgrade error: Domain Name Does Not Exist In The DatabaseDotNetNuke Upgrade error: Domain Name Does Not Exist In The Database
Previous
 
Next
New Post
10/15/2008 10:48 AM
 

 

Hello everyone. After many attempts, i've finally managed to upgrade my DNN 4.x (previous to 4.6.2, i think it was 4.4.1) to DNN 4.9.0. The installation said it completed successfully (I've upgraded DNN before, but after 4.4.1 I haven't been able to upgrade anymore because of an error, that later on proved to be the fact that I was forgetting to copy the InstallationDate key to the new web.config file). However, when browsing to the website, it says the domain name is not in the database. I've checked the Portals and PortalAlias tables, and all the HTTPAliases are there, just as before. However, DNN will not work anymore, and keeps throwing that error. The connection strings are all in order (and after all, it's saying the alias doesn't exist in the database, not that it can't connect to it), but right now, my development site is down. Any ideas ? Thank you in advance.
 
New Post
10/15/2008 1:04 PM
 

 

Replying to my own post here, in case anyone makes the same mistake as me: when upgrading, and updating the web.config file, *ALWAYS* check if the objectQualifier is set. Aside from the connection strings (connectionStrings and AppSettings), machineKey and codeDirectories, also check the objectQualifier. Since i hadn't set it, DNN created a new set of empy tables, without the prefix. Noticed the empty tables after looking at the database's contents. Changed the prefix, ran the upgrade procedure again, and now it all works fine :)
 
New Post
10/15/2008 1:33 PM
 

great, btw: you will not need to modify web.config file in the future, since its upgrade is now performed by the installer.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/21/2011 5:58 AM
 

 

Hello,

Sorry for replying to a such old message but... I have the same and exact problem !!
:-(

I checked my Portal Alias table, it's ok. So what else could it be ?

In the web.config, the objectqualifier is as follows:
{providers}
        {clear /}
        {add name="SqlDataProvider" type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider" connectionStringName="SiteSqlServer" upgradeConnectionString="" providerPath="~\Providers\DataProviders\SqlDataProvider\" objectQualifier="" databaseOwner="dbo" /}
     {/providers}

I am upgrading locally from DNN 4.9.5 to 5.6.3

DV FX
 
New Post
9/3/2011 5:22 PM
 
I made an error in web.config, now it's solved.
;-)

Thanks,
DV FX
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DotNetNuke Upgrade error: Domain Name Does Not Exist In The DatabaseDotNetNuke Upgrade error: 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