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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Deploying DNN 3.2.2 to a production server - DotNetNuke Upgrade ErrorDeploying DNN 3.2.2 to a production server - DotNetNuke Upgrade Error
Previous
 
Next
New Post
4/27/2006 5:54 PM
 

I'm hoping someone out there can help me out... I want to deploy my local DNN installation to my hosting provider, and no matter what I try, I am constatly getting the following error:

DotNetNuke Upgrade Error

The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

Invalid object name 'dbo.PortalAlias'.

I've been searching the forums and google for 2 days now and needless to say its getting a bit frustrating... I was able to setup a new install on the host with no problem, it works fine.Only when I restore the DB to the host sql server and copy my development DNN folder up do I get this error. Is there any reason why it is trying to upgrade, and why the assembly versions don't match??

Any help at all would be greatly appreciated!

Thanks.

 

Paul

 
New Post
4/27/2006 6:41 PM
 

there are 2 things you have to do to make this work:

* make sure the web.config is correct, you need to change the sql connection string
* make sure the hostname of the "live"site is added as portalias in your db. You can do that by hand by adding the correct value to the portalalias table (use portalid 0)

cheers

erik


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
4/27/2006 7:20 PM
 

Hi Erik, thanks for the reply!

I can't begin to tell you how many times I've checked over the sql connection string in the web config... And I was sure to add the new portal alias in the site settings page before I backed up the database in my local test environment. It's strange because I was able to setup a clean, new install without any problems at all, which leads me to believe that there is no problem with the hosting company. This error only occurs when I restore the database from my local backup. 

I really hope I don't have to recreate all the work I've done on my development box, I spent countless hours setting everything up the way I wanted it. Again, thanks for the reply, if you can think of any other reason why this error may occur I'd be very grateful!

Thanks!

Paul 

 
New Post
4/27/2006 9:49 PM
 

After some tinkering around I was able to replicate the problem on my development box... It seems that once I changed the database object ownership from 'dbo' to some other account, and modified the databaseowner property in the web.config file to reflect the change, the exact same error occured. Makes sense because the dbowner on my host's database is not 'dbo' either.

So my question is how come the application is still looking for 'dbo.PortalAlias', even though I've made the change to the web.config? Has anyone out there come across this before?

Thanks,

 

Paul

 
New Post
4/28/2006 2:12 AM
 

Ah... thats where your mistake is. DBO does not necessarily mean that your username is DBO, it just means that the user that u use to connect to your db has DBO rights in the db. So if your user indeed has dbo rights, then just leave the DBO in web.config, don't change it with your real username.

cheers,

Erik


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Deploying DNN 3.2.2 to a production server - DotNetNuke Upgrade ErrorDeploying DNN 3.2.2 to a production server - DotNetNuke Upgrade Error


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