pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive help / color / mirror / Atom feed From: Ken J. Wright <ken@cncware.com>
To: pgsql-interfaces@postgresql.org
Subject: ODBC authentication failure
Date: Sun, 14 Feb 1999 11:04:56 -0800
Message-ID: <3.0.32.19990214110455.008099f0@ren.cncware.com> (raw )
Hello Byron,
Attached is the tracelog from an attempted ODBC connect.
This occurs whenever authentication fails during an attempt to connect
(using ODBCExpress). I believe I should get a connection dialog, but it
fails instead. I have tried different hdbc prompt settings & also different
pg_hba.conf settings, but basically the same thing happens whenever
authentication fails for any reason. The trace indicates that this is
another ODBC2.0 vs. ODBC3.0 issue. Would you agree? And more importantly,
how do I, you, we fix it? I can certainly (and do currently) just trap the
error and deal with it through my own dialog box, but I was hoping to also
be able to rely on the fallback of the driver handling the prompting.
Comments?
Cheers!
Ken
Attachments:
sql.log (text/plain, 5.0K) download
gl ffc013a5:ffc0e0bd ENTER SQLAllocHandle
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x0121fc5c
SQLHANDLE * 0x0164164c
gl ffc013a5:ffc0e0bd EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2 <SQL_HANDLE_DBC>
SQLHANDLE 0x0121fc5c
SQLHANDLE * 0x0164164c ( 0x0121ff10)
gl ffc013a5:ffc0e0bd ENTER SQLGetConnectAttr
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x006eedd4
SQLINTEGER 4
SQLINTEGER * 0x00000000
gl ffc013a5:ffc0e0bd EXIT SQLGetConnectAttr with return code 0 (SQL_SUCCESS)
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x006eedd4
SQLINTEGER 4
SQLINTEGER * 0x00000000
gl ffc013a5:ffc0e0bd ENTER SQLSetConnectAttr
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x00000000
SQLINTEGER 4
gl ffc013a5:ffc0e0bd EXIT SQLSetConnectAttr with return code 0 (SQL_SUCCESS)
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x00000000
SQLINTEGER 4
gl ffc013a5:ffc0e0bd ENTER SQLGetConnectAttr
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x006eede0
SQLINTEGER 4
SQLINTEGER * 0x00000000
gl ffc013a5:ffc0e0bd EXIT SQLGetConnectAttr with return code 0 (SQL_SUCCESS)
SQLHDBC 0x0121ff10
SQLINTEGER 110 <SQL_ATTR_ODBC_CURSORS>
SQLPOINTER 0x006eede0
SQLINTEGER 4
SQLINTEGER * 0x00000000
gl ffc013a5:ffc0e0bd ENTER SQLDriverConnectW
HDBC 0x0121ff10
HWND 0x00000b70
WCHAR * 0x6a9ae068 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x6a9ae068
SWORD 8
SWORD * 0x00000000
UWORD 3 <SQL_DRIVER_COMPLETE_REQUIRED>
gl ffc013a5:ffc0e0bd EXIT SQLDriverConnectW with return code -1 (SQL_ERROR)
HDBC 0x0121ff10
HWND 0x00000b70
WCHAR * 0x6a9ae068 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x6a9ae068
SWORD 8
SWORD * 0x00000000
UWORD 3 <SQL_DRIVER_COMPLETE_REQUIRED>
DIAG [28000] User authentication failed (210)
DIAG [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr). (0)
gl ffc013a5:ffc0e0bd ENTER SQLGetDiagRecW
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 1
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6
gl ffc013a5:ffc0e0bd EXIT SQLGetDiagRecW with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 1
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8 (210)
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6 (26)
gl ffc013a5:ffc0e0bd ENTER SQLGetDiagRecW
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 2
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6
gl ffc013a5:ffc0e0bd EXIT SQLGetDiagRecW with return code 0 (SQL_SUCCESS)
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 2
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8 (0)
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6 (140)
gl ffc013a5:ffc0e0bd ENTER SQLGetDiagRecW
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 3
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6
gl ffc013a5:ffc0e0bd EXIT SQLGetDiagRecW with return code 100 (SQL_NO_DATA_FOUND)
SQLSMALLINT 2
SQLHANDLE 0x0121ff10
SQLSMALLINT 3
SQLWCHAR * 0x006eeb70 (NYI)
SQLINTEGER * 0x006eedc8
SQLWCHAR * 0x011203a0 (NYI)
SQLSMALLINT 256
SQLSMALLINT * 0x006eedc6
view thread (4+ messages) latest in thread
Message-ID: <3.0.32.19990214110455.008099f0@ren.cncware.com>
Permalink: ../3.0.32.19990214110455.008099f0@ren.cncware.com/
Also on: postgresql.org/message-id/3.0.32.19990214110455.008099f0@ren.cncware.com
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: ken@cncware.com
Subject: Re: ODBC authentication failure
In-Reply-To: <3.0.32.19990214110455.008099f0@ren.cncware.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox