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 ...Advanced installation problems (DNN 3.3.4 + W2k3)Advanced installation problems (DNN 3.3.4 + W2k3)
Previous
 
Next
New Post
10/9/2006 5:34 AM
 

Hi,

I'm installing DNN on a W2003 server (for development purpuses).
The database server (SQL2000) resides on another W2k3 (SBS) server which acts as a domain controller, but only controls itself. This is because of the preinstalled SBS. This server also has a running DNN-webserver without any problems, but thats 100% locally.

Now I'm trying to access the newly created DB on the SQL-server during the installation of DNN, but I keep on slamming into the

ERROR: Could not connect to database specified in connectionString for SqlDataProvider

It's DNN version 3.3.4 altough that seems trivial to me.

The problem seems to me is that the worker-process on the new dev-dnn-server uses the NETWORK SERVICE credentials which are not recognised by the SQL-server so network access to the SQL-server is denied. Now how to solve it is above my knowledge level.

I've tried running the IIS application pool under the credentials of an user that's known to the SQL-server AND  the dev-server, but then i get a 'service unavailable' error in my browser.

Any takers? TIA!

 
New Post
10/9/2006 4:15 PM
 

did you check whether your connectionstring is ok? What kind of authentication are you using for your SQL server. Mixed authentication would be best, make sure you created a useraccount for your db, and specify that user in your connection string. Also make sure that your sql server accepts incoming connections (make user TCP/IP is enabled in the sql server communication configuration). Also make sure you do not have an active firewall blocking incoming connections on the SQL server tcp port (usually 1433)

 


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

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

 
New Post
10/9/2006 5:48 PM
 

Yes. Using the connection string on a locally running dnn installation works. Also using the string on the dev server in a dev-application works. The sql-server is using mixed authentication. the user account is created and has access to the db (verified).

There's no firewall blocking: The TCP/IP network access was disabled! Enabling it did the trick!

Thanks Eric!

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Advanced installation problems (DNN 3.3.4 + W2k3)Advanced installation problems (DNN 3.3.4 + W2k3)


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