Ingres 2.6 Error

[lazyboy]

Hi Guys,

I'm having this error

Communications error while establishing connection. No such host is known SocketException thrown by System.Net.Dns.GetHostByName("<Server/VNode>") in resolving the hostname

when I connect an application developed on C#.Net with Ingres 2.6 database running on top of Tru64 Unix.

But using the exact same codes, when I connect with Ingres 2.6 database on Windows it's working just fine.

Will gladly appreciate all the help I could get.
TIA.

[jackhigh]

Perhaps the Windows box is known to the DNS but the UNIX box is not.
You could try putting the UNIX box in the local hosts file.

[Bodo]

How are you connecting from .NET to the Ingres DBMS?
I assume you are not using the .NET DataProvider as this would require a DataAccessServer, which is not available in Ingres2.6.

[thoda04]

Hi Chris,

Bodo is correct. A Data Access Server (DAS) is needed for the Ingres .NET Data Provider to connect to. However, you can get the data provider to connect to the Ingres 2.6 by setting up an intermediate installation (let's call it myserver) of maybe Ingres 9.2 that has a vnode definition (let's call it myvnode) that points to the Ingres 2.6 installation. The .NET data provider connection string would look something like "server=myserver;database=myvnode::my26databas e;". The vnode redirection should get you to 2.6 database. More details and vnode_usage options are in the Ingres Connectivity Guide.

Hope this helps,
Dave

[lazyboy]

Thanks Jack and Bodo.

@Dave,
Here is the code for my connection:

string strConnection = "Host=<Server/VNode>;database=<Database>;User ID=<UserID>;Password=<Password>;";

So you are saying I will just revise it to

"Server=myserver;database=mynode::database;Use r ID=UID;Password=PWD;";

But just thinking about it, will the use of DSN could help by just using

"DSN=dsnname;UID=Username;PWD=Password;";

Thanks a lot guys, at least I know that it is possible to connect..whew!!

[denjo02]

Incidentally, the may be working on Windows but not on Unix because the default Port in a connection is II7, which also matches the default installation code and listen address for a Windows DAS Server. If the target DAS Server is in an installation with a different two-character code, you will need to specify the Port=xxx parameter in the connection string.

[thoda04]

Hi Chris,

Your DSN connection string would only work if you are using the MS Data Provider for ODBC (ODBC.NET). A DSN is an ODBC definition. The connection string that I referred to was for the Ingres .NET Data Provider for native .NET data provider access to Ingres.

Dave

[Bodo]

If you are using ODBC for connecting from your .NET application to your server you can create a DSN and test the connection using the "Test" button in the "Ingres ODBC Administrator" (opened from the "ODBC Data Source Administrator" when editing an Ingres DSN).

[lazyboy]

Originally Posted by Bodo

If you are using ODBC for connecting from your .NET application to your server you can create a DSN and test the connection using the "Test" button in the "Ingres ODBC Administrator" (opened from the "ODBC Data Source Administrator" when editing an Ingres DSN).

Yep, if I'm gonna use the ODBC by creating and ODBC.. I can connect to Ingres 2.6.
But if I'm going to use the .Net DataProvider.. same error guys.

I think bodo is right.. no DataAccessServer on Ingres 2.6.

But hey, I'm not losing hope here.. any more takers

TIA

[Bodo]

You can setup a DAS (Ingres 9.x) on your or another Windows machine which then connects via Ingres/Net to your Ingres2.6 installation (on Tru64).
That's what Dave (thoda04) mentioned in his post where he wrote about using an intermediate installation.
This way your .Net app uses the .NET Data Provider to connect to the DAS which connects to the Ingres2.6 DBMS.