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 ...Installation ProblemsInstallation Problems
Previous
 
Next
New Post
2/22/2007 12:46 PM
 

Thanks Leupold, this is the complete message,

 DotNetNuke Upgrade Error

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

ERROR: Could not connect to database.

The stored procedure 'dbo.dnn_GetPortalAliasByPortalID' doesn't exist

I'm using "dnn" as object qualifier.

Rgds

 
New Post
2/22/2007 1:57 PM
 

this is your issue: "ERROR: Could not connect to database."

make sure, the connection string is correct and appropriate for authentication method of the sql server as well as the sql server user existis and has been granted dbo permission for the database to be used.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/22/2007 2:42 PM
 

Are you running .NET 2.0 or .NET 1.0????  Also was there a previous install attempted on this database prior????

 

Thanks

 

 

 
New Post
2/22/2007 3:20 PM
 

There was only one installation attempt, when the table (dnn_version) and stored procedures (dnn_finddatabaseversion, dnn_getdatabaseversion, dnn_updatedatabaseversion) were created.  I will check with the host, both connection strings are okay, maybe the problem is with the user permissions.

Thanks

 
New Post
2/22/2007 5:12 PM
 

Whenever you fail an attempt on an install, Its a lot easier to just drop the db and create a new one since this is a fresh install.  What happens is when you make a failed attempt the first time, its trivial to get it up the second because of DNN writing to the DB.  even if you run install/install.aspx?mode=Upgrade, that may not solve it.  So what I would do in this case again is to keep your files on the server and just simply drop the db and create a fresh new db and run it again.  ( Of course also update the web.config with new db name, pwd etc.)

Hope this helps.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installation ProblemsInstallation Problems


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