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 ...DNN Error: Connection To The Database Failed (SQL not working on Server 2008)DNN Error: Connection To The Database Failed (SQL not working on Server 2008)
Previous
 
Next
New Post
3/29/2018 6:51 PM
 
Not according to this article which explicitly states that each AppPoolIdentity is unique. https://docs.microsoft.com/en-us/iis/... - the only way I know of to run them all under DefaultAppPool is if all the sites are running in that Pool.


>>Also, how do I map each DNN website database without attaching each database?
I don't know about this. My notes are for the case of a 'normal' (my wording) database that is permanently attached and available to SQL Server. If you are doing something else then I doubt that my notes apply.

Why are your databases not permanently attached?

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
3/29/2018 7:16 PM
 
Richard Howells wrote:
Why are your databases not permanently attached?

 They never have been.  I've been using DNN since version 2.x, now I'm running sites using both 7.4.2 and 9.1.1, and I've never had to attach any DNN database to get it to work. 

 
New Post
3/29/2018 7:24 PM
 
Fair enough.

I have no knowledge of how security is managed for such databases. What I wrote may well not apply to your situation.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
3/30/2018 4:30 PM
 
As another example, if I try to create a new DNN website from scratch, I get the following from the wizard



ERROR:Index #: 0
Source: .Net SqlClient Data Provider
Class: 14
Number: 15372
Message:
 
New Post
4/2/2018 9:39 PM
 
Still looking for answers.  Here is a listing from the DNN Logs:



2018-04-02 17:32:45,090 [MachineName][Thread:20][ERROR] DotNetNuke.Data.PetaPoco.PetaPocoHelper - [3] Error executing SQL: ;Exec dbo.GetEventLogType
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
2018-04-02 17:32:45,090 [MachineName][Thread:20][ERROR] DotNetNuke.Services.Exceptions.Exceptions - System.Data.SqlClient.SqlException (0x80131904): Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.Open()
   at PetaPoco.Database.OpenSharedConnection()
   at DotNetNuke.Data.PetaPoco.PetaPocoExt.ExecuteReader(Database database, String sql, Object[] args)
   at DotNetNuke.Data.PetaPoco.PetaPocoHelper.ExecuteReader(String connectionString, CommandType type, Int32 timeoutSec, String sql, Object[] args)
   at DotNetNuke.Data.SqlDataProvider.ExecuteReader(String procedureName, Object[] commandParameters)
   at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.<>c.<GetLogTypeInfo>b__25_0(CacheItemArgs c)
   at DotNetNuke.Common.Utilities.DataCache.GetCachedDataFromRuntimeCache(CacheItemArgs cacheItemArgs, CacheItemExpiredCallback cacheItemExpired)
ClientConnectionId:af066594-fb15-456f-aeba-72e0fdc46e3d
Error Number:15372,State:1,Class:14
2018-04-02 17:32:45,105 [MachineName][Thread:20][ERROR] DotNetNuke.Data.PetaPoco.PetaPocoHelper - [3] Error executing SQL: ;Exec dbo.GetEventLogType
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
2018-04-02 17:32:54,575 [MachineName][Thread:7][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
2018-04-02 17:32:59,052 [MachineName][Thread:7][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
2018-04-02 17:33:00,019 [MachineName][Thread:7][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
2018-04-02 17:33:01,064 [MachineName][Thread:7][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
2018-04-02 17:33:01,844 [MachineName][Thread:12][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
2018-04-02 17:33:02,531 [MachineName][Thread:12][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
2018-04-02 17:33:02,952 [MachineName][Thread:12][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
2018-04-02 17:33:03,326 [MachineName][Thread:12][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
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN Error: Connection To The Database Failed (SQL not working on Server 2008)DNN Error: Connection To The Database Failed (SQL not working on Server 2008)


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