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 ...MS SQL 2012MS SQL 2012
Previous
 
Next
New Post
4/20/2012 11:14 AM
 
I just tried installing on localhost using the web installer and it works, so it would seem there're some IIS settings i was missing.

The idea is to make a local install and then simply move it onto the hosted environment in order to go around the installation problems i experienced there.
 
New Post
4/20/2012 1:16 PM
 
Moving the installation was no success.

What i did was scripting out the database (schema and data, but no users) and ran the script on the remote sql server.

It came out with some errors about some modules that couldnt be created as they already existed on the remote location.

Then went and changed the portalalias to match the production environment and also altered the conn string for the db in web.config

Finally i copied the files to the remote location as well, but when i access it, i get error upon error, first something about razorhost that cant be loaded, then i removed it from the db and the desktopmodules folder, but then a new error came up, somthing about a runtime being newer than the one currently running aso........

I call it quits for today, because ive pretty much spent the whole day trying to do a simple dnn installation and it keeps failing no matter how i try and do it.

I even tried using the webmatrix to install to the remote location, but it doesnt seem to do anything but copyt the installation files as u still have to go thru the whole setup thing afterwards, only difference is that the web.config contains the db conn string and therefor u dont have to type it in.

It would be really good to know if theres a problem running DNN 6.1.5 under MSSQL 2012 or not, because i dont feel like wasting anymore time on this if thats the case.



.....sry if i sound grumpy though......but i am.... lol
 
New Post
4/20/2012 2:05 PM
 
I have done a new install of DNN 6.1.5 and 6.2.0
If you want to transfer an local databse to an other server, you only could run backup scripts and you have to make sure you allready have the same SQL Database Users created on the new SQL Server.

Also you must be sure you using the same SQL Schema!

 
New Post
4/21/2012 3:18 AM
 
backup and restore is definately a better approach than scripting the database.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/21/2012 3:54 AM
 
I know and its much easier too, but in the hosted environment i dont have admin access to the sql server and therefore cant make nor retrieve the .bak file.

Ive copied dnn installations from production evironment to localhost before by scripting the db:

1. Generate scripts
2. Select all objects except for users
3. Select "Data and schema"

The run the sql file on my local sql server and it normally works like a charm. :-)

However u run into some limitations, like if the script file becomes too large, u get a "File too large error".


When moving ive always created a db with the same user, login and schemes.
Then its usually just down to chg the conn string in the web.config and change the portalalias in the db. :-)
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...MS SQL 2012MS SQL 2012


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