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 ...web.config settings for Sql 2005 Express and DNN4  - HELP!!!!!!!!web.config settings for Sql 2005 Express and DNN4 - HELP!!!!!!!!
Previous
 
Next
New Post
12/3/2006 11:29 PM
 

Ahhh, I see.  Thank you for clearing that up.

But, with all due respect, why isn't this - clearly - documented?  The latest install is 4.3.7, the latest docs, although they say 4.3.7 link to 4.3.1.  I can't possibly be the only person who has hit their head against a wall with this.  This is rather disappointing.

- Mark

 

 

 

 
New Post
12/4/2006 6:46 AM
 

hello sir,

                  i am installing dotnetnuke4.0.3. i am using a database which is on a remote machine its giving me an error that : Could not connect to database specified in connectionString for SqlDataProviderSystem.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server.

    what should i do to resolve this error.

 
New Post
12/4/2006 9:56 AM
 



hirma wrote . . .

I am installing dotnetnuke 4.0.3. i am using a database which is on a remote machine its giving me an error that : Could not connect to database specified in connectionString for SqlDataProviderSystem.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server.

what should i do to resolve this error.




hirma,

In order to better help you, can you please Reply a post and include the following info:

(a) Do you know the URL for your database?
(b) Do you know the name of that database?
(c) Do you know the user name and password for that database?
(d) Can you please post the section called "ConnectionStrings" from your web.config file ? (Note: In order for your code to be visible in your Reply post, you might need to replace character '<' with '*' and replace '>' with '&'.

(e) Do you know if the remote database is SQL Server? Or is it MySQL ?

Thanks,
Travis
 
New Post
12/4/2006 2:32 PM
 
smsolutions wrote

Ahhh, I see.  Thank you for clearing that up.

But, with all due respect, why isn't this - clearly - documented?  The latest install is 4.3.7, the latest docs, although they say 4.3.7 link to 4.3.1.  I can't possibly be the only person who has hit their head against a wall with this.  This is rather disappointing.

- Mark

1) d there have been numerous post on the forums about SQLExpress

www.dotnetnuke.com/Community/BlogsDotNetNuke/tabid/825/EntryID/1202/Default.aspx
www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/78613/scope/posts/Default.aspx
www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/82012/scope/posts/Default.aspx

2) We cannot document all the possible scenerios  that a user might come across.  The main problem that we had here was that you tried to use the "Initial Catalog" instead of the "Database" attribute.  I am not sure SQLExpress does not support the Initial Catalog setting (based on other forums post I have read).  In the core web.config files sent in the package neither of the 2 sample connectionStrings use Initial Catalog.

-- Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;

-- Server=(local);Database=DotNetNuke;uid=;pwd=;

If you had simply used the 2nd connectionString and put in your Database name, UID and PWD you would have been up and running without any issues.  The only other thing you might have had to change is (local) to ./SQLExpress (or whatever you names your SQL instance).

Again, we do try to document as much as possible but we can only do so much and when we see something that is causing problems we try to resolve the issue and blog about it.  The blog I did on using SQL Express / SQL Managements Studio is a good example of that and I spent a good part of day testing different scenerios so that a completed solution could be posted (based on the number of community members that were having similar problems).

We can do a better job of documenting, but compared to some other open-source projects we do a pretty decent job.  On the other hand, the forums / blogs are a way to document things so please use them as much as possible when looking for help.
 
New Post
12/6/2006 11:39 PM
 



smehaffie wrote . . .

smsolutions wrote

Ahhh, I see. Thank you for clearing that up.

But, with all due respect, why isn't this - clearly - documented?

- Mark

The blog I did on using SQL Express / SQL Managements Studio is a good example of that and I spent a good part of day testing different scenerios so that a completed solution could be posted (based on the number of community members that were having similar problems).




Shawn --

Indeed, this blog you made is incredibly valuable to me. I used it successfully to configure access to the database from both DNN and SQL Server Management Express without having them fight/kill the other's access. I did have one process problem right at the end of my journey which I have documented in this thread here. I would be grateful if you can check that thread out. Thanks!

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...web.config settings for Sql 2005 Express and DNN4  - HELP!!!!!!!!web.config settings for Sql 2005 Express and DNN4 - HELP!!!!!!!!


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