Issue using the JDBC driver to connect to a remote server

Hi All,

We have a customer in Japan who's using our tool to connect to their SQL Server. Our application runs on a Linux machine and uses the MSSQL JDBC driver for connectivity.

We're getting errors back that are not-decipherable because, I presume, they're in Japanese, and then our logs don't log them in Unicode, so they get flattened out as question marks. The errors come out looking something like this:

Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]? 'MSSQL'

?

SQL State: HY000

SQL Code: 4060

[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]? 'sa' ?

SQL State: 28000

SQL Code: 18456

[Microsoft][SQLServer 2000 Driver for JDBC]An error occured while attempting to

log onto the database.

SQL State: 08001

SQL Code: 0

I think we could troubleshoot the problem if we could only read the errors coming back. I know in the ODBC world there are options like "Change the language of SQL Server system messages" and "Perform transaltion for character data" in the ODBC control panel. I couldn't find any similar options available in the JDBC driver however. Do they exist?

Even if they don't, just scanning the messages makes it pretty clear that there's an authentication/permissions issue at work here. We have another app using the same credentials that works fine though - so if there are any known issues about using JDBC to authenticate in a multi-lingual environment, that would be helpful too. Our tcpdumps seem to suggest that the JDBC driver is using multi-byte strings when communicating with the server, however the "working" application is using single-byte encoding. Could that be why we're not authenticating? How is that controlled? Note that at this point I'm just talking about authentication, not the codepages/encodings of the data in the database - right now I'm just worried about logging in.

Thanks!
Tom

I do not think app using single byte encoding should make any difference when logging in. You really should get the error string in English to understand what is going on.

|||

Error 4060 is "Cannot open database "..." requested by the login. The login failed.", 18456 is "Login failed for user ...".

I am moving to the "SQL Server Security" forum for further follow-up.

Issue publishing reports under Win2k3

I'm trying to publish some reports using the RS tool under Windows
Server 2003 SBS.
It works fine under Win XP but using SBS I get the messages
"The operation you are attempting requires a secure connection
(HTTPS)."
Any ideas?
Cheers
Chris.The rs script uses rs.CreateReport
and this is where the exception occurs.|||On 18 Jun, 18:54, theinvisibleGhost <theinvisibleGh...@.yahoo.com>
wrote:
> The rs script uses rs.CreateReport
> and this is where the exception occurs.
I found a similar message here:
http://groups.google.co.uk/group/microsoft.public.crm/browse_thread/thread/4b3872a882e9bcd7/bdba3dfc3d002231?lnk=st&q=Microsoft.ReportingServices.Diagnostics.Utilities.SecureConnectionRequiredException&rnum=1&hl=en#bdba3dfc3d002231
It didn't resolve my issue but I found that my virtual directorys were
corrupted in someway.
I deleted them and then recreated them and my issue was resolved.

ISQL/W - SQL graphical query tool

hi, i have an error when i open the query analizer and press F1 to use the
help, the error that is displayed to say :
ISQL w - graphical query tool
ISQL/w - SQL graphical query tool to detected a throuble and had to close
...
and i can not use the help, may someone help me, please?
thanks
JJ_ wrote:
> hi, i have an error when i open the query analizer and press F1 to
> use the help, the error that is displayed to say :
> ISQL w - graphical query tool
> ISQL/w - SQL graphical query tool to detected a throuble and had to
> close ...
>
> and i can not use the help, may someone help me, please?
>
> thanks
Install the SQL Server Service Pack 3a on the client PC and see if that
helps.
David G.
|||David,
I Install the SQL Server Service Pack 3a on my PC and nothing, the error is
displayed again when I want to raise the help to press F1, do you have
another idea, please?
thanks
"David G." wrote:

> JJ_ wrote:
> Install the SQL Server Service Pack 3a on the client PC and see if that
> helps.
> --
> David G.
>
|||When I start QA and press F1, this is the help file that opens:
C:\Program Files\Microsoft SQL Server\80\Tools\Books\startsql.chi
Do you have this file?
David Gugick
Imceda Software
www.imceda.com