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 ...How to Place Database on a Separate ServerHow to Place Database on a Separate Server
Previous
 
Next
New Post
10/6/2006 3:49 PM
 

I have DNN 4.3.5 installed on my system, using Starter Kit.  Is it possible to place the SQLServer database on another machine?

I have my connectionString as

Server=dbserver;Database=dnn;uid=dnn;pwd=dnnpwd;

That works if IIS and SQLServer 2005 are both on the same machine -- dbserver.  If the IIS is installed on another machine, say webserver, and DNN is also on webserver, I can log into the portal but cannot do site or portal managment.  When I click on Users, I receive the following message:

An error has occurred

Any help is appreciated.

 
New Post
10/7/2006 2:13 PM
 

I'm a little confused how you got to Users in the first place. Did you setup DotNetNuke from scratch with the connection string to the other (SQL) server, or did you setup DotNetNuke with a connection string to the same machine then change it to the other (SQL) server?

DotNetNuke doesn't care where the SQL database resides, during installation it will setup the database accordingly. If you simply change the connection string of an existing DotNetNuke installation, there better be data on the other end.


Dwayne J. Baldwin
 
New Post
10/7/2006 4:58 PM
 

Dwayne,

In VisualStudio 2005, instead of "Publish Web Site" under Build I copy all the files to the web server and it works.  Here is what I did in the first place, that cause the problem.  On development server, I have both SQLServer 2005 and DNN installed with VisualStudio 2005.

Everything works on development server with http://localhost/mysite and http://devserver/mysite (with devserver/mysite in alias).  Inside VS 2005, I use "Publish Web Site" to compile and publish (not copy) the web site to testing server, which has no SQLServer.  On testing server, I can run http://localhost/mysite or http://testserver/mysite (testserver/mysite added as an alias) and log in as host or admin.  But I will get the error after clicking on Users on the top.  When I go to Site Settings, many places (such as Portal Skin, Portal Container) will show "<>" instead of "<Not Specified>".  If I expand "Advanced Settings" and "Other Settings", the dropdown for Portal TimeZone is blank.

Now I simply copy the files inside the web site from development server to testing server with Windows Explorer, the portal works fine.  Is that because some files are not moved with "Publish Web Site"?

 
New Post
10/7/2006 9:37 PM
 

I think you may be on to something here. How many modules are listed in the drop down list?

I have seen many times where a half installed DNN only displays 5 modules and many other things are broken. It is usually caused by the other way around, copying the files from an existing DNN site where the installation routine has not properly installed the modules on the new machine. 

One workaround for this issue is to copy the files in install\modules (from a fresh DNN install package)to the half baked site and hit the site with http://(server)/DotNetNuke/Install/Install.aspx?mode=Install

Let me explain a little about the installation process and it might explain the situation;  During a fresh install from the DNN install package, the application takes each zip file in Install/Module and unzips the contents into \DesktopModules and runs the approriate database scripts. This allows the modules to be registered under DNN for the code part while the scripts provide the database part. The original file is then deleted from from the Install/Module folder.

This works fine for development purposes, but when you attempt to copy your existing site to new machine, the new application will have no knowledge of any modules because the Install\Module folder is emtpy (already installed).

The best way is to install DotNetNuke normally from the Install package onto the new machine to get a completely working version of DotNetNuke. Then you can do you your development locally, and either publish or copy your files OVER the working version on the new machine.

It makes sense once you understand how the DNN installation actually works. 

I hope this is of some help to you. Please let me know your results.


Dwayne J. Baldwin
 
New Post
10/8/2006 11:25 PM
 

Dwayne,

I think the easiest way to use remote SQLServer is (1) to install DNN on a separate server from the beginning or (2) to copy the entire installed website to another server.  Even with an empty Install\Module, I find that (2) still works.  There must be something else causing my initial problem.  Basically, my finding is DO NOT use "Publish Web Site" in VS 2005.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...How to Place Database on a Separate ServerHow to Place Database on a Separate Server


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