Re: Unknown connect option (Get), Postgres 7.4.2] - Mailing list pgsql-odbc

From Jeff Eckermann
Subject Re: Unknown connect option (Get), Postgres 7.4.2]
Date
Msg-id 20040525150945.27927.qmail@web20802.mail.yahoo.com
Whole thread Raw
In response to Re: Unknown connect option (Get), Postgres 7.4.2]  (Albin Blaschka <Albin.Blaschka@bal.bmlfuw.gv.at>)
List pgsql-odbc
--- Albin Blaschka <Albin.Blaschka@bal.bmlfuw.gv.at>
wrote:
>
> Hello all,
>
> Thank you for your replies!
>
> but everything proposed, I have already tried and
> checked before I wrote
> to the list...

I'm not going to say that the ODBC driver could not be
the problem.  All I will say is, every case similar to
yours that I have seen, turned out to be a problem
with connecting or authenticating.

You can easily test the authentication question, just
by temporarily setting up user "albin" to use "trust"
authentication.

I don't want to assume anything based on the fact that
PgAdminIII can connect, because I don't know how it
handles that.

If all else fails, try setting up psql on your
workstation (there are instructions in the docs on how
to do that), and try connecting manually.  If you get
a failure then, you may at least get a more helpful
error message.

>
> To summarize:
> When I want to connect from Computer A as user B to
> Database C via
> PGAdminIII everything works smoothely -
> When I want to connect from Computer A as user B to
> Database C via
> Access or PGAdminII it fails... :-(
>
> So I came to the conclusion that ODBC is the first
> to suspect...
> and pg_hba.conf (which I edited by hand for the new
> setup) can't
> be the problem...
>
> But here (a little boiled down) is my pg_hba.conf:
>
> # TYPE  DATABASE       USER            IP-ADDRESS
> IP-MASK     METHOD
>   local all            postgres
>            trust
>   local all            +dba
>            md5
>   local zuecht         zuecht_odbc
>            md5
>   local gruenland      gruen_odbc
>            md5
>   local basisdaten     versuch
>            md5
>
>   host  all            postgres        127.0.0.1
> 255.255.0.0 md5
>   host  all            postgres        192.168.0.0
> 255.255.0.0 md5
>
>   host  all            albin           192.168.0.0
> 255.255.0.0 md5
>
>   host  all            +dba            192.168.0.0
> 255.255.0.0 md5
>
>
> Remark:
> user "albin" (It's me;-) is a member of the group
> dba, as you see below, I
> tried to connect in this way ...
>
>
> PostgreSQL loggs the following during I try to
> connect via Access
> (via Syslog):
>
> May 25 10:44:58 postgres[4528]: [2-1] LOG:  00000:
> Verbindung empfangen:
>
> Host=192.168.0.110 Port=1086
> May 25 10:44:58 postgres[4528]: [2-2] ORT:
> BackendFork, postmaster.c:2395
> May 25 10:44:58 postgres[4528]: [3-1] LOG:  00000:
> Verbindung authorisiert:
>
> Benutzer=albin Datenbank=zuecht
> May 25 10:44:58 postgres[4528]: [3-2] ORT:
> BackendFork, postmaster.c:2457
> May 25 10:44:58 postgres[4528]: [4-1] LOG:  00000:
> Anweisung:
> May 25 10:44:58 postgres[4528]: [4-2] ORT:
> pg_parse_query, postgres.c:464
> May 25 10:44:58 postgres[4528]: [5-1] LOG:  00000:
> Dauer: 0.297 ms
> May 25 10:44:58 postgres[4528]: [5-2] ORT:
> exec_simple_query,
> postgres.c:960
>
> I am working in Austria, so the output is partly in
> German, a short
> (rough) translation:
>
> Verbindung empfangen = connection received
> Verbindung authorisiert = connection authorized
> Benutzer = user
> Datenbank = database
>
> Thanks for all!
>
> Albin
>
> Database: PostgreSQL 7.4.2, self-compiled
> Clients:  W2K, Access from Office XP
> ODBC:     7.03.02.00
>
> Here is the output of the psqlodbc-log:
> CONN ERROR: func=PGAPI_GetConnectOption,
> desc='fOption=30002', errnum=205,
> errmsg='Unknown connect option (Get)'
>
>
------------------------------------------------------------
>             henv=136060816, conn=136066856,
> status=0, num_stmts=16
>             sock=136060872, stmts=136060944,
> lobj_type=-999
>             ---------------- Socket Info
> -------------------------------
>             socket=-1, reverse=0, errornumber=0,
> errormsg='(NULL)'
>             buffer_in=136077856,
> buffer_out=136081960
>             buffer_filled_in=0, buffer_filled_out=0,
> buffer_read_in=0
> conn=136066856, PGAPI_DriverConnect(
> in)='DSN=testing7.4.2;',
> fDriverCompletion=1
> DSN info:
>
DSN='testing7.4.2',server='balappserver',port='5432',dbase='zuecht',user='al
> bin',passwd='xxxxx'
>
>
onlyread='0',protocol='6.4',showoid='0',fakeoidindex='0',showsystable='0'
>           conn_settings='',conn_encoding='OTHER'
>           translation_dll='',translation_option=''
> Global Options: Version='07.03.0200', fetch=100,
> socket=4096,
> unknown_sizes=0,
>                 max_varchar_size=254,
> max_longvarchar_size=8190
>                 disable_optimizer=1, ksqo=1,
> unique_index=1,
> use_declarefetch=0
>                 text_as_longvarchar=1,
> unknowns_as_longvarchar=0,
> bools_as_char=1 NAMEDATALEN=64
>                 extra_systable_prefixes='pg_;',
> conn_settings=''
> conn_encoding='OTHER'
>                 conn=136066856, query=' '
> NOTICE from backend during send_query: 'LOG:
> Anweisung:
> '
> NOTICE from backend during send_query: 'LOG:  Dauer:
> 0.246 ms
> '
> CONN ERROR: func=PGAPI_DriverConnect, desc='Error
> from CC_Connect',
> errnum=105, errmsg='The database does not exist on
> the server
> or user authentication failed.'
>
>
------------------------------------------------------------
>             henv=136060816, conn=136066856,
> status=0, num_stmts=16
>             sock=136060872, stmts=136060944,
> lobj_type=-999
>             ---------------- Socket Info
> -------------------------------
>             socket=964, reverse=0, errornumber=0,
> errormsg='(NULL)'
>             buffer_in=136077856,
> buffer_out=136081960
>             buffer_filled_in=48,
> buffer_filled_out=0, buffer_read_in=48
>
> And here from the mylog-file:
>
> [1244]globals.extra_systable_prefixes = 'dd_;'
> [1244][[SQLAllocHandle]][1244]**** in PGAPI_AllocEnv
> **
> [1244]** exit PGAPI_AllocEnv: phenv = 136060816 **
> [1244][[SQLSetEnvAttr]] att=200,2
> [1244][[SQLAllocHandle]][1244]PGAPI_AllocConnect:
> entering...
> [1244]**** PGAPI_AllocConnect: henv = 136060816,
> conn = 136066856
> [1244]EN_add_connection: self = 136060816, conn =
> 136066856
> [1244]       added at i =0, conn->henv = 136060816,
> conns[i]->henv =
> 136060816
> [1244][SQLGetInfo(30)][1244]PGAPI_GetInfo:
> entering...fInfoType=77
> [1244]PGAPI_GetInfo: p='03.00', len=0, value=0,
> cbMax=12
> [1244][[SQLSetConnectAttr]] 103
> [1244]PGAPI_SetConnectAttr 103
> [1244]PGAPI_SetConnectOption: entering fOption = 103
> vParam = 20
> [1244][[SQLGetConnectAttr]] 30002
> [1244]PGAPI_GetConnectAttr 30002
> [1244]PGAPI_GetConnectOption: entering...
> [1244]CONN ERROR: func=PGAPI_GetConnectOption,
> desc='fOption=30002',
> errnum=205, errmsg='Unknown connect option (Get)'
> [1244][[SQLSetConnectAttr]] 30002
> [1244]PGAPI_SetConnectAttr 30002
> [1244]PGAPI_SetConnectOption: entering fOption =
> 30002
=== message truncated ===





__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/

pgsql-odbc by date:

Previous
From: Albin Blaschka
Date:
Subject: Re: Unknown connect option (Get), Postgres 7.4.2]
Next
From: xier@in.tum.de
Date:
Subject: PostgreSQL delete the blank in the end of the String automatically. how can I avoid it?