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 - error connecting to server BEFORE SETUPInstallation - error connecting to server BEFORE SETUP
Previous
 
Next
New Post
6/5/2008 12:40 PM
 

I'm trying to install a third DNN 4.6.2 installation on an existing website.  We've got two other 4.6.2 installs in virtual directories that have been up and running since sometime last fall on the same website.

I've unzipped the 4.6.2 install and created the virtual directory in IIS (Server 2003 SP1, IIS 6).  I've granted permissions for both NETWORK SERVICE and ASPNET to the directory (just to cover all bases).

When I go to the website to START configuration, I get the following error:

DotNetNuke Error: - Version 04.06.02


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)

 Note that this is BEFORE I even get into the installation wizard.  When I click on the "Return to Site" link, it takes me to the wizard, but I get three javascript errors (running IE 6) and the page does not have the correct styling, and no images.  If I attempt to display any of the images (as http://site/virtualdir/images/rt.gif) I get the same error page as above.

As far as I can tell there are no differences in the configuration or the permissions between this new virtual directory or the other two dnn virtual directories running on the same website.

 

 

 

 
New Post
6/6/2008 12:39 PM
 

Make sure you configure the database for acces as well.  You may need to edit the web.config connection strings in the new setup to match the new database.

Also, there is no ASPNET account on Windows Server 2003, you can remove that access.

Jeff

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installation - error connecting to server BEFORE SETUPInstallation - error connecting to server BEFORE SETUP


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