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 ...SQL Express Login issuesSQL Express Login issues
Previous
 
Next
New Post
1/14/2008 11:47 AM
 

I am having some moderate to severe issues with accessing my portal locally. I have not deployed it to the web server yet, but have not had any issues accessing the portal to work on it. It is configured with SQL Express 2005 and my DNN version is 4.7. I am now getting a message when I run the web app from Visual Studio 2005 that states the following:

This site is currently Unavailable

Please check back later

I close the application and try to re-run it and get the following:

System.Data.SqlClient.SqlException: Cannot open user default database. Login failed.
Login failed for user 'computerName\ASPNET'.

If I do an IIS reset I get the first message again.

I have added the computerName\ASPNET in the server security settings/logins on SQLExpress and added the user with dbo rights. I am still getting the above error. I know this is probably something simple ... but I'm out of ideas. Any suggestions would be greatly appreciated.

 

 
New Post
1/14/2008 3:24 PM
 

Rob,

I would suggest logging in to your database using the SQL Express Management Studio and the credentials that your app is using. Most importantly you want to make sure that your user can access the database, but then you also need to make sure you have permissions to create tables, execute stored procs, etc...and this is something that might be easier to do a quick test in Management Studio than trying to use the application.

One thing I noticed is that you're getting a specific error message about the default database -- can you check to see what this user's default databse is?

Take care,

Ian


Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
New Post
1/15/2008 3:19 PM
 

Ian,

Thanks for the quick response. The user has dbo.owner privileges. I located the culprit about 30 minutes ago, although I don't know why the setting changed. The App_Data directory on the web server was set to read-only and the child files did not have permissions to access the database. I reset these to full permission and everything works again. Do you have any idea how these permissions may have gotten changed?  The only thing I did was to open the database in Management Studio and add  a table and a stored proc to handle a contacts module I was writing.

Thanks again,

Rob

 
New Post
1/16/2008 12:40 PM
 

Rob,

I can't say that I have experienced this issue before, although I'm guessing that a certain step you may have taken triggered SQL Server to reset those permissions. I am aware of other scenarios in which SQL Server will explicitly change file permissions (attaching and detaching a database), so it may be a reasonable assumption that it could change permissions in other contexts as well.

My apologies for not having a more in-depth understanding, but I'm glad you corrected your issue!

Take care,

Ian


Software Engineer
Co-Founder, dnnGallery
Stack Overflow: Ian Robinson
Twitter: @irobinson
Linked In: Ian Robinson
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SQL Express Login issuesSQL Express Login issues


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