Getting Started with Adobe After Effects - Part 6: Motion Blur


Upload Image Close it
Select File

Towards the innovative SQL ideas
Browse by Tags · View All
sql server 125
sql 124
ms sql server 119
ms sql 118
database 109
tsql 81
#SQL Server 78
t-sql 75
#sql 71
sql server general 67

Archive · View All
April 2011 14
July 2011 12
May 2011 12
August 2011 11
June 2011 10
September 2011 8
December 2011 6
November 2011 6
September 2013 5
June 2013 5

SQL Server - "Login failed for user 'username'. The user is not associated with a trusted SQL Server connection"

Sep 10 2011 12:25AM by Paresh Prajapati   

Recently i faced one more issue for login failed, this is different one from earlier and that was due to default databases deleted which was set as default for that login which failed.

Here i got same issue but slightly different and additional messages with it. The earlier was Login failed for user. This time i got Login failed for user and not associated with trusted SQL Server connection.

Problem:
I have created one login for "DBA". After successfully created with it i have assigned sysroles to user. I am very happy here because this created user is for me and i am going to use this user only which have full access of the SQL Server instance and all the objects of that instance.





After creating user i have tried to connect the SQL Server instance. But SQL Server has given me one surprise gift. This gift was " Login failed for user 'dba'. " with addition following message.

"Login failed for user '<LoginName>'.  Reason: Not associated with a trusted SQL Server connection."

Solution?
I have checked the login properties and check the assigned roles, checked it's status as enable or not. Also checked granted permission but everything are OK.

Finally i have checked SQL Server instance properties and reviewed Security section. And here i found my solution. Please see the screenshot, you can see the SQL Server Authentication was "Windows authentication". That why it was not allowed to connect instance through SQL users.



After changing SQL Authentication to SQL Server and Windows Authentication, I was able to connect SQL Server instance.

This is most common error which we faced mostly. What you want to say here?

Tags: sql, sql server 2008, sql server 2005, tsql, sql server, ms sql, ms sql server, t-sql, sql server denali, #SQL Server, sql server 2011, database, sql server general, sql errors, SQL Server Problems, login, user, #TSQL,


Paresh Prajapati
6 · 23% · 7485
3
 
0
Lifesaver
 
0
Refreshed
 
0
Learned
 
0
Incorrect



Submit

5  Comments  

  • Hi Chibaletoth,

    When you wrote "once I set the Windows Authentication ", please, could you explain what you mean ? Do you set the Windows authentification in the connection string or in the connection form of SSMS or do you want to forbid the use of the SQL Server authentification ?

    commented on Sep 13 2011 12:10PM
    Patrick Lambin
    167 · 1% · 296
  • I do faced this issue many times, I think this happens when we install default mode as windows and not mixed mode, We need to select mixed mode while we install sql server.

    commented on Sep 24 2011 8:09AM
    Hima
    31 · 6% · 1776
  • @Hima: You are absolutely correct. The root cause is the selection of features and configuration options at install time.

    Windows Authentication, being more secure is the default installation mode from SQL Server 2008 onwards. Thus, if somebody ran through the installation using the default options, and the application is using SQL users, then one is most likely to end up with this issue.

    commented on Sep 25 2011 11:41PM
    Nakul Vachhrajani
    4 · 36% · 11645
  • Recently, to deploy my site, I changed my authentication from 'Windows' to 'SQL authentication'. Successfully added the user to ‘Security\Logins’. But having problem enabling database role membership as it returns error 15247. I believe error 15151 is also that of permission issues.

    Here's an extra info in case it might help narrow down the problem scope, if i access my server it shows this error;

    "Login failed for user 'kaneXtreme' ".

    In my localhost,it shows this error;

    "The SELECT permission was denied on the object, database, schema"

    In my opinion, I think both error messages are pointing to a similar problem which is permission.

    This problem has been remained unsolved for some time now. If anyone have come across this problem before I really hope to get a few input to work around on this.

    Thank you in advance.

    commented on Jan 7 2012 6:51AM
    kanextreme
    3085 · 0% · 2
  • commented on Oct 4 2012 8:24AM
    bhaskar7698
    3085 · 0% · 2

Your Comment


Sign Up or Login to post a comment.

"SQL Server - "Login failed for user 'username'. The user is not associated with a trusted SQL Server connection"" rated 5 out of 5 by 3 readers
SQL Server - "Login failed for user 'username'. The user is not associated with a trusted SQL Server connection" , 5.0 out of 5 based on 3 ratings
    Copyright © Rivera Informatic Private Ltd Contact us      Privacy Policy      Terms of use      Report Abuse      Advertising      [ZULU1097]