October 14, 2017 at 10:35 am
Hi all,
Application team getting following error message when they are trying to connect to the SQL DB instance from linux/unix box. And ‘microsoft\sqldba' domin account already have sysadmin permission on the SQL DB instance.
Please suggest me how should I resolve this issue further.
Failed connecting to the database <Database >.
ODBC Error
SQLCODE: 18456
SQLSTATE: 46
MESSAGE: [DataDirect][ODBC 20101 driver][20101]Login failed for user ‘microsoft\sqldba'.
Thanks in advance!!
SQL server DBA
October 14, 2017 at 10:42 am
Database admin(DBA) - Saturday, October 14, 2017 10:35 AMHi all,
Application team getting following error message when they are trying to connect to the SQL DB instance from linux/unix box. And ‘microsoft\sqldba' domin account already have sysadmin permission on the SQL DB instance.
Please suggest me how should I resolve this issue further.Failed connecting to the database <Database >.
ODBC Error
SQLCODE: 18456
SQLSTATE: 46
MESSAGE: [DataDirect][ODBC 20101 driver][20101]Login failed for user ‘microsoft\sqldba'.Thanks in advance!!
You have a domain called 'Microsoft'?!
What is your full connection string?
October 14, 2017 at 10:56 am
That looks like you're trying to connect via an AD account, however, Unix/Linux doesn't natively support Domain Authentication.
Can I assume that you do indeed have kerboros installed on your Linux server, and it's all configured correctly to authenticate to your Domain Controller? I also assume that you are logged into the Unix Server as Microsoft\sqldba, or have used su sqldba in bash.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
October 14, 2017 at 11:47 am
Phil Parkin - Saturday, October 14, 2017 10:42 AMDatabase admin(DBA) - Saturday, October 14, 2017 10:35 AMHi all,
Application team getting following error message when they are trying to connect to the SQL DB instance from linux/unix box. And ‘microsoft\sqldba' domin account already have sysadmin permission on the SQL DB instance.
Please suggest me how should I resolve this issue further.Failed connecting to the database <Database >.
ODBC Error
SQLCODE: 18456
SQLSTATE: 46
MESSAGE: [DataDirect][ODBC 20101 driver][20101]Login failed for user ‘microsoft\sqldba'.Thanks in advance!!
You have a domain called 'Microsoft'?!
What is your full connection string?
Thank you Phil for your quick response.No,Just i have mentioned Microsoft as domain. and i have validated connection string is fine(Port and Instance and database name) ,but i suspect that issue related to ODBC driver from UNIX box s
Do you have any thoughts how can we troubleshoot the issue further?
SQL server DBA
October 14, 2017 at 11:52 am
Thom A - Saturday, October 14, 2017 10:56 AMThat looks like you're trying to connect via an AD account, however, Unix/Linux doesn't natively support Domain Authentication.Can I assume that you do indeed have kerboros installed on your Linux server, and it's all configured correctly to authenticate to your Domain Controller? I also assume that you are logged into the Unix Server as Microsoft\sqldba, or have used su sqldba in bash.
Thank you Thom for your quick help on this and application team connection string & they have mentioned as Microsoft\sqldba account but not sure about su sqldba...
Please suggest how should i proceed further..
SQL server DBA
October 14, 2017 at 2:02 pm
Database admin(DBA) - Saturday, October 14, 2017 11:52 AMThom A - Saturday, October 14, 2017 10:56 AMThat looks like you're trying to connect via an AD account, however, Unix/Linux doesn't natively support Domain Authentication.Can I assume that you do indeed have kerboros installed on your Linux server, and it's all configured correctly to authenticate to your Domain Controller? I also assume that you are logged into the Unix Server as Microsoft\sqldba, or have used su sqldba in bash.
Thank you Thom for your quick help on this and application team connection string & they have mentioned as Microsoft\sqldba account but not sure about su sqldba...
Please suggest how should i proceed further..
What application are you using to try to connect to SQL Server? As I said before, Unix/Linux doesn't native support Integrated Security. How are you handling the impersonation?
su is a very basic unix command, which is used to impersonate a different account. If you were using sqlcmd at command line, and using integrated security, you would need to ensure you had used su to impersonate the account (or have logged in as that account). Can I assume you aren't very familiar with Unix? Trying to set up kerboros/integrated security on Unix to a Windows Domain is not the most simple of tasks; especially for someone who doesn't know the platform.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply