Skip site navigation (1) Skip section navigation (2)

Re: Problem with NT 4.0 / driver 08.01.0102

From: "Philippe Lang" <philippe(dot)lang(at)attiksystem(dot)ch>
To: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Problem with NT 4.0 / driver 08.01.0102
Date: 2006-01-23 15:34:44
Message-ID: 6C0CF58A187DA5479245E0830AF84F42143A9E@poweredge.attiksystem.ch (view raw or flat)
Thread:
Lists: pgsql-odbc
I guess the problem comes from libpq, because on this exact same computer, a
simple switch from psqlodbc 7.030.208 to 08.01.0102 and the problem arises.
172.17.0.4 is accessible and used by many people, no problem on the server
side.

Is libpq maybe incompatible with Windows NT 4.0? Or may a bug with name
resolution under NT 4.0?

Here is the mylog output:


[158]Could not establish connection to the database; LIBPQ returned -> could
not translate host name "172.17.0.4" to address: Unknown host
 
[158]CONN ERROR: func=PGAPI_DriverConnect, desc='Error from CC_Connect',
errnum=113, errmsg='could not translate host name "172.17.0.4" to address:
Unknown host
'
[158][[SQLGetDiagRec]]
[158]PGAPI_GetDiagRec entering rec=1[158]**** PGAPI_ConnectError:
hdbc=151350640 <0>
[158]enter CC_get_error
[158]enter CC_create_errormsg
[158]msg = 'could not translate host name "172.17.0.4" to address: Unknown
host
'
[158]exit CC_create_errormsg
[158]exit CC_get_error
[158]CC_get_error: status = 113, msg = #could not translate host name
"172.17.0.4" to address: Unknown host
#
[158]	     szSqlState = 'S1000',len=68, szError='(null)'
[158]PGAPI_GetDiagRec exiting 1
[158][[SQLGetDiagRec]]
[158]PGAPI_GetDiagRec entering rec=1[158]**** PGAPI_ConnectError:
hdbc=151350640 <70>
[158]enter CC_get_error
[158]exit CC_get_error
[158]CC_get_error: status = 113, msg = #could not translate host name
"172.17.0.4" to address: Unknown host
#
[158]	     szSqlState = 'S1000',len=68, szError='could not translate host
name "172.17.0.4" to address: Unknown host
'
[158]PGAPI_GetDiagRec exiting 0
[158][[SQLGetDiagField]] Handle=(2,9056d70) Rec=1 Id=8
[158]PGAPI_GetDiagField entering rec=1[158]PGAPI_GetDiagField exiting 0
[158][[SQLGetDiagField]] Handle=(2,9056d70) Rec=1 Id=9
[158]PGAPI_GetDiagField entering rec=1[158]PGAPI_GetDiagField exiting 0
[158][[SQLGetDiagField]] Handle=(2,9056d70) Rec=1 Id=10
[158]PGAPI_GetDiagField entering rec=1[158]PGAPI_GetDiagField exiting 0
[158][[SQLGetDiagField]] Handle=(2,9056d70) Rec=1 Id=11
[158]PGAPI_GetDiagField entering rec=1[158]PGAPI_GetDiagField exiting 0
[158][[SQLGetDiagRec]]
[158]PGAPI_GetDiagRec entering rec=2[158]**** PGAPI_ConnectError:
hdbc=151350640 <0>
[158]PGAPI_GetDiagRec exiting 100
[158][[SQLFreeHandle]][158]PGAPI_FreeConnect: entering...
[158]**** in PGAPI_FreeConnect: hdbc=151350640
[158]enter CC_Destructor, self=151350640
[158]in CC_Cleanup, self=151350640
[158]after LIBPQ destructor
[158]exit CC_Cleanup
[158]after CC_Cleanup
[158]after free statement holders
[158]exit CC_Destructor
[158]PGAPI_FreeConnect: returning...
[158][[SQLFreeHandle]][158]**** in PGAPI_FreeEnv: env = 169348848 ** 
[158]in EN_Destructor, self=169348848
[158]exit EN_Destructor: rv = 1
[158]   ok 

-----Message d'origine-----
De : Ludek Finstrle [mailto:luf(at)pzkagis(dot)cz] 
Envoyé : lundi, 23. janvier 2006 14:47
À : Philippe Lang
Cc : pgsql-odbc(at)postgresql(dot)org
Objet : Re: [ODBC] Problem with NT 4.0 / driver 08.01.0102

> CONN ERROR: func=PGAPI_GetConnectOption, desc='fOption=30002', 
> errnum=205, errmsg='Unknown connect option (Get)'

I think the real problem is described later.

> CONN ERROR: func=PGAPI_DriverConnect, desc='Error from CC_Connect', 
> errnum=113, errmsg='could not translate host name "172.17.0.4" to address:
> Unknown host '

I don't know why but it can't get IP address. It means that 172.17.0.4 is
name not IP. Could you check DNS server or lmhosts file?
Do you have correct route table on the host? Could you ping/reach
172.17.0.4 host?

> No problem of this type arise with both Windows 2000 and XP.
> And the old 7.030.208 version does not have this problem. It runs fine 
> under NT.

It run in same situation (same host, same app, ...)? The newer driver is
using libpq to connect to server. So it could be the problem. I have no
WinNT 4.0 box here.

BTW maybe mylog output could be mo0re helpful.

Regards,

Luf

Responses

pgsql-odbc by date

Next:From: Ludek FinstrleDate: 2006-01-23 16:14:54
Subject: Re: Problem with NT 4.0 / driver 08.01.0102
Previous:From: Ludek FinstrleDate: 2006-01-23 13:46:53
Subject: Re: Problem with NT 4.0 / driver 08.01.0102

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group