Skip to Content
author's profile photo Former Member
Former Member

Error via ODBC: wrong dll version (check: SQLTCPx.dll)

Hi,

after system, MAXDB 7.06.03 & database studio installation on new server my application reports error: wrong dll version (check: SQLTCPx.dll)

On previous server connection via ODBC was ok.

I have checked all available ODBC Drivers (MAXDB, SAPDB, SAPDB 7.4) and it does nothing.

Connection via .net driver (without ODBC) works fine.

How can I get correct version of dll ?

Which version is correct?

This dll currently exists in system: v. 7.6.3.0 (C:\Program Files\sdb\DBM) or v. 7.6.2.0 (C:\Program Files\sdb\programs\pgm)

Best regards,

Lukasz

MAXDB 7.06.03.07 Community Edition, WIN 2k3 x32 Ent. ed.

ODBC:

Version 7.6.03 Build 007-123-157-515

Object Mode 32 bit

Test File pgm/sqlod32.dll

Make Id 256246

Installation Date 24.01.2008

Size 3045874 bytes

Checksum 293d54b1f67025353bc9cfdbe1dd84f3

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Jan 25, 2008 at 04:12 PM

    Hello Lukasz

    Apparently something went wrong. The ODBC driver (sqlod32[w].dll) depends on SQLTCPx.dll s. There is some checking that only dlls which belong to a certain release can work together.

    You can check the versions within the file explorer (context menu -> Properties -> Version).

    It could be that the path-environment points to two separate MaxDB-ODBC drivers (one from the general installation the other one of SQLStudio, which installs its own driver). Usually the SQLStudio driver is registered under SQLSTUDIOODBC.

    BTW, which .NET driver do you mean?

    With kind regards Thomas

    Add a comment
    10|10000 characters needed characters exceeded

    • Hello Lukasz

      We were able to reproduce your problem. Actually there is an inconsistency in the installation of Database Studio, if already a 7.6 package was installed. Of course, this will be fixed in the future and will be available with the next version of Database Studio.

      As a workaround for you, you can either use the ODBC-driver of SQLStudio, which is registered under the driver name SQLSTUDIOODBC, or you register this driver under a new name.

      In my environment, the call would be:

      odbcreg -i <name> -p "C:\Program Files\SDB\SQLStudio" -d sqlod32w.dll

      Please check the location of the SQLStudio ODBC-driver and adjust the above statement, if necessary. Please make sure, that you use quotes, if your path contains space characters.

      Sorry for the inconvenience

      Thomas

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.