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 ...i wonder if its really that difficult and complicatedi wonder if its really that difficult and complicated
Previous
 
Next
New Post
8/6/2007 10:15 AM
 

hi, my name is sabine, and im something like a newbie in the dotnetnukeworld. i made a nuke website on a virtual pc and now i wanted to synchronize with another server, just to test it. if it works, i planned to synchronize with the real webserver. but it does not work. i read a lot of documentation and tried really hard to work it out. but it seems as you have to copy a lot of things from a to b and check if in one table is this and there is that.

i did the following:

at first i installed a new portal on the destination server, set all permissions and everything -> it works without any problem.

then i installed redgate on my own server and synchronized my own website database with the destination server database. the only difference between the two databases is the username and the password and the name of the database. my own database is called nuke, the destination database is called liftoff. yeah and the two owner have different names and passwords.

the synchronisation worked, i could see the data from my own database on the destination database (and the owner was set like it should be)  BUT: when i tried to open the website from destination server (with correct address: testpc/testportal) he gave me a redirection error. "the adress you are calling is redirecting your request that it never can be completed".

well i checked in the database of the destination server the table portal alias, there is the right adress. erikvb (he wrote an article about moving database from a to b) told me that i should copy some files (mostly dlls in the bin folder) but i think thats a little bit complicated. everytime when i synchronize after a update i should compare the dlls and copy them around? and i dont think that i would have the permission on the webserver to play around with dlls.

 

isnt there a much easier way? what have i done wrong? can you please help me?

thank you!

kind regards,

sabine kreuzer

 

 
New Post
8/6/2007 4:57 PM
 

Sabine,

there are also file sync utilities around, that will do the filesyncing for you. Of course you have access to copy dll's to the server... how else would you install dnn in the first place? Anyway, you only need to compare all the folders i told you to (like bin, desktopfolders) if you installed new modules. otherwise, you only need to compare the portals directory, which contains all userfiles

Like i explained to you by email, it would be benificial if your dev DB and live DB were set up as identical as possible. If you entered the correct portal alias (domain name) as http alias, all should be fine. Mind you: if you first fired up your site, and only after that add a new portal alias directly in the db, you should restart your site (by touching web.config for instance), because the portal alias data is cached by dnn, and will only be read again after a site restart.


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

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

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...i wonder if its really that difficult and complicatedi wonder if its really that difficult and complicated


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