MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue.
If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
As Nan Yu said, you could try configure your SQL Server in Mixed Authentication Mode. Following these steps below.
1.Open SQL Server Management Studio. To do this, click Start, click All Programs, click Microsoft SQL Server 20xx (where xx is the version of SQL), and then click SQL Server Management
Studio.
2.Right-click the server, and then click Properties.
3.On the Security page, under Server authentication, click the SQL Server and Windows Authentication mode option button, and then click OK.
4. In the SQL Server Management Studio dialog box, click
OK to restart SQL Server. For more information, see
Choose an authentication mode
in SQL Server Books Online.
Besides, I suggest you could consider the following two scenarios:
Scenario 1: You are trying to connect by using SQL Server Authentication but the login used does not exist on SQL Server
To resolve this issue, verify that the SQL Server login exists. For more information, see Create
a login in SQL Server Books Online.
Scenario 2: The login may use Windows Authentication but the login is an unrecognized Windows principal
An unrecognized Windows principal means that Windows can't verify the login. This might be because the Windows login is from an untrusted domain. To resolve this issue, verify that
you are logged in to the correct domain.
Hope this can help you. If you have any question and confusion about the problem. Please don't
hesitate to let me know.
Best regards
Cathy
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue.
If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
The only scenario is close to my situation after reviewing SQL logs and verifying mix mode authentication.
but am not quite sure what does mean Windows login is from an un-trusted domain? it didn't catch this if any one can clarify this term..
Scenario 2: The login may use Windows Authentication but the login is an unrecognized Windows principal
An unrecognized Windows principal means that Windows can't verify the login. This might be because the Windows login is from an un-trusted domain. To resolve this issue, verify that you are logged in to the correct domain.
The error means that if you have chosen Windows Authentication, your machine will need to be logged into to the Network Domain. If you aren't, if you are a standalone, or Workstation for example. you will not be using Windows Authentication.
Member
36 Points
36 Posts
login fail
Aug 11, 2016 05:09 PM|omega71044|LINK
Error Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed
DB: MS SQL Server 2008 R2
Environment: Windows Server 2008 R2 - IIS 7.5
Contributor
2155 Points
2142 Posts
Re: login fail
Aug 11, 2016 08:54 PM|march11|LINK
show some of your code.
All-Star
18615 Points
3745 Posts
Microsoft
Re: login fail
Aug 15, 2016 08:46 AM|Nan Yu|LINK
Hi omega71044,
Please firstly make sure you have changed the Server authentication from Windows Authentication mode to SQL Server and Windows Authentication mode :
https://support.microsoft.com/en-us/kb/2121736
Hope it helps.
Best Regards,
Nan Yu
Please remember to click "Mark as Answer" the responses that resolved your issue.
If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
Member
36 Points
36 Posts
Re: login fail
Aug 15, 2016 05:55 PM|omega71044|LINK
it;s already checked
what should I do to resolve this issue
Star
8660 Points
2882 Posts
Re: login fail
Aug 16, 2016 02:45 AM|Cathy Zou|LINK
Hi omega71044,
As Nan Yu said, you could try configure your SQL Server in Mixed Authentication Mode. Following these steps below.
1.Open SQL Server Management Studio. To do this, click Start, click All Programs, click Microsoft SQL Server 20xx (where xx is the version of SQL), and then click SQL Server Management Studio.
2.Right-click the server, and then click Properties.
3.On the Security page, under Server authentication, click the SQL Server and Windows Authentication mode option button, and then click OK.
4. In the SQL Server Management Studio dialog box, click OK to restart SQL Server. For more information, see Choose an authentication mode in SQL Server Books Online.
Besides, I suggest you could consider the following two scenarios:
Scenario 1: You are trying to connect by using SQL Server Authentication but the login used does not exist on SQL Server
To resolve this issue, verify that the SQL Server login exists. For more information, see Create a login in SQL Server Books Online.
Scenario 2: The login may use Windows Authentication but the login is an unrecognized Windows principal
An unrecognized Windows principal means that Windows can't verify the login. This might be because the Windows login is from an untrusted domain. To resolve this issue, verify that you are logged in to the correct domain.
For more detail steps, you could refer to the link below:
https://support.microsoft.com/en-sg/kb/555332
Hope this can help you. If you have any question and confusion about the problem. Please don't hesitate to let me know.
Best regards
Cathy
Please remember to click "Mark as Answer" the responses that resolved your issue.
If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
Member
36 Points
36 Posts
Re: login fail
Aug 22, 2016 06:33 PM|omega71044|LINK
The only scenario is close to my situation after reviewing SQL logs and verifying mix mode authentication.
but am not quite sure what does mean Windows login is from an un-trusted domain? it didn't catch this if any one can clarify this term..
Scenario 2: The login may use Windows Authentication but the login is an unrecognized Windows principal
An unrecognized Windows principal means that Windows can't verify the login. This might be because the Windows login is from an un-trusted domain. To resolve this issue, verify that you are logged in to the correct domain.
Contributor
2155 Points
2142 Posts
Re: login fail
Aug 23, 2016 04:44 PM|march11|LINK
The error means that if you have chosen Windows Authentication, your machine will need to be logged into to the Network Domain. If you aren't, if you are a standalone, or Workstation for example. you will not be using Windows Authentication.
https://msdn.microsoft.com/en-us/library/ff647405.aspx
https://support.microsoft.com/en-us/kb/323176
there are differences, the security principal, if I recall, is trying to authenticate against a Domain Controller, not a local Windows installation.
https://technet.microsoft.com/en-us/library/hh831496(v=ws.11).aspx