iml-sapdbi405.com
Date: Fri Feb 27 2004 - 13:04:17 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Sven,

We are runing all 7.5.0.8 on our systms and I've been seeing similar problems. what is also odd is that the 'rejected bad connect packet'
sounds aweful similar to an error I was seeing with DBMCLI / SQLCLI - and these don't even use the ODBC?

In production we have: Win2k 7.5.0.8 odbc drivers talking to a win2k 7.5.0.8 MaxDB server. Same OS, two different machines. We have a
unicode database and use the unicode driver. No such problems. the ODBC driver I put on the 'client system' I did by running MaxDB 7.5.0.8
server setup and choosing to only install the ODBC driver. In other words, I did not download the stand-alone ODBC driver - as I have found
them to be out of date in the past :)

However... I am working on my much list-referenced Sun Solaris 8 system. The Solaris system is also running 7.5.0.8 with a copy of the same
(unicode database) that I loaded from the production Win2K system. I am using a Windows XP client to do my SQL queries... I have been
encountering many unexplained connect / driver failures. Furthermore, I often find that rebooting the client (Windows XP) machine sometimes
fixes it, sometimes stop / start of the Solaris xserver helps. I haven't had time to experiment a lot with it as I'm trying to get work done and
not spend all my days testing MaxDB :)

Not sure if this information is of use. Your errors and probems sound very similar. Hard to draw conclusions, maybe the Unix xserver has a
problem that puts the Windows Unicode driver in some fouled state?

  Stephen Gutknecht

On Fri, 27 Feb 2004 03:00 , Sven Köhler <skoehlerupb.de> sent:

>Hi,
>
[snip]
>
>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)
>
>As i said it before: the error-message is not true.
>
>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".
>
[snip]

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

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]