OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: [BUG] Unicode ODBC Driver is broken

From: Sven Köhler (skoehlerupb.de)
Date: Fri Feb 27 2004 - 06:05:51 CST


>>i can connect to a running SAPDB 7.4 instance, but i
>>__cannot__ connect
>>to MaxDB 7.5. Today i had the idea to try the normal Driver
>>instead of
>>the Unicode-version, and well - i can connect and MS Access lists all
>>the tables.
>>
>>With the Unicode-version of the SAPDB-Driver i get the
>>following error:
>>[SAP AG][SQLOD32 DLL][SAP DB]Unabale to connect to data source; -709
>>CONNECT: (connection refused).(#-709)

> Can you tell me all relevant info about DB and driver and
> which UID/PWD combination failed?
>
> I.e. versions, unicode etc.

It happens with any UID/PWD combination and i'm using sqlod32w.dll - the
unicode-version of the ODBC-driver.
The server is running MaxDB 7.5.0.8 and the ODBC-driver is version
7.5.0.10. I can connect to any SAPDB 7.4 with the same driver - even
with the same ODBC-DSN.

I try to connect to a database with _UNICODE=yes and
DEFAULT_CODE=UNICODE. Both SAPDB 7.4 and the MaxDB 7.5.0.8 are running
under Linux.

>>I'm using ettercap and can see, that the ODBC-driver connects
>>twice to
>>the Server and for the second try, the response by the MaxDB
>>server is
>>"Rejected bad connect packet".
>
> This shouldn't happen.

That's true, but it may be, that's not even your fault, but some weird
behaviour of MaxDB 7.5.0.8 - so what further information do you need?

The ODBC-trace deesn't contain much information. I can see that the
Application tries to connect, and the error-message i mentioned above is
listed. Nothing more.

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb