Received: from cncware.whidbey.com (IDENT:root@cncware.whidbey.com [208.25.171.37]) by hub.org (8.9.2/8.9.1) with ESMTP id OAA06723 for ; Sun, 14 Feb 1999 14:54:47 -0500 (EST) (envelope-from ken@ori-ind.com) Received: from ken (ken.cncware.com [192.168.61.201]) by cncware.whidbey.com (8.8.7/8.8.7) with SMTP id LAA06497 for ; Sun, 14 Feb 1999 11:54:06 -0800 Message-Id: <3.0.32.19990214115631.008732b0@ren.cncware.com> X-Sender: ken_ori@ren.cncware.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 14 Feb 1999 11:56:32 -0800 To: pgsql-interfaces@postgreSQL.org From: "Ken J. Wright" Subject: ODBC authentication failure Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_919050992==_" --=====================_919050992==_ Content-Type: text/plain; charset="us-ascii" 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 --=====================_919050992==_ Content-Type: text/plain; charset="us-ascii" Content-Disposition: attachment; filename="sql.log" gl ffc013a5:ffc0e0bd ENTER SQLAllocHandle SQLSMALLINT 2 SQLHANDLE 0x0121fc5c SQLHANDLE * 0x0164164c gl ffc013a5:ffc0e0bd EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS) SQLSMALLINT 2 SQLHANDLE 0x0121fc5c SQLHANDLE * 0x0164164c ( 0x0121ff10) gl ffc013a5:ffc0e0bd ENTER SQLGetConnectAttr SQLHDBC 0x0121ff10 SQLINTEGER 110 SQLPOINTER 0x006eedd4 SQLINTEGER 4 SQLINTEGER * 0x00000000 gl ffc013a5:ffc0e0bd EXIT SQLGetConnectAttr with return code 0 (SQL_SUCCESS) SQLHDBC 0x0121ff10 SQLINTEGER 110 SQLPOINTER 0x006eedd4 SQLINTEGER 4 SQLINTEGER * 0x00000000 gl ffc013a5:ffc0e0bd ENTER SQLSetConnectAttr SQLHDBC 0x0121ff10 SQLINTEGER 110 SQLPOINTER 0x00000000 SQLINTEGER 4 gl ffc013a5:ffc0e0bd EXIT SQLSetConnectAttr with return code 0 (SQL_SUCCESS) SQLHDBC 0x0121ff10 SQLINTEGER 110 SQLPOINTER 0x00000000 SQLINTEGER 4 gl ffc013a5:ffc0e0bd ENTER SQLGetConnectAttr SQLHDBC 0x0121ff10 SQLINTEGER 110 SQLPOINTER 0x006eede0 SQLINTEGER 4 SQLINTEGER * 0x00000000 gl ffc013a5:ffc0e0bd EXIT SQLGetConnectAttr with return code 0 (SQL_SUCCESS) SQLHDBC 0x0121ff10 SQLINTEGER 110 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 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 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 --=====================_919050992==_ Content-Type: text/plain; charset="us-ascii" --=====================_919050992==_--