JDBC Unsupported Encoding

Thread view:

SMMT - 07 May 2004 01:33 GMT

Hi,

I'm using JDBC to connect to SQL Server 2000 running under windows 2000
server.
Here is the thing. I have another machine , windows 2000 pro that can
connect with the same server. Running the program in w2k pro all is fine,
but running it under w2k server it spits the error
[Microsoft][SQLServer 2000 driver for JDBC] Unsopported VM encoding Cp437.

This is very stange error that only ocurs when I try to access to the server
from the server machine it self. This as something related with the code
page (cp) 437.
Does any one kown what make this error or how can i get read of it?

Reply to this Message

Roedy Green - 07 May 2004 01:59 GMT

>[Microsoft][SQLServer 2000 driver for JDBC] Unsopported VM encoding Cp437.

Cp437 is the old DOS encoding with the line drawing set, used on
Hercules, and monochrome video adapter cards.

Surely it is supported in the Java you are running. Perhaps SQL
Server does not like receiving messages encoded that way.

I would read up on the encodings used by JDBC to see what can be done.

See http://mindprod.com/jgloss/encoding.html

You can test for support with the nativetoascii utility.

--
Canadian Mind Products, Roedy Green.
Coaching, problem solving, economical contract programming.
See http://mindprod.com/jgloss/jgloss.html for The Java Glossary.

Reply to this Message

SMMT - 07 May 2004 02:07 GMT

"Roedy Green"

> >[Microsoft][SQLServer 2000 driver for JDBC] Unsopported VM encoding Cp437.
>
[quoted text clipped - 3 lines]
> Surely it is supported in the Java you are running. Perhaps SQL
> Server does not like receiving messages encoded that way.

The thing is.: the program is the same , in the same "javanese". Runnig it
in one machine has no problems. Running it in the other (the one with the
SQL server in it) has that problem. Both machines connect to the same sql
server. If the problem is SQL server it should give an error while running
in either machine, but it only does with one ... that is the odd thing ...

:-(

Reply to this Message

Roedy Green - 07 May 2004 02:47 GMT

>The thing is.: the program is the same , in the same "javanese". Runnig it
>in one machine has no problems. Running it in the other (the one with the
>SQL server in it) has that problem. Both machines connect to the same sql
>server. If the problem is SQL server it should give an error while running
>in either machine, but it only does with one ... that is the odd thing ...
>:-(

Check the localization of each machine.

You can use Wassup to check the system properties.

Go in to the control panel and see the localisation.

See http://mindprod.com/wassup.html
--
Canadian Mind Products, Roedy Green.
Coaching, problem solving, economical contract programming.
See http://mindprod.com/jgloss/jgloss.html for The Java Glossary.

Reply to this Message

SMMT - 07 May 2004 23:26 GMT

I thinks is a bug on the SQLServer JDBC Driver for XP and Windows 2K server.
I changed to jdbc-odbc bridge for the time being...no more time for strange
things like this

Reply to this Message

JDBC Unsupported Encoding

Free Magazines