By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
428,829 Members | 1,829 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 428,829 IT Pros & Developers. It's quick & easy.

Connection issue when trying to connect MS SQL SERVER from Linux

P: n/a
SRK
Hi,
I have installed free TDS ODBC driver on Linux and from there I am
trying to connect to MS SQLSERVER installed on Windows machine. But it
gives me following error -

tsql -H ps6312 -p 1433 -U shiv
locale is "en_US.UTF-8"
locale charset is "UTF-8"
Password:
Msg 18456, Level 14, State 1, Server , Line 0
Login failed for user 'shiv'.
Msg 20014, Level 9, State 0, Server OpenClient, Line 0
Login incorrect.
There was a problem connecting to the server
I am not sure what could be the reason behind this error as the user
has been configured on SQL server. Do I need to do some configuration
on SQL server side for connecting from Linux or should I have some
thing else at Linux side.
Looking forward to get reply.

Thanks in advance.

Regards
Shiv
Sep 23 '08 #1
Share this Question
Share on Google+
6 Replies


P: n/a
SRK (ku*****@gmail.com) writes:
I have installed free TDS ODBC driver on Linux and from there I am
trying to connect to MS SQLSERVER installed on Windows machine. But it
gives me following error -

tsql -H ps6312 -p 1433 -U shiv
locale is "en_US.UTF-8"
locale charset is "UTF-8"
Password:
Msg 18456, Level 14, State 1, Server , Line 0
Login failed for user 'shiv'.
Msg 20014, Level 9, State 0, Server OpenClient, Line 0
Login incorrect.
There was a problem connecting to the server
I am not sure what could be the reason behind this error as the user
has been configured on SQL server. Do I need to do some configuration
on SQL server side for connecting from Linux or should I have some
thing else at Linux side.
The login shiv is an SQL login?

You typed the password correctly?

The default datbase for this login exists?

There is no login trigger?

Are you able to connect if you use the same user/password from SQLCMD
on Windows?

--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Sep 23 '08 #2

P: n/a
SRK
On Sep 24, 2:12*am, Erland Sommarskog <esq...@sommarskog.sewrote:
SRK (kuma...@gmail.com) writes:
I have installed free TDS ODBC driver on Linux and from there I am
trying to connect to MS SQLSERVER installed on Windows machine. But it
gives me following error *-
tsql -H ps6312 -p 1433 -U shiv
locale is "en_US.UTF-8"
locale charset is "UTF-8"
Password:
Msg 18456, Level 14, State 1, Server , Line 0
Login failed for user 'shiv'.
Msg 20014, Level 9, State 0, Server OpenClient, Line 0
Login incorrect.
There was a problem connecting to the server
I am not sure what could be the reason behind this error as the user
has been configured on SQL server. Do I need to do some configuration
on SQL server side for connecting from Linux or should I have some
thing else at Linux side.

The login shiv is an SQL login?

You typed the password correctly?

The default datbase for this login exists?

There is no login trigger?

Are you able to connect if you use the same user/password from SQLCMD
on Windows?

--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se

Links for SQL Server Books Online:
SQL 2008:http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005:http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000:http://www.microsoft.com/sql/prodinf...ons/books.mspx
Hi,
I have tried using all the logins such as SQL server sa user, windows
domain user as well as shiv, which I created for SQL server. I was
able to login on windows using all the users specified above, but when
I try to connect it using free TDS odbc driver through Linux, it
fails.

Thanks
Shiv
Sep 24 '08 #3

P: n/a
SRK (ku*****@gmail.com) writes:
I have tried using all the logins such as SQL server sa user, windows
domain user as well as shiv, which I created for SQL server. I was
able to login on windows using all the users specified above, but when
I try to connect it using free TDS odbc driver through Linux, it
fails.
And you try to connect to the server you intend to? I don't see any server
specification in your command line.

Does the password contain any non-ASCII characters?

I've never used Free TDS, but since other people appears to use it, I guess
it works sometimes at least. All I can really help with is asking some
checking questions.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Sep 24 '08 #4

P: n/a
On Sep 23, 6:44*pm, SRK <kuma...@gmail.comwrote:
Hi,
I have installed free TDS ODBC driver on Linux and from there I am
trying to connect to MS SQLSERVER installed on Windows machine. But it
gives me following error *-

tsql -H ps6312 -p 1433 -U shiv
locale is "en_US.UTF-8"
locale charset is "UTF-8"
Password:
Msg 18456, Level 14, State 1, Server , Line 0
Login failed for user 'shiv'.
Msg 20014, Level 9, State 0, Server OpenClient, Line 0
Login incorrect.
There was a problem connecting to the server

I am not sure what could be the reason behind this error as the user
has been configured on SQL server. Do I need to do some configuration
on SQL server side for connecting from Linux or should I have some
thing else at Linux side.

Looking forward to get reply.

Thanks in advance.

Regards
Shiv

Hi Shiv,

I am facing the same issue , Could you share the solution with me i
you have solved the problem. I am using the FreeTDS 5.0 driver.

The erro is
locale is "C"
locale charset is "ANSI_X3.4-1968"
Msg 18456, Level 14, State 1, Server , Line 0
Login failed for user 'ibia_ir'.
Msg 20014, Level 9, State 0, Server OpenClient, Line 0
Login incorrect.
There was a problem connecting to the server.

But i am able to login using the same id from the Query Analyser.

Thanks in Advance,
Prasanna
Oct 10 '08 #5

P: n/a
(pr**********@gmail.com) writes:
I am facing the same issue , Could you share the solution with me i
you have solved the problem. I am using the FreeTDS 5.0 driver.

The erro is
locale is "C"
locale charset is "ANSI_X3.4-1968"
Msg 18456, Level 14, State 1, Server , Line 0
Login failed for user 'ibia_ir'.
Msg 20014, Level 9, State 0, Server OpenClient, Line 0
Login incorrect.
There was a problem connecting to the server.

But i am able to login using the same id from the Query Analyser.
The one thing I would check is whether the password includes any
characters not in the ASCII character set.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Oct 10 '08 #6

P: n/a
SRK
On Oct 11, 2:42*am, Erland Sommarskog <esq...@sommarskog.sewrote:
*(prasanna....@gmail.com) writes:
I am facing the same issue , Could you share the solution with me i
you have solved the problem. I am using the FreeTDS 5.0 driver.
The erro is
locale is "C"
locale charset is "ANSI_X3.4-1968"
Msg 18456, Level 14, State 1, Server , Line 0
Login failed for user 'ibia_ir'.
Msg 20014, Level 9, State 0, Server OpenClient, Line 0
Login incorrect.
There was a problem connecting to the server.
But i am able to login using the same id from the Query Analyser.

The one thing I would check is whether the password includes any
characters not in the ASCII character set.

--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se

Links for SQL Server Books Online:
SQL 2008:http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005:http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000:http://www.microsoft.com/sql/prodinf...ons/books.mspx
Thanks to all for showing interest. Actually there was issue related
to named instance and port. When I checked port for named instance, it
was different and so after changing port it worked fine. Before that I
had to enable TCP/IP on SQL server side.

thanks
Shiv
Oct 21 '08 #7

This discussion thread is closed

Replies have been disabled for this discussion.