Hopefully I am posting in the right newsgroup...
I am trying to troubleshoot an issue with a user who needs to access a SQL 2000 database from Ubuntu. He is passing the following command which is generating the error below (I've blocked out the IP Address):
tsql -H XXX.XXX.XXX.XXX -p 1433 -U Username TestUser -P TestPassword -D TestDatabase
locale is "en_CA.UTF-8" locale charset is "UTF-8" Default database being set to TestDatabase Msg 18456, Level 14, State 1, Server , Line 0 Login failed for user 'TestUser'. Msg 20002, Level 9, State -1, Server OpenClient, Line -1
Adaptive Server connection failed There was a problem connecting to the server
Furthermore, when we pass his Windows username and password, it works fine. The issue occurs only with the SQL login. I have used Query Analyzer to connect to the server using the SQL login and confirmed it worked successfully.
I found this article to help troubleshoot, but the problem is it doesn't list the solution for state 1 (which you can see is part of the error above). http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
Any help would be greatly appreciated!
Thanks,
Rubens
Rubens - 26 Nov 2008 19:39 GMT
Please disregard, the issue was related to a character in the password.
Thanks,
Hopefully I am posting in the right newsgroup...
I am trying to troubleshoot an issue with a user who needs to access a SQL 2000 database from Ubuntu. He is passing the following command which is generating the error below (I've blocked out the IP Address):
tsql -H XXX.XXX.XXX.XXX -p 1433 -U Username TestUser -P TestPassword -D TestDatabase
locale is "en_CA.UTF-8" locale charset is "UTF-8" Default database being set to TestDatabase Msg 18456, Level 14, State 1, Server , Line 0 Login failed for user 'TestUser'. Msg 20002, Level 9, State -1, Server OpenClient, Line -1
Adaptive Server connection failed There was a problem connecting to the server
Furthermore, when we pass his Windows username and password, it works fine. The issue occurs only with the SQL login. I have used Query Analyzer to connect to the server using the SQL login and confirmed it worked successfully.
I found this article to help troubleshoot, but the problem is it doesn't list the solution for state 1 (which you can see is part of the error above). http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
Any help would be greatly appreciated!
Thanks,
Rubens