Monday, February 20, 2012

JDBC for SQL 2000 Service Pack 4?

Am I knuts, or does SQL2k SP4 break the latest set of JDBC drivers? Can
anyone confirm?
oleitch-AT-locustcreek-DOT-com
And by "break" you mean?
Alin.
|||"Fail to work with"
JDBC will not connect (gives the 'End of stream was detected on a read'
error). Was working fine before SP4 (previously SP3).
|||Works fine for me. What is the exact error? Can you connect using OSQL.EXE?
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"end-user" <end-user@.discussions.microsoft.com> wrote in message
news:A01EF57B-01C3-4B84-A9CB-1D3E22E6BE42@.microsoft.com...
> "Fail to work with"
> JDBC will not connect (gives the 'End of stream was detected on a read'
> error). Was working fine before SP4 (previously SP3).
|||The exact error is " java.sql.SQLException: [Microsoft][SQLServer 2000 Driver
for JDBC]End of stream was detected on a read."
On the SQL server, I get a "Connection opened but invalid login packet(s)
sent. Connection closed".
I can't run osql.exe as I'm connecting from a linux box.
|||Can someone confirm that the JDBC drivers (for sp3) can successfully connect
to SQL Server w/ SP4 *when the "force protocol encryption" option is enabled*?
|||end-user wrote:
> Can someone confirm that the JDBC drivers (for sp3) can successfully connect
> to SQL Server w/ SP4 *when the "force protocol encryption" option is enabled*?
Anyone?
|||Anyone what?
|||Alin Sinpalean wrote:
> Anyone what?
>
Can someone confirm that the JDBC drivers (for sp3) can successfully
connect to SQL Server w/ SP4 *when the "force protocol encryption"
option is enabled*?
|||"Force protocol encryption" enabled? The MS driver never did support
SSL encryption. Use jTDS ( http://jtds.sourceforge.net ) or one of the
commercial drivers for that.
Disclaimer: I'm a jTDS developer.
Alin.

No comments:

Post a Comment