Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jun 30, 2012 07:44 PM by RichardL1969
Jun 30, 2012 01:09 PM|LINK
I've suddenly started getting an error with my mdf database within Web Developer 2010 Express.
The database was initially set up using the ASP.NET website template, and I'd added a few small tables to the database.
These had been working fine, with no issues.
However (suspiciously coinciding with my machine grinding to a half as the weekly scan kicks in) I first got an error when my page took an age to load in the browser, before failing with a stack trace.
The top of the error says...
[SqlException (0x80131904): Cannot open user default database. Login failed.
Login failed for user 'mypc-PC\me'.]and now if I try to view the database through database explorer I get the same message as a pop-up.Bearing in mind this database has been working fine for a few days, any ideas why it should have stopped working, and how I can login again?It's obviously decided that my login isn't valid, but I've no idea why, or how to make it valid again.
Jun 30, 2012 03:33 PM|LINK
Have you set password expired policy for SQL Server
Jun 30, 2012 04:30 PM|LINK
Not that I'm aware of. How would I check?
Note that this error is in Web Developer, not SQL Server. Management studio R2 won't even open this type of mdf file.
I also checked against another website that also uses an ASPNETDB database, and that no longer works either.
Jun 30, 2012 04:54 PM|LINK
First Check SQL Server is running or not
If running then open SQL Server and try to login with the id you mentioned
If not able to login. Try to login with other ID.
After login go to Security -> Logins -> Right Click on the User you mention and Click Properties
In the Login Properties Child Window change password.
If you want uncheck Enforce password policy or Enforce password expiration checkboxes.
Jun 30, 2012 07:44 PM|LINK
Thanks, but I think it might have been a problem with my virus scanner bodging something up by making everything slow and timing out, and maybe other stuff besides.
I left my pc for a few hours and let the virus scan finish, and then rebooted, and it's fine now.
I don't really understand it, but even in this day and age "have you tried turning it off and on again?" still seems to be a valid solution.
Thanks for your help anyway.