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 ...Uploading DNN with VWD 2005Uploading DNN with VWD 2005
Previous
 
Next
New Post
3/9/2008 3:28 PM
 

I've installed the DNN VWD starter kit and I can create a dnn site inside VWD. Everything works fine without doing any modification. Now I want to use the uploading feature inside VWD to upload my DNN site to a web host. It uploads fine. When I try the URL from the browser I get the following error page:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Kinda makes sense, but I'm not sure how to fix this. Do I need to make a change to the web.config? 

 
New Post
3/9/2008 4:19 PM
 

FIG,

Yes, you'll need to update the web.config to reflect the fact that you are using a new database in your web hosting environment.

Look for SiteSqlServer in the web.config file and update with the new server, database name, user name, and password for your database connection.

Take care,

Ian


Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
New Post
3/9/2008 4:27 PM
 

FIG:

I think you are running into a little bit of confusion that many people with some ASP.Net experience run into when getting started with DNN.  That is okay, let's review.

You DO NOT need the DNN Starter Kit to setup a DNN site for production, you only need the Install Package.  This follows the idea of "XCopy Deployment" as commonly used with .Net applications.  Notice that the Started Kit is intended for those that need to setup a DNN module development environment.  But even if you are developing modules, you should use the Install Package for production and then install your new modules in the usual way.  The Install Package is a precompiled version of DNN, so there is no need for you to have Visual Studio or Visual Web Dev Express to roll out a DNN site.

Now, to answer you question on modifications needed for the Web.config file, yes, you probably need to make changes to it according to your production server environment.  Most likely the SQL Server connect strings need to be adjusted.  You need to check with your host server admin how the SQL Server environment is setup.

EDIT: Forgot to mention that you'd probably need to add new aliases to your portals if you were using something like "localhost/dotnetnuke" on your dev PC and on the production server need to be www.realdomain.com for instance.

Hope this helps.

Carlos

 

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Uploading DNN with VWD 2005Uploading DNN with VWD 2005


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