odbc connection error

[Ian Kreitenstein]

I am receiving the following error when attempting to connect to a database via ODBC:

“[DataDirect][ODBC SequeLink driver][SequeLink Client]Network problem, connection unexpectedly closed by peer”

This is an initial installation of ODBC. I have confirmed the host and port defined within the odbc.ini file are correct by doing a tnsping to the database to which I am trying to connect. I can also connect to the database via SQLPlus from the Quovadx server.

Any assistance would be appreciated.

Thanks in advance.

Regards,

Ian

Topic

[Ian Kreitenstein]

I have resolved this with the assitance of the Quovadx support group (thanks) and thought that I would post the resolution for the edification of those that may benefit in the future.

We had the SequeLink snap-on installed without installing the associated program on the target database server. The resolution – after deciding we did not want to install the SequeLink Server on each server hosting a database to which Quovadx was to connect – was to run the install again from the CD and select the Connect 4.2 option. Connect 4.2 does not work in the same two-tier type of architecture space as SequeLink. Therefore, we only need to run Connect 4.2 on Quovadx, define the database addresses in the tnsnames.ora, configure the odbc.ini file, and write the code to make the connection.

FYI.

Ian

[Ed Mastascusa]

Another ODBC connection issue using Connect4.2 on cloverleaf 5.3 on AIX

I have a problem when I am trying to connect to a named instance of an MS SQL database on an SQL server.  The Data Direct documentation seems to indicate that I just need to append the instance name after the server, i.e.  servernamed_instance. However, when I try to access an instance in this way SQLConnect()returns SQL_ERROR and I am getting the following error messages.

Message: [DataDirect][ODBC SQL Server Driver]ient unabl

SQLSTATE:08001

Message: [DataDirect][ODBC SQL Server Driver][libssclient19;

[Dorian DiNardo]

Ed,

The in the entry of the Address line might be your culprit. Here is an example of an entry in our odbc file that we are using.

[WebTest_Server]

Driver=/quovadx/qdx5.3/integrator/lib/Connect4.2/lib/CVmsss19.so

Address=PHCWEBT1,1433

Description=DataDirect 4.20 SQL Server Wire Protocol

AnsiNPW=Yes

Database=Surgery

LogonID=xxxxx

Password=xxxxx

QuotedId=No

Hope this helps,

Dorian

[Ed Mastascusa]

Thanks Dorian.

The -less entry does work on our system, but only when we use it to connect to the unnamed (default) instance of SQL server running on the box. The problem I am having is that I need to connect to a second instance named “test” that also runs on the box. I can’t figure out how configure the instance name in the ini file.

The best way I can explain is to constrast how query analyzer behaves.

In order to connect to the default unnamed instance using the query analyzer utility Microsoft provides, for the unnamed instance I just enter the server “myserver” as the SQL server in the “connect to SQL server” dialog. I then get a window with the title “Query – myserver.defaultdatabase.userid – Untitled” where I can enter and execute my SQL.

For the named instance “test” I can connect by using “myservertest” as the server name. In this case Query Analyzer lets me connect to the “test” instance on “myserver” using the test user ID and password. I then get a window with the title “Query – myservertest.testdefaultdatabase.testuserid – Untitled” where I can enter and execute my SQL on the test instance.

However, simply appending the instance name as “test” in the odbc.ini Address line doesn’t seem to work. I’ve also tried to express the “test” instance using “\test” and “.test” without any success.

[John Mercogliano]

Ed,

  It is my understanding that the port option is not supported with named instances.  The work around for this is to assign a different port number to the named instance then you can connection with servername, port and this will connect to the named instance because the default is listening on another port.

  Hope this helps.

John Mercogliano
Sentara Healthcare
Hampton Roads, VA

[Ed Mastascusa]

Hi John,

Thanks for the help. It looks like I’ll be trying your “one instance to one port” suggestion once I can get the database admins to buy into that.

I did talk to tech support and in Connect 4.2 named instances are not supported. The newer version 5.0 used with cloverleaf 5.4 apparently does support named instances.

[John Mercogliano]

Yes, it does support named instances but for your situation it still might not work.  It does not seem that you can use both the named instance and port number parameters and it looks like your system is set up to use different port from the default.

John Mercogliano
Sentara Healthcare
Hampton Roads, VA

[Author]

Replies