15 Nisan 2012 Pazar 01:22
15 Nisan 2012 Pazar 04:42Do you see any records in the ERROR.LOG?
Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/
15 Nisan 2012 Pazar 09:37
So more exactly what error message do you get for these login failures?
From your description, my guess is that they are not able to connect to the database they want to connect to. In any case, if you dropped the logins and recreated them, you have caused some damage, since the logins no longer match the database users. (Since you talk about passwords, I assume that you have SQL logins.) You need to use sp_change_users_login to fix this. Once you have done this, attempt to connect from OSQL with:
osql -S server -U user -P pwd -d db
to see that these logins are able to connect to the databases.
Erland Sommarskog, SQL Server MVP, firstname.lastname@example.org
- Yanıt Olarak Öneren Peja TaoModerator 16 Nisan 2012 Pazartesi 08:12
16 Nisan 2012 Pazartesi 14:27ModeratörOne more simple guess... Is your server configured in Mixed mode authentication?
Mark as ANSWER if I helped you today :-)
16 Nisan 2012 Pazartesi 14:28
Thanks Erland. The user(s) that's associated with the login(s) are not orphaned. And I am able to connect to SQL using SSMS/ Enterprise Manager either locally/ remotely with the credentials as that of the logins used by the webservers/ filenet.
I had tried using OSQL utility and I am able to get the results as desired.
16 Nisan 2012 Pazartesi 15:21
I don't see any login failure messages written in either the sql server logs/ event viewer logs. Thanks.
16 Nisan 2012 Pazartesi 15:22Yes it is, I guess I wouldn't have been able to connect to SQL using SSMS/ Enterprise Manager had it not been configured as mixed authentication mode.
16 Nisan 2012 Pazartesi 18:17I was able to resolve the issue. The collation option set on the server is Latin1_General_BIN which is case sensitive. One of the databases which's the default database for the sql logins had a different name in that the case was not specifed correctly. Once that's corrected, everything worked.
- Yanıt Olarak İşaretleyen Rocky_SQL_DBA 16 Nisan 2012 Pazartesi 18:17