MySQL Bugs: #2504: MySQL Error while trying to connect via MyODBC using password

Bug #2504	MySQL Error while trying to connect via MyODBC using password
Submitted:	25 Jan 2004 3:32	Modified:	25 Jan 2004 8:56
Reporter:	Yuriy Dzhenyeyev	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	3.51.06	OS:	Windows (Windows 2000)
Assigned to:		CPU Architecture:	Any

Description:
While trying connect from the MyQDBC DSN-Configuration or from VB.NET (as describet in http://www.mysql.com/products/myodbc/manual.html#ODBC.NET(VB)) to MySQL 4.1.0 alpha-max-nt as 'localhost':

- log in as 'root' without password: successful
- login as any existing user with specified password using any string as password: 
    1. error message from mysqld-nt.exe: 'Die Anweisung in "0x0058521f" verweist auf Speicher in "0x00000001". Der Vorgang "read" konnte nicht auf dem Speicher durchgefuehrt werden.'
    2. error message from MyODBC-Driver: '[MySQL][MyODBC Driver] Lost connection to MySQL server during query.'

the following log-file was created by the ODBC-Tracing:

testapp         794-7a8	ENTER SQLSetEnvAttr 
		SQLHENV             00000000
		SQLINTEGER                 201 <unknown>
		SQLPOINTER          [Unknown attribute 201]
		SQLINTEGER                  -6 

testapp         794-7a8	EXIT  SQLSetEnvAttr  with return code 0 (SQL_SUCCESS)
		SQLHENV             00000000
		SQLINTEGER                 201 <unknown>
		SQLPOINTER          [Unknown attribute 201]
		SQLINTEGER                  -6 

testapp         794-7a8	ENTER SQLAllocHandleStd 
		SQLSMALLINT                  1 
		SQLHANDLE           00000000
		SQLHANDLE *         0012F4B4

testapp         794-7a8	EXIT  SQLAllocHandleStd  with return code 0 (SQL_SUCCESS)
		SQLSMALLINT                  1 
		SQLHANDLE           00000000
		SQLHANDLE *         0x0012F4B4 ( 0x04381540)

testapp         794-7a8	ENTER SQLAllocHandleStd 
		SQLSMALLINT                  2 
		SQLHANDLE           04381540
		SQLHANDLE *         00D96828

testapp         794-7a8	EXIT  SQLAllocHandleStd  with return code 0 (SQL_SUCCESS)
		SQLSMALLINT                  2 
		SQLHANDLE           04381540
		SQLHANDLE *         0x00D96828 ( 0x043815e8)

testapp         794-7a8	ENTER SQLSetConnectAttrW 
		SQLHDBC             043815E8
		SQLINTEGER                 103 <SQL_ATTR_LOGIN_TIMEOUT>
		SQLPOINTER          0x0000000F
		SQLINTEGER                  -5 

testapp         794-7a8	EXIT  SQLSetConnectAttrW  with return code 0 (SQL_SUCCESS)
		SQLHDBC             043815E8
		SQLINTEGER                 103 <SQL_ATTR_LOGIN_TIMEOUT>
		SQLPOINTER          0x0000000F (BADMEM)
		SQLINTEGER                  -5 

testapp         794-7a8	ENTER SQLDriverConnectW 
		HDBC                043815E8
		HWND                00000000
		WCHAR *             0x0434592C [      -3] "******\ 0"
		SWORD                       -3 
		WCHAR *             0x0434592C 
		SWORD                        8 
		SWORD *             0x00000000
		UWORD                        0 <SQL_DRIVER_NOPROMPT>

testapp         794-7a8	EXIT  SQLDriverConnectW  with return code -1 (SQL_ERROR)
		HDBC                043815E8
		HWND                00000000
		WCHAR *             0x0434592C [      -3] "******\ 0"
		SWORD                       -3 
		WCHAR *             0x0434592C 
		SWORD                        8 
		SWORD *             0x00000000
		UWORD                        0 <SQL_DRIVER_NOPROMPT>

		DIAG [HY000] [MySQL][ODBC 3.51 Driver]Lost connection to MySQL server during query (2013) 

		DIAG [HY000] [MySQL][ODBC 3.51 Driver]Lost connection to MySQL server during query (2013) 

testapp         794-7a8	ENTER SQLGetDiagRecW 
		SQLSMALLINT                  2 
		SQLHANDLE           043815E8
		SQLSMALLINT                  1 
		SQLWCHAR *          0x0018CA20 (NYI) 
 		SQLINTEGER *        0x0012F4A0
		SQLWCHAR *          0x0018B5C0 (NYI) 
 		SQLSMALLINT                512 
		SQLSMALLINT *       0x0012F498

testapp         794-7a8	EXIT  SQLGetDiagRecW  with return code 0 (SQL_SUCCESS)
		SQLSMALLINT                  2 
		SQLHANDLE           043815E8
		SQLSMALLINT                  1 
		SQLWCHAR *          0x0018CA20 (NYI) 
 		SQLINTEGER *        0x0012F4A0 (2013)
		SQLWCHAR *          0x0018B5C0 (NYI) 
 		SQLSMALLINT                512 
		SQLSMALLINT *       0x0012F498 (69)

testapp         794-7a8	ENTER SQLGetDiagRecW 
		SQLSMALLINT                  2 
		SQLHANDLE           043815E8
		SQLSMALLINT                  2 
		SQLWCHAR *          0x0018CA20 (NYI) 
 		SQLINTEGER *        0x0012F4A0
		SQLWCHAR *          0x0018B5C0 (NYI) 
 		SQLSMALLINT                512 
		SQLSMALLINT *       0x0012F498

testapp         794-7a8	EXIT  SQLGetDiagRecW  with return code 0 (SQL_SUCCESS)
		SQLSMALLINT                  2 
		SQLHANDLE           043815E8
		SQLSMALLINT                  2 
		SQLWCHAR *          0x0018CA20 (NYI) 
 		SQLINTEGER *        0x0012F4A0 (2013)
		SQLWCHAR *          0x0018B5C0 (NYI) 
 		SQLSMALLINT                512 
		SQLSMALLINT *       0x0012F498 (69)

testapp         794-7a8	ENTER SQLGetDiagRecW 
		SQLSMALLINT                  2 
		SQLHANDLE           043815E8
		SQLSMALLINT                  3 
		SQLWCHAR *          0x0018CA20 (NYI) 
 		SQLINTEGER *        0x0012F4A0
		SQLWCHAR *          0x0018B5C0 (NYI) 
 		SQLSMALLINT                512 
		SQLSMALLINT *       0x0012F498

testapp         794-7a8	EXIT  SQLGetDiagRecW  with return code 100 (SQL_NO_DATA_FOUND)
		SQLSMALLINT                  2 
		SQLHANDLE           043815E8
		SQLSMALLINT                  3 
		SQLWCHAR *          0x0018CA20 (NYI) 
 		SQLINTEGER *        0x0012F4A0
		SQLWCHAR *          0x0018B5C0 (NYI) 
 		SQLSMALLINT                512 
		SQLSMALLINT *       0x0012F498

testapp         794-7a8	ENTER SQLFreeHandle 
		SQLSMALLINT                  2 <SQL_HANDLE_DBC>
		SQLHANDLE           043815E8

testapp         794-7a8	EXIT  SQLFreeHandle  with return code 0 (SQL_SUCCESS)
		SQLSMALLINT                  2 <SQL_HANDLE_DBC>
		SQLHANDLE           043815E8

How to repeat:
Have not had any successful connection with user + password untill now

Thank you for taking the time to report a problem.  Unfortunately
you are not using a current version of the product your reported a
problem with -- the problem might already be fixed. Please download
a new version from http://www.mysql.com/downloads/

If you are able to reproduce the bug with one of the latest versions,
please change the version on this bug report to the version you
tested and change the status back to "Open".  Again, thank you for
your continued support of MySQL.

Additional info:

You have to use Myodbc-3.52 to connect to MySQL-4.1.x