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 ...CanCan't connect to database after backup
Previous
 
Next
New Post
12/5/2006 3:10 PM
 

I have a working dnn site.  I've created several modules and corresponding tables in the database and everything works great.  Then, I open SQL Server Management Studio Express, attach to the database, backup the database, detach from the database and I can no longer attach to the db from dnn (error shown below).  I can open the database from Visual Studio and see my tables, but I cannot run the application.  Rebooting doesn't help.  I've even tried copying over the database with a prior copy.  It still doesn't work.  The only way I have found to reconnect to the database is to copy over the entire dotnetnuke install directory with a copy I made prior to the backup.  Then it works again. 

Anyone else had this behavior?  How do I fix it?

Thanks

Mark

 

-----------------  DB ERROR BELOW --------------------------------------

DotNetNuke Upgrade Error

The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

Cannot open user default database. Login failed. Login failed for user 'PARAPRO1\ASPNET'.

 
New Post
12/23/2006 7:25 AM
 
This could be a "schema" (databaseowner) issue.

        <add name="SqlDataProvider" type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider" connectionStringName="SiteSqlServer" upgradeConnectionString="" providerPath="~\Providers\DataProviders\SqlDataProvider\" objectQualifier="dnn_" databaseOwner="dbo" />
Check on your database and web.config file which is the configured value ("dbo" by default, but I guess is another in your case) and check on the database that the schema exists and has the right permissions.

HTH,
Horacio Judeikin.-
 
New Post
12/26/2006 7:01 AM
 

Here's the solution to the database connection problem I experienced after attaching the Database.mdf file with SQL Server Management Studio Express.

http://www.dotnetnuke.com/tabid/825/EntryID/1202/Default.aspx

Hope this helps.

 

 
New Post
12/26/2006 5:34 PM
 

Thanks Horatio.  I'm not sure how to check permission on the schema.  My web.config connection strings (below) do not specify a db owner.  Do they need to?  I can connect with VS 2005 Server Explorer after I modify with SQL Express Manager, but I cannot connect with dnn site. 

<add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|ParaPro.mdb;" providerName="System.Data.SqlClient"/> 

<

Thanks for your help. 

add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|ParaPro.mdb;"/>
 
New Post
12/26/2006 5:36 PM
 

TLanier

Thanks for your help also.  I followed the article, but I still get the same error.  When you modified the attached name did you keep the .mdf extension on the name?

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...CanCan't connect to database after backup


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