Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...SqlExpress - could not connect to database specified in connectionString for SqlDataProviderSqlExpress - could not connect to database specified in connectionString for SqlDataProvider
Previous
 
Next
New Post
11/8/2006 5:28 PM
 
Andreas Kyster

Joined: 8/18/2006
Posts: 9

Hi all

I have digged into this and found something that might help to resolve this.

During an installation of SQL Server Express you are faced with a decision related to instances: Default instance or Named instance. I chose Default instance and hence my instance is called MSSQLSERVER, and no, just changing the instance name in the connection strings doesn't fix the problem. If you choose Named Instance, it is called SQLEXPRESS, and this might work with the default connection string in DNN.

Could it be that the connection string is different for a default instance ??

Now I will try to reinstall SQL Server with a named instance, brb.
 
New Post
11/8/2006 6:23 PM
 
Andreas Kyster

Joined: 8/18/2006
Posts: 9

Hi all

In case you chose as I did in my previous post to install SQL Server as a Default Instance, you can breathe easy.

I have just reinstalled SQL Server Express as a Named Instance and the install ran with the default connectionstring, I only changed the DB name of course.

Yeehaaaa !!
 
New Post
6/6/2007 2:26 PM
 
Ereck Johan

ereckjohan@writewire.net
Joined: 1/17/2006
Posts: 14

A couple of things on this I found:

1) If IIS is installed after .Net 2.0, you must run the repair process on .Net 2.0 so that the ASP.Net account (or Network Service) gets the appropriate permissions on the metabase directory.

2) Make sure that the ASP.Net account (or Network Service) has write permissions on the virtual root and all sub files and folders.

3) In some cases, the message appears to be related to an inability to create the database.ldf file.  I had to stop IIS (otherwise another process was attaching the file) and kill all instances of SQL Express running through Task Manager/Processes.  Then open the database.mdf file in SQL Studio to generate the database.ldf manually.   The actual failure message was "asp.net account login failure) when really it was a failure related to trying to open the .ldf file which it then could not create for some reason.

Once the permissions were set and the .ldf file was created the installation was successful.  The trickest part with this was that SQLExpress generates instances per user meaning my own ID as well as ASP.net and Network Service.  So kill all instances to ensure that the files are not locked by another instance process.  If you get the failure during installation you have probably locked the database.mdf file with the failed instance.
 
New Post
8/16/2007 12:37 PM
 
mark richardson

Joined: 7/30/2007
Posts: 501

 

Another one having problems....

I have no default website and this is the name of my development server:
"sypadevelopment"

therefore my install file seems to be here:
http://sypadevelopment/DotNetNuke_2/Install/install.aspx

If I enter http://localhost/DotNetNuke_2/Install/install.aspx
I get a 'page not found message'

my connection string is:

connectionString="Server=(sypadevelopment);Database=DotNetNuke_2;uid=****;pwd=****;"

I have tried changing server name to "Server=(local) but I get the same error message.

I used a multitude of connection strings from: http://www.connectionstrings.com/?carrier=sqlserver2005 (tried all .NET ones)

There is nothing I can do to the connection string to make it work.

My security permisions are set for ASPNET (full control / and tried read & write etc) (using IIS 5.1)

any ideas?

I am running XP Pro service pack 2 , with IIS 5.1
version installed: 'DotNetNuke_04.05.05_Install' file.


Connection Error(s):
Index #: 0
Source: .Net SqlClient Data Provider
Class: 16
Number: 1813
Message: Could not open new database 'C:\INETPUB\WWWROOT\DOTNETNUKE_2\WEBSITE\APP_DATA\DATABASE.MDF'. CREATE DATABASE is aborted.

Index #: 1
Source: .Net SqlClient Data Provider
Class: 14
Number: 15350
Message: An attempt to attach an auto-named database for file C:\Inetpub\wwwroot\DotNetNuke_2\website\App_Data\database.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

Index #: 2
Source: .Net SqlClient Data Provider
Class: 0
Number: 5111
Message: File activation failure. The physical file name "C:\Inetpub\wwwroot\DotNetNuke_2\website\App_Data\database_log.ldf" may be incorrect.

Index #: 3
Source: .Net SqlClient Data Provider
Class: 0
Number: 5129
Message: The log cannot be rebuilt when the primary file is read-only.
........................................................................

 
 
New Post
8/16/2007 4:55 PM
 
Ereck Johan

ereckjohan@writewire.net
Joined: 1/17/2006
Posts: 14
Is the database created already?  If not, try creating an empty database, with the name you specify in the connection string, instead of letting the install process create it.  I have found this usually works every time during installation.  It leaves me to believe there is a permission or security context problem with database creation through install.  When I get a moment I will debug it.
 
 Page 2 of 4
Previous1234Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SqlExpress - could not connect to database specified in connectionString for SqlDataProviderSqlExpress - could not connect to database specified in connectionString for SqlDataProvider


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