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 ...Connection to the database failed (moving to local server)Connection to the database failed (moving to local server)
Previous
 
Next
New Post
1/29/2017 5:53 PM
 
Hallo,
nice to be back to the community after a long time!
I'm facing a very singular issue. I'm copying a production install of a DNN 7.3.3 to my local development machine.
I have SQL Server 2012 installed in localhost with IIS on my local machine, while I have 2 separate servers in production.
I have other 2-3 DNN installs on my local machines which regularly access the database, that I use for module development.
I need to do the same with this new site.
I modified the web.config connection strings to point at "localhost" for the DB server(which is already working fine for the other DNN installs so no TCP/IP or firewall issues).
I restored the DB inside SQL Server, recreated the user login and fixed the orphaned users to re-associate the login to the DB user.
Things I do normally, so nothing new here really.
About folder security I associated the root folder to the IIS application pool tied to the local website I created (which by the way is the same application pool of the other websites that actually do work fine).

So I'm really lost at this point.
Looking at the logs I just have:
2017-01-29 18:15:56,049 [MyPC-PC][Thread:22][ERROR] DotNetNuke.Common.Initialize - The connection to the database has failed, however, the application is already completely installed, a 500 error page will be shown to visitors. No other clue.

I restarted the IIS, I restarted SQL Server, I restarted the whole machine. No luck.

Some hint before I really go mad would be really appreciated.
Thanks in advance
 
New Post
1/29/2017 7:20 PM
 
AFAIR, DNN 7.3 still has two connection strings, did you make sure, both as identical?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
1/30/2017 4:19 PM
 
Yes my friend, changed both to localhost as for the db server location.
 
New Post
1/30/2017 7:18 PM
 
are you using default instance? if you installed SQL Server Express, it installs as instance "(localhost)\sqlexpress" (or ".\sqlexpress")

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
1/31/2017 10:10 PM
 
I don't have SQL Express installed.

Those are both the SQL strings of the NON WORKING site:

<add name="SiteSqlServer" connectionString="Data Source=localhost;Initial Catalog=mycatalog.com;User ID=my.user.com;Password=123abc" providerName="System.Data.SqlClient" />

<add key="SiteSqlServer" value="Data Source=localhost;Initial Catalog=mycatalog.com;User ID=my.user.com;Password=123abc" />

And this is (one of the two) SQL strings of the working site on the same local machine:

<add name="SiteSqlServer" connectionString="Data Source=localhost;Initial Catalog=dnndev.me;User ID=dnndev.me;Password=dnndev.me" providerName="System.Data.SqlClient" />


 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Connection to the database failed (moving to local server)Connection to the database failed (moving to local 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