patternMinor
Password mismatch while logging to sql server
Viewed 0 times
loggingwhilesqlpasswordservermismatch
Problem
Alright, I have a classic asp application and I have a connection string to try to connect to db.
MY connection string looks as follows:
Now when I'm accessing db though front-en I get this error:
I looked in the sql profiler and I got this:
What I've tried:
*checked 100 times that my password is actually correct.
*Tried this:
*Enable ALL possible permissions for this account in SSMS.
* I've tried this connection string:
And I got this error:
MY connection string looks as follows:
Provider=SQLOLEDB;Data Source=MYPC\MSSQLSERVER;Initial
Catalog=mydb;database=mydb;User Id=me;Password=123Now when I'm accessing db though front-en I get this error:
Microsoft OLE DB Provider for SQL Server error '80040e4d'
Login failed for user 'me'.I looked in the sql profiler and I got this:
Login failed for user 'me'. Reason: Password did not match that
for the login provided. [CLIENT: ]
Error: 18456, State:8.What I've tried:
*checked 100 times that my password is actually correct.
*Tried this:
alter login me with check_policy off (Do not even know why I did this)*Enable ALL possible permissions for this account in SSMS.
* I've tried this connection string:
Provider=SQLOLEDB;Data Source=MYPC\MSSQLSERVER;Initial Catalog=mydb;database=mydb; Integrated Security = SSPIAnd I got this error:
Microsoft OLE DB Provider for SQL Server error '80004005' Cannot open database mydb requested by the login. The login failed.Solution
The only times I have ever seen the State 8 error for 18456 (Password Mismatch) was in fact a password mismatch. Try a new password. Type it in notepad, copy and paste it to SQL and then do the same into your app config. Make sure nothing is happening to that password when it is being handed off to SQL - no trimming, extra spaces, etc.
But then the second error you got seems to indicate you may have gotten past that bad password error and are now unable to access your database.
That can be one of a few things:
1.) Verify the database specified really does exist.
2.) Verify that the login you are using has been granted appropriate permissions into that database (If the permissions are at the SQL Server system administrator level then this shouldn't be a necessary step)
That's where I'd start anyway.
But then the second error you got seems to indicate you may have gotten past that bad password error and are now unable to access your database.
That can be one of a few things:
1.) Verify the database specified really does exist.
2.) Verify that the login you are using has been granted appropriate permissions into that database (If the permissions are at the SQL Server system administrator level then this shouldn't be a necessary step)
That's where I'd start anyway.
Context
StackExchange Database Administrators Q#7181, answer score: 3
Revisions (0)
No revisions yet.