<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>MySQL Forums - Connector/ODBC</title>
        <description>Forum for Connector/ODBC</description>
        <link>https://forums.mysql.com/list.php?37</link>
        <lastBuildDate>Sun, 15 Mar 2026 07:25:39 +0000</lastBuildDate>
        <generator>Phorum 5.2.23</generator>
        <item>
            <guid>https://forums.mysql.com/read.php?37,741462,741462#msg-741462</guid>
            <title>Stored procedure create through odbc driver (2 replies)</title>
            <link>https://forums.mysql.com/read.php?37,741462,741462#msg-741462</link>
            <description><![CDATA[ How to create a stored procedure via odbc. Can odbc use set delimiter?]]></description>
            <dc:creator>Robert Gilland</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Wed, 10 Dec 2025 16:34:58 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,741320,741320#msg-741320</guid>
            <title>No rows is inserted in the table (no replies)</title>
            <link>https://forums.mysql.com/read.php?37,741320,741320#msg-741320</link>
            <description><![CDATA[ Hi, ALL,<br />
Apologies if this subforum is a wrong place to ask about this.<br />
<br />
My application that I&#039;m working on uses mySQL. As of this moment I&#039;m using version 8.0.<br />
<br />
I&#039;m also using 8.0 ODBC driver.<br />
<br />
I&#039;m working with Gentoo Linux and unixODBC.<br />
<br />
Below is my (simplified) code:<br />
<br />
<pre class="bbcode">
                std::wstring qry2 = L&quot;INSERT IGNORE INTO abcattbl VALUES( ?, ?, (SELECT CASE WHEN t.engine = &#039;InnoDB&#039; THEN (SELECT st.table_id FROM information_schema.INNODB_TABLES st WHERE name = CONCAT(?,&#039;/&#039;, ?) ) ELSE (SELECT 0) END AS id FROM information_schema.tables t WHERE t.table_name = ? AND t.table_schema = ?), \&#039;\&#039;, 8, 400, \&#039;N\&#039;, \&#039;N\&#039;, 0, 34, 0, \&#039;Serif\&#039;, 8, 400, \&#039;N\&#039;, \&#039;N\&#039;, 0, 34, 0, \&#039;Serif\&#039;, 8, 400, \&#039;N\&#039;, \&#039;N\&#039;, 0, 34, 0, \&#039;Serif\&#039;, \&#039;\&#039; );&quot;;

    SQLWCHAR *qry = new SQLWCHAR[qry2.length() + 2];
    memset( qry, &#039;\0&#039;, qry2.length() + 2 );
    uc_to_str_cpy( qry, qry2 );

    auto qry1 = new SQLWCHAR[30];
    memset( qry1, &#039;\0&#039;, 30 );
    uc_to_str_cpy( qry1, L&quot;BEGIN&quot; );
    ret = SQLExecDirect( m_hstmt, qry1, SQL_NTS );
    delete[] qry1;
    qry1 = nullptr;
    ret = SQLPrepare( m_hstmt, qry, SQL_NTS );
    ret = SQLBindParameter( m_hstmt, 1, SQL_PARAM_INPUT, SQL_C_TINYINT, SQL_TINYINT, 0, 0, &amp;osid, 0, &amp;cbParam[2] );
    for( auto it = pimpl.m_tableDefinitions[cat].begin(); it &lt; pimpl.m_tableDefinitions[cat].end(); ++it )
    {
        schemaName = new SQLWCHAR[(*it).schemaName.length() + 2];
        tableName = new SQLWCHAR[(*it).tableName.length() + 2];
        memset( schemaName, &#039;\0&#039;, (*it).schemaName.length() + 2 );
        memset( tableName, &#039;\0&#039;, (*it).tableName.length() + 2 );
        uc_to_str_cpy( schemaName, (*it).schemaName );
        uc_to_str_cpy( tableName, (*it).tableName );
        ret = SQLBindParameter( m_hstmt, 2, SQL_PARAM_INPUT, SQL_C_WCHAR, SQL_WCHAR, (*it).tableName.length(), 0, tableName, 0, &amp;cbParam[1] );
        ret = SQLBindParameter( m_hstmt, 3, SQL_PARAM_INPUT, SQL_C_WCHAR, SQL_WCHAR, (*it).schemaName.length(), 0, schemaName, 0, &amp;cbParam[2] );
        ret = SQLBindParameter( m_hstmt, 4, SQL_PARAM_INPUT, SQL_C_WCHAR, SQL_WCHAR, (*it).tableName.length(), 0, tableName, 0, &amp;cbParam[3] );
        ret = SQLBindParameter( m_hstmt, 5, SQL_PARAM_INPUT, SQL_C_WCHAR, SQL_WCHAR, (*it).tableName.length(), 0, tableName, 0, &amp;cbParam[3] );
        ret = SQLBindParameter( m_hstmt, 6, SQL_PARAM_INPUT, SQL_C_WCHAR, SQL_WCHAR, (*it).schemaName.length(), 0, schemaName, 0, &amp;cbParam[2] );
        ret = SQLExecute( m_hstmt );
        delete[] schemaName;
        delete[] tableName;
        schemaName = nullptr;
        tableName = nullptr;
    }
    ret = SQLEndTran( SQL_HANDLE_DBC, m_hdbc, SQL_COMMIT );</pre>
<br />
Table structure is as follows:<br />
<br />
<pre class="bbcode">
CREATE TABLE IF NOT EXISTS abcattbl(abt_os tinyint, abt_tnam char(129) NOT NULL, abt_tid integer, abt_ownr char(129) NOT NULL, abd_fhgt smallint, abd_fwgt smallint, abd_fitl char(1), abd_funl integer, abd_fstr integer, abd_fchr smallint, abd_fptc smallint, abd_ffce char(18), abh_fhgt smallint, abh_fwgt smallint, abh_fitl char(1), abh_funl integer, abh_fstr integer, abh_fchr smallint, abh_fptc smallint, abh_ffce char(18), abl_fhgt smallint, abl_fwgt smallint, abl_fitl char(1), abl_funl integer, abl_fstr integer, abl_fchr smallint, abl_fptc smallint, abl_ffce char(18), abt_cmnt char(254), PRIMARY KEY( abt_tnam, abt_ownr ));
CREATE UNIQUE INDEX abcatt_x ON abcattbl(abt_os ASC, abt_tnam ASC, abt_ownr ASC)\&quot;));</pre>
<br />
The problem is that after executing all those SQLBindParameter() and SQLExecute() the table contains only 1 row.<br />
<br />
I turned on server logging and for some reason only the first parameter is properly bound. No table/schema parameter is bound as appropriate.<br />
<br />
One other thing:<br />
<br />
With the ODBC driver it seems I can&#039;t retrieve any of the INFORMATION_SCHEMA table or system tables of mySQL. Calling SQLTables() retrieves only my own tables.<br />
Is this how the driver operates? In odbc.ini I do have a database name defied.<br />
<br />
Thank you for any pointers.<br />
<br />
<pre class="bbcode">
void ODBCDatabase::uc_to_str_cpy(SQLWCHAR *dest, const std::wstring &amp;src)
{
    const wchar_t *temp = src.c_str();
    while( *dest )
    {
        dest++;
    }
    while( *temp )
    {
        *dest = *temp;
        dest++;
        temp++;
    }
    *dest++ = &#039;\0&#039;;
    *dest = &#039;\0&#039;;
}

</pre>]]></description>
            <dc:creator>Igor Korot</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Sun, 26 Oct 2025 01:58:09 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,741305,741305#msg-741305</guid>
            <title>Uninstall Mac MYSQL ODBC driver (no replies)</title>
            <link>https://forums.mysql.com/read.php?37,741305,741305#msg-741305</link>
            <description><![CDATA[ Working with InfoTopics, trying to use their WriteBack Extreme product, and I installed the mac version of MYSQL ODBC driver v. 9.4. as it required an MySQL ODBC driver.<br />
<br />
Their product wasn&#039;t working with that, so they said to uninstall v9.4 and install v.8.0.33 of the MYSQL driver.<br />
<br />
I searched the site and there is no info on uninstalling for Mac users. No instructions and a google search turns up confusing info.<br />
<br />
How would I go about accomplishing this?]]></description>
            <dc:creator>Terry Jackson</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Thu, 16 Oct 2025 16:48:59 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,741132,741132#msg-741132</guid>
            <title>ODBC 9.4.0 - Linked tables in MS Access (no replies)</title>
            <link>https://forums.mysql.com/read.php?37,741132,741132#msg-741132</link>
            <description><![CDATA[ Hi. I suspect the answer to this is &quot;It&#039;s an access issue&quot; but someone might have a magic bullet.<br />
<br />
I have the MySQL 9.4.0 64bit ODBC connecter running looking at Wordpress tables some of which I want to be available in an MS access application.<br />
<br />
Using this connector I can successfully import tables and all the data is present and correct. However I cannot link to tables. When I try this the connecter creates the link but every field in the table is filled with &quot;#Deleted&quot;<br />
<br />
I need to tables to be linked rather than imported. Does anyone know of a work around for this issue?<br />
<br />
Thank you.]]></description>
            <dc:creator>Steve Lee</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Wed, 27 Aug 2025 11:20:51 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,741063,741063#msg-741063</guid>
            <title>MySQL ODBC connector forgets password and server name (9 replies)</title>
            <link>https://forums.mysql.com/read.php?37,741063,741063#msg-741063</link>
            <description><![CDATA[ Starting with V.8, in some environments the ODBC Connector allways appears to forget it&#039;s parameters for Sytem DSNs, despite these are written into HKLM\Software\ODBC correctly. <br />
<br />
The server name and the password are written into the data source key after having defined them. The data source works fine then.<br />
<br />
With certain installations recalling the data source by ODBCAD32 does not present those two values, which had been defined previously, despite the key still holds these. When trying to test the connection by the GUI right after opening the data source it fails, unless the server name and passwort got redefined inside the UI.<br />
<br />
This only happens with certain environments. <br />
What might be wrong with these?<br />
<br />
I recently also was confused, the data source cannot be configured to &quot;enable auto reconnect&quot; or use a disinct charset any more. But that was clearly announced. <br />
It&#039;s confusing though, the GUI still offers those options even with the newest connectors, but does not use them any more and removes those registry values accordingy when saving.]]></description>
            <dc:creator>Horst Wieland</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Wed, 20 Aug 2025 08:19:08 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,740584,740584#msg-740584</guid>
            <title>CVE-2024-13176 (2 replies)</title>
            <link>https://forums.mysql.com/read.php?37,740584,740584#msg-740584</link>
            <description><![CDATA[ The CPU APR 2025 release identifies (&quot;CVE-2024-13176&quot;) affecting component (&quot;Connector/ODBC&quot;). The (&quot;Supported Versions Affected&quot;) column only lists the 64-bit driver version. <br />
<br />
Can you confirm if the 32-bit is affected?<br />
If so, is the CVE resolved in the 32-bit 8.0.42 release?]]></description>
            <dc:creator>Jarod Burris</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Mon, 16 Jun 2025 05:37:46 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,740265,740265#msg-740265</guid>
            <title>Data Source Name Not Found and No Driver Specified (4 replies)</title>
            <link>https://forums.mysql.com/read.php?37,740265,740265#msg-740265</link>
            <description><![CDATA[ I installed MySQL 8.0 successfully on my brand new laptop (Win 11 64GB RAM if that&#039;s relevant)<br />
<br />
I updated my MDAC and installed Visual Studio C++ x86 Redistributable<br />
<br />
Then I downloaded and installed the MySQL 8.0 Drivers, and I was able to find them via C:\Windows\SysWOW64\odbcad32.exe <br />
<br />
I created a User DSN and restarted my laptop<br />
<br />
However, my development website continues to not find the drivers nor data source name<br />
<br />
&quot;Data Source Name Not Found and No Driver Specified&quot;<br />
<br />
This is a showstopper inasmuch as my development website fails to run, thus, no changes can be made to the Production version if I can&#039;t get the new development website to configure correctly.<br />
<br />
Anyone help? Thanks<br />
<br />
This is the connection string I created that worked fine before:<br />
<br />
var VALS = {};<br />
	<br />
	function populateVals() {<br />
		var key = &quot;&quot;;<br />
		var line = &quot;&quot;;<br />
		var keyVal = [];<br />
		var fso = Server.CreateObject(&quot;Scripting.FileSystemObject&quot;);<br />
		var file = fso.openTextFile(Server.MapPath(&quot;/.user.ini&quot;), 1);<br />
		do {<br />
			line = file.readLine();<br />
			if (!String.isNullOrEmpty(line) &amp;&amp; line.trim().indexOf(&quot;;&quot;) != 0 &amp;&amp;<br />
			    line.trim().indexOf(&quot;[&quot;) != 0 &amp;&amp; line.trim().indexOf(&quot;=&quot;) &gt; 0<br />
			    ) {<br />
				keyVal = line.split(&quot;=&quot;);<br />
				if (typeof keyVal !== &#039;undefined&#039; &amp;&amp; keyVal != null &amp;&amp; keyVal.length == 2 &amp;&amp; !String.isNullOrEmpty(keyVal[0])) {<br />
					key = keyVal[0].trim();<br />
					if (!String.isNullOrEmpty(keyVal[1]) &amp;&amp; keyVal[1].trim().startsWith(&quot;\&quot;&quot;) &amp;&amp; keyVal[1].trim().endsWith(&quot;\&quot;&quot;)) {<br />
						VALS[key] = keyVal[1].trim().substring(1, keyVal[1].trim().length - 1);<br />
					} else if (!String.isNullOrEmpty(keyVal[1])) {<br />
						VALS[key] = keyVal[1].trim();<br />
					}<br />
				}<br />
			}<br />
		} while (!file.atEndOfStream);<br />
		<br />
		file.close();<br />
		file = null;<br />
		fso = null;<br />
	}<br />
	<br />
	populateVals();<br />
<br />
var DB_CONNECTION_STR = <br />
		&quot;Provider=MSDASQL; DRIVER={MySQL ODBC 8.0 Unicode Driver}; SERVER=&quot; + VALS[&quot;mysql_db_host&quot;] + &quot;; PORT=&quot; +<br />
		 VALS[&quot;mysql_db_port&quot;] + &quot;; DATABASE=&quot; + VALS[&quot;mysql_db_name&quot;] + &quot;; UID=&quot; + VALS[&quot;mysql_db_user&quot;] + <br />
		 &quot;; PWD=&quot; + VALS[&quot;mysql_db_password&quot;] + &quot;; OPTION=3;&quot;;]]></description>
            <dc:creator>Phillip Powell</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Thu, 20 Feb 2025 02:01:10 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,740023,740023#msg-740023</guid>
            <title>authentication_ldap_sasl.so duplicate problem (1 reply)</title>
            <link>https://forums.mysql.com/read.php?37,740023,740023#msg-740023</link>
            <description><![CDATA[ Dear Colleagues,<br />
<br />
I&#039;ve got a server had a<br />
<br />
Distributor ID: Debian<br />
Description:    Debian GNU/Linux 11 (bullseye)<br />
Release:        11<br />
Codename:       bullseye<br />
<br />
and 7TB MySQL database. <br />
<br />
I need to create remote table, I cant do that with federated engine cuz our database size is too big and old. They&#039;re afraid of the cluster method fall when we do restart mysql. <br />
<br />
When I try to do that with ODBC connecter, I&#039;ve got error messagess. <br />
<br />
<br />
root@u:/# apt --fix-broken install<br />
Reading package lists... Done<br />
Building dependency tree... Done<br />
Reading state information... Done<br />
Correcting dependencies... Done<br />
The following additional packages will be installed:<br />
  mysql-community-client-plugins<br />
The following NEW packages will be installed:<br />
  mysql-community-client-plugins<br />
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.<br />
3 not fully installed or removed.<br />
Need to get 0 B/1,316 kB of archives.<br />
After this operation, 20.3 MB of additional disk space will be used.<br />
Do you want to continue? [Y/n] y<br />
(Reading database ... 43914 files and directories currently installed.)<br />
Preparing to unpack .../mysql-community-client-plugins_8.0.37-1debian11_amd64.deb ...<br />
Unpacking mysql-community-client-plugins (8.0.37-1debian11) ...<br />
dpkg: error processing archive /var/cache/apt/archives/mysql-community-client-plugins_8.0.37-1debian11_amd64.deb (--unpack):<br />
 trying to overwrite &#039;/usr/lib/mysql/plugin/authentication_ldap_sasl_client.so&#039;, which is also in package percona-server-server-5.7 5.7.44-48-1.bullseye<br />
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)<br />
Errors were encountered while processing:<br />
 /var/cache/apt/archives/mysql-community-client-plugins_8.0.37-1debian11_amd64.deb<br />
E: Sub-process /usr/bin/dpkg returned an error code (1)<br />
<br />
<br />
We&#039;re using percona server so &quot;authentication_ldap_sasl.so&quot; this file already created.<br />
<br />
Since I am new to Mysql, I am not familiar with the Percona content. I do not want to corrupt the file by trying overwrite or other methods.]]></description>
            <dc:creator>Ayçelen Çetince</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Tue, 14 Jan 2025 02:39:21 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,739872,739872#msg-739872</guid>
            <title>MySQL ODBC data sources not an option (1 reply)</title>
            <link>https://forums.mysql.com/read.php?37,739872,739872#msg-739872</link>
            <description><![CDATA[ I downloaded and installed mysql-connector-odbc-9.1.0-winx64; I opened the ODBC Data Source Administration (64-bit), from C:\Windows\System32\odbcad32.exe, however I do not have the option I see others describing to choose from which is &#039;MySQL ODBC 8.0 ANSI Driver&#039; (or Unicode).<br />
Therefore when trying to connect in excel VBA I get error: &quot;-2147467259: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified&quot;]]></description>
            <dc:creator>Edward Laier</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Tue, 14 Jan 2025 02:23:14 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,739779,739779#msg-739779</guid>
            <title>Help with generic error (5 replies)</title>
            <link>https://forums.mysql.com/read.php?37,739779,739779#msg-739779</link>
            <description><![CDATA[ I was hoping someone may be able to shed some light on the possible reasons for the generic error message we are seeing when using Connector/ODBC.  Usually we are connecting to an RDS database in AWS via ProxySQL.<br />
<br />
The most common time this is seen is when trying to open a datareader, at which point we receive the error:<br />
<br />
ERROR [HY000] [MySQL][ODBC 8.0(w) Driver][mysqld-5.7.40]<br />
<br />
Nothing else is returned in the message. This is unreliable to recreate, but when we have seen it on occassion the connection remains open, but effectively corrupt because further attempts to retry opening the data reader always return this message.<br />
<br />
Does anyone know what may be causing this issue, or how we can find more information out about the error?]]></description>
            <dc:creator>Paul Haynes</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Thu, 16 Jan 2025 02:33:35 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,733193,733193#msg-733193</guid>
            <title>Oracle MySQL Connectors (October 2024 CPU) (4 replies)</title>
            <link>https://forums.mysql.com/read.php?37,733193,733193#msg-733193</link>
            <description><![CDATA[ Hi all,<br />
We have another round of CVEs that are being flagged against the 32-bit driver. The publication (https://www.oracle.com/security-alerts/cpuoct2024.html) only lists the 64-bit driver (&quot;9.0.0 and prior&quot;) in the (&quot;Supported Versions Affected&quot;) column. <br />
<br />
If you could please confirm the 32-bit ODBC driver version that remediates these CVEs so we have the artifact necessary to remediate.<br />
<br />
CVE-2023-45853<br />
<br />
CVE-2024-5535<br />
<br />
CVE-2024-6119<br />
<br />
CVE-2024-21262<br />
<br />
CVE-2024-21272<br />
<br />
.... as an aside if there is a mechanism for the initial publication to include the 32-bit driver version as well it would alleviate the need for this type of request which I can see is becoming more frequent. <br />
<br />
Thank you for your attention on this]]></description>
            <dc:creator>Jarod Burris</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Thu, 28 Nov 2024 06:11:50 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,730666,730666#msg-730666</guid>
            <title>MySQL-connector-ODBC-9.1.0-macos14-arm64.dmg Failed installation (3 replies)</title>
            <link>https://forums.mysql.com/read.php?37,730666,730666#msg-730666</link>
            <description><![CDATA[ Hello community,<br />
<br />
Please your support with a failed installation.<br />
Software: Connector ODBC 9.1.0. for MacOs (downloaded from mysql website)<br />
Computer: MacOs14 - M1 - 64ARM.<br />
Priorly installed iODBC, ok.<br />
Message error: &quot;the installer encountered an error that caused the installation to fail&quot;<br />
I also attempt using the Terminal with Homebrew.<br />
<br />
I&#039;ll appreciate your help.]]></description>
            <dc:creator>Jose Caceres</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Mon, 11 Nov 2024 23:12:02 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,730575,730575#msg-730575</guid>
            <title>MySQL Connector ODBC v5.3.10 64bit (1 reply)</title>
            <link>https://forums.mysql.com/read.php?37,730575,730575#msg-730575</link>
            <description><![CDATA[ It would be great if someone can help me with the below<br />
<br />
I am trying to install MySQL Connector ODBC v5.3.10 64 bit. The operating system I am using is Windows Server 2019 version 1809.<br />
<br />
I keep getting error message when I try installing MySQL Connector ODBC v5.3.10 64bit<br />
<br />
This is the error message that comes up: <br />
error 1918: error installing odbc driver mysql odbc 5.3 driver, odbc error 13: the setup routines for the mysql odbc 5.3 driver could not be loaded due to system error code 126: the specified module could not be found ...\myodbc5s.dll).<br />
<br />
<br />
Are there any dependency I need to install for the 64 bit<br />
<br />
Thanks]]></description>
            <dc:creator>Ese Oronsaye</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Wed, 06 Nov 2024 01:05:20 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,730447,730447#msg-730447</guid>
            <title>MySQL ODBC Connector 9.1.0 - Connection Issues in ODBC Data Source Administrator and Connected Application (14 replies)</title>
            <link>https://forums.mysql.com/read.php?37,730447,730447#msg-730447</link>
            <description><![CDATA[ I have downloaded/ tried installing the MySQL ODBC Connector Version 9.1.0 from the General Availability Releases page; the installation completes successfully, but when I configure the DSN in 64-bit ODBC Data Source Administrator, and click &quot;Test&quot; (or click the &quot;Database&quot; dropdown), ODBC Data Source Administrator crashes.<br />
<br />
The connector also doesn&#039;t work from a connected 64-bit application which leverages it to connect to a MySQL database (running MySQL version 8), and causes the connected application to throw an exception and stop running.  I do not have this same issue with prior versions, including the other recommended version on the GA releases page, 8.0.4.<br />
<br />
Enabling tracing and testing the connection shows that the driver fails to complete the connection step.  The last entry logged to the tracing log file shows &quot;ENTER SQLDriverConnectW &quot;, but ends there with no further logs generated.<br />
<br />
Looking at event viewer, after ODBC Data Source Administrator crashes while testing the DSN I set up using the connector, I can see the below error message:<br />
<br />
&quot;Faulting application name: odbcad32.exe, version: 10.0.19041.1<br />
Faulting module name: MSVCP140.dll, version: 14.36.32532.0<br />
Exception code: 0xc0000005&quot;<br />
<br />
As far as I&#039;m aware, I have the correct dependencies installed on my machine (Microsoft Visual C++ 2015-2022) required for version 9.1.0, and version 8 of MySQL is supported in connector version 9.1.0.<br />
<br />
Has anyone else encountered this issue, or have any advice on how to remedy the error I&#039;m receiving?]]></description>
            <dc:creator>Shawn Conway</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Thu, 17 Apr 2025 19:16:07 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,729819,729819#msg-729819</guid>
            <title>8.0.40 32-bit version listed as vulnerable. (10 replies)</title>
            <link>https://forums.mysql.com/read.php?37,729819,729819#msg-729819</link>
            <description><![CDATA[ As per the CPUOCT2024 advisory, my odbc connector driver prior to 9.1.0 are vulnerable. We need a 32-bit version that connects to our application. We only have 8.0.40 as the last version with 32-bit odbc driver. What are the alternatives to connect to database from a 32-bit architecture application to mysql database using 9.1.0 64-bit driver ? or Anyone heard of plans to release a 32-bit driver for 9.1.0 version ?]]></description>
            <dc:creator>Dinesh kanagala</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Thu, 05 Dec 2024 16:24:00 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,727716,727716#msg-727716</guid>
            <title>CVE-2024-21262 (2 replies)</title>
            <link>https://forums.mysql.com/read.php?37,727716,727716#msg-727716</link>
            <description><![CDATA[ CVE-2024-21262 has been published with reference to the 64 bit version on the publication (&quot;9.0.0 and prior&quot;) but no mention of the 32 bit driver. Is the 8.0.37 or 8.0.40 release susceptible to/ a resolution for this exploit?<br />
 <br />
<a href="https://www.oracle.com/security-alerts/cpuoct2024.html"  rel="nofollow">https://www.oracle.com/security-alerts/cpuoct2024.html</a>]]></description>
            <dc:creator>Jarod Burris</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Tue, 22 Oct 2024 18:56:35 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,726673,726673#msg-726673</guid>
            <title>MySQL Connector/ODBC 64bit vs 32bit (no replies)</title>
            <link>https://forums.mysql.com/read.php?37,726673,726673#msg-726673</link>
            <description><![CDATA[ Dear ODBC users,<br />
<br />
a quick update on Connector/ODBC development plans:<br />
<br />
MySQL Connector/ODBC 64bit:<br />
— all future ongoing development will be 64bit only (no 32bit)<br />
— new features will be added<br />
— security vulnerabilities and critical bugs will be fixed<br />
<br />
MySQL Connector/ODBC 32bit:<br />
— 32bit development ends with 8.0.x (8.4.x, 9.x will be 64bit only)<br />
— no new features<br />
— only fixes for security vulnerabilities and critical bugs<br />
— releases will be Windows only<br />
<br />
<br />
Which Version is recommended:<br />
— always use the latest version of connector, regardless of version of Server<br />
— e.g. use Connector/ODBC 9.x with Server 8.0.x, 8.4.x LTS, 9.x<br />
<br />
<br />
It might look counter-intuitive, but I did not make a mistake:<br />
<br />
In 64-bit Windows: <br />
<br />
    The 64-bit executables and libraries are in %WINDIR%\System32<br />
       — The location of 64-bit ODBC Admin:  %WINDIR%\System32\odbcad32.exe<br />
<br />
    The 32-bit executables and libraries are in %WINDIR%\SysWow64<br />
       — The location of 32-bit ODBC Admin:  %WINDIR%\SysWow64\odbcad32.exe]]></description>
            <dc:creator>Bogdan Degtyariov</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Fri, 04 Oct 2024 00:55:57 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,726665,726665#msg-726665</guid>
            <title>MySQL ODBC Connector 8.0.37 vulnerability (1 reply)</title>
            <link>https://forums.mysql.com/read.php?37,726665,726665#msg-726665</link>
            <description><![CDATA[ Hi,<br />
<br />
We are limited to use 32bit of the MySQL ODBC Connector driver in our application, and hence we could only use the latest version 8.0.37.<br />
<br />
However, during a recently vulnerability scan, it is found that the following vulnerabilities have been found:<br />
<br />
  - CVE-2023-22102<br />
  - CVE-2023-6129<br />
<br />
We would like clarify if there will be a patch to fix these vulnerabilities?<br />
<br />
<br />
Thanks!<br />
<br />
Jack]]></description>
            <dc:creator>Jack Lee</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Mon, 21 Oct 2024 00:38:14 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,725666,725666#msg-725666</guid>
            <title>Error using latest 64Bit ODBC driver for windows 11 (7 replies)</title>
            <link>https://forums.mysql.com/read.php?37,725666,725666#msg-725666</link>
            <description><![CDATA[ I downloaded the latest MYSQL ODBC 64-bit drivers for Windows 11. After install and successful connection to my database (cloud), I tried to link to my database in Access 365 and got this message when trying to view the rows in a table: ODBC--Call failed .. all column headers appeared correctly, but all rows say #NAME?<br />
<br />
Yes if I import that same table the import works fine.<br />
<br />
If I try to build a query I get the same errors.<br />
<br />
Any ideas what can be the issue?]]></description>
            <dc:creator>Charles Szymaszek</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Fri, 18 Oct 2024 04:54:51 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,725479,725479#msg-725479</guid>
            <title>x86 ODBC Connector vulnerability (5 replies)</title>
            <link>https://forums.mysql.com/read.php?37,725479,725479#msg-725479</link>
            <description><![CDATA[ Hello<br />
<br />
I have a question where I have a 32-bit application that uses the ODBC 32-bit connector.<br />
<br />
We have had this security vulnerability identified - <a href="https://www.oracle.com/security-alerts/cpuapr2024.html#AppendixMSQL"  rel="nofollow">https://www.oracle.com/security-alerts/cpuapr2024.html#AppendixMSQL</a> - CVE-2023-6129 which is 8.3.0 and prior.<br />
<br />
The latest x86 version of the ODBC connector is 8.0.37. Is there a plan to release a patch for x86 in the 8.0.X line for this vulnerability?<br />
<br />
Thanks]]></description>
            <dc:creator>Paul Haynes</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Sun, 06 Oct 2024 05:41:45 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,725439,725439#msg-725439</guid>
            <title>HELP: ODBC Connector not working correctly (1 reply)</title>
            <link>https://forums.mysql.com/read.php?37,725439,725439#msg-725439</link>
            <description><![CDATA[ Note: I am not a developer and don&#039;t understand how this connector works. However, it has worked fine for me for years.<br />
<br />
I need help determining which version of MySQL Connector/ODBC will work for me. I am using MS Access and need to connect to an external database. From my experience, these connections are very finicky. Corporate just sent me a new laptop and I can&#039;t get this connection working. It works just fine on my previous laptop.<br />
<br />
Previous laptop: Windows 10 Enterprise. System Type: 64-bit operating system. MySQL Connector/ODBC 8.0 (32-bit). Yes, the only one that works on that 64-bit system is a 32-bit MySQL version.<br />
<br />
New Laptop: Windows 11 Enterprise. System Type: 64-bit operating system. When trying to use a 32-bit version I receive a message saying there is an architectural conflict. It sounds like 32-bit is not even an option on Windows 11.<br />
<br />
On the new laptop, when setting up a connection to the database I have the option of downloading the tables or creating links to the tables. I can download the tables just fine. However, I need links to the tables. When I choose to create links and then open a link to a table I receive a message saying ODBC call failed. After clicking OK on the message, the table opens, but every field in every record contains #Name?. The field names are there and the rows are there. Just no data.<br />
<br />
Any help would be greatly appreciated.<br />
<br />
Dale]]></description>
            <dc:creator>Dale Logan</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Mon, 26 Aug 2024 17:58:35 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,725404,725404#msg-725404</guid>
            <title>ODBC &amp; Multiple Statements (1 reply)</title>
            <link>https://forums.mysql.com/read.php?37,725404,725404#msg-725404</link>
            <description><![CDATA[ am i right in thinking that since MySQL 8.0.24 i can&#039;t send multiple statements within a single ODBC query?]]></description>
            <dc:creator>Nigel Gomm</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Fri, 04 Oct 2024 05:10:31 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,725292,725292#msg-725292</guid>
            <title>dlopen(/usr/local/mysql-connector-odbc-9.0.0-macos14-x86-64bit/lib/libmyodbc9w.so, 0x0006): tried: &#039;/us [SQLSTATE=00000] (1 reply)</title>
            <link>https://forums.mysql.com/read.php?37,725292,725292#msg-725292</link>
            <description><![CDATA[ I installed 3 software: iODBC,ODBC Manager,and mysql-connector-odbc-9.0.0.<br />
My computer OS system is Mac.<br />
when I load the database by JMP17.2,it produces error.<br />
Error message:<br />
[iODBC][Driver Manager]dlopen(/usr/local/mysql-connector-odbc-9.0.0-macos14-x86-64bit/lib/libmyodbc9w.so, 0x0006): tried: &#039;/us [SQLSTATE=00000]<br />
<br />
Who could tell me how to solve it?]]></description>
            <dc:creator>Alison Alison</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Thu, 01 Aug 2024 07:10:47 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,725182,725182#msg-725182</guid>
            <title>32 bit odbc connection not working (6 replies)</title>
            <link>https://forums.mysql.com/read.php?37,725182,725182#msg-725182</link>
            <description><![CDATA[ I ran the installer for the odbc connection for 9.0.0 and noticed that there was no 32 bit version available to execute. when i created a data source in the 64 bit app, it also created the same connection in 32 bit using a 64 bit driver. when i try to create a dataset in SSRS, I get the IM014 architecture mismatch, and there is no 32 bit driver to choose in order to create a 32 bit connection. i am confused. is there another place that i am not aware of to find a 32 bit .exe file, or is it a one size fits all?]]></description>
            <dc:creator>Darren Richards</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Fri, 04 Oct 2024 08:09:38 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,725167,725167#msg-725167</guid>
            <title>How to change maximum execution time with MS Access&amp;MySQL Connector/ODBC (2 replies)</title>
            <link>https://forums.mysql.com/read.php?37,725167,725167#msg-725167</link>
            <description><![CDATA[ In MS Access, By right-clicking on the [Table] pane and selecting [Import] -&gt; [ODBC Database], importing source data into a new table in the current database.<br />
When using the MySQL ODBC 8.0 Unicode Driver to import tables smaller than 200MB in row file format, the error &quot;[MySQL][ODBC 8.0(w) Driver][mysqld-{version}-log]Query execution was interrupted, maximum statement execution time exceeded (#3024)&quot; frequently occurs.<br />
<br />
Since the MySQL server we are connecting to does not have an execution time limit, i suspect that Access or the Driver is imposing this limit. What solutions can ensure a stable import process?<br />
<br />
The connection information screen for the MySQL Connector does not have a relevant setting option (including in Details), and setting `SET @@session.max_execution_time = nnnnn` in the Initial Statement did not work.<br />
<br />
My environment is as follows:<br />
<br />
Windows 10 Pro<br />
Microsoft Access For Microsoft 365 MSO (Version 2406 Build 16.0.17726.20078) 64-bit<br />
.accdb 2007 - 2016 file format<br />
MySQL ODBC 8.0 Unicode Driver<br />
<br />
Any help or suggestions would be greatly appreciated. Thank you!]]></description>
            <dc:creator>Sonosuke Tarumoto</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Wed, 21 Aug 2024 09:22:09 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,725035,725035#msg-725035</guid>
            <title>Issues with bound parameters using ODBC Connector 8.4 &amp; 9.0 (3 replies)</title>
            <link>https://forums.mysql.com/read.php?37,725035,725035#msg-725035</link>
            <description><![CDATA[ Hi,<br />
<br />
I&#039;m experiencing some erroneous/erratic behaviour using the latest ODBC connectors (8.4 and now 9.0) on Win64 where bound parameters are concerned (these issues are not apparent with earlier versions).<br />
<br />
Firstly, when connecting to a 5.7x database, every query I execute that has a bound parameter fails with the following error:<br />
<br />
[MySQL][ODBC 9.0(w) Driver][mysqld-5.7.44-0ubuntu0.18.04.1+esm1]No data supplied for parameters in prepared statement;<br />
<br />
What is interesting though is that looking at the traffic to/from the server, I can see no problems at this level, the connector is issuing a prepare statement which the server responds to with a success status.<br />
<br />
Secondly, when connecting to a 8.0x database, the behaviour is generally ok however there are particular scenarios where it fails. I have one particular query, that will always fail the first time I run it. In this instance, it comes back with this error:<br />
<br />
[MySQL][ODBC 9.0(w) Driver][mysqld-8.0.37-0ubuntu0.22.04.3]Using unsupported buffer type: %d  (parameter: %d) <br />
<br />
Of an in itself that error is weird in that it looks like a template string, in that I would expect at least one of those &quot;%d&quot; tokens to be populated. However if I then run that query again, without changing any of the bound parameters ie. literally calling SQLExecDirect again, it will succeed.<br />
<br />
Again, looking at the traffic between the client and server, I see what appears to be an identical exchange as with the 5.7 one - a prepare statement is sent and is acknowledged successfully by the server.<br />
<br />
Jon.]]></description>
            <dc:creator>Jon Bird</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Sat, 13 Jul 2024 12:07:15 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,724959,724959#msg-724959</guid>
            <title>fail to reconnect to mysql8 (1 reply)</title>
            <link>https://forums.mysql.com/read.php?37,724959,724959#msg-724959</link>
            <description><![CDATA[ I am getting this error below after attempting to reconnect to MySql8 using odbc version 8.036 in windows 10 with 32bit.<br />
<br />
I does work for first time but after trying to reconnect again I get this error below. Then after waiting 2 minutes and try again it work again<br />
but trying again immediatly will fail.<br />
<br />
I don&#039;t have connection issue from mac system using MySql Workbench8<br />
 <br />
<br />
MySQL][ODBC 8.0(w) Driver]Can&#039;t connect to MySQL server on &#039;xxxxxxx.rds.amazonaws.com:3306&#039; (10060)&quot;<br />
<br />
<br />
odbcad32        214-1a70 ENTER SQLGetDiagRecW<br />
SQLSMALLINT                  2 &lt;SQL_HANDLE_DBC&gt;<br />
SQLHANDLE           0x07311BA0<br />
SQLSMALLINT                  1<br />
SQLWCHAR *          0x02AB9C04<br />
SQLINTEGER *        0x02AB9EB3<br />
SQLWCHAR *          0x03F5EB58<br />
SQLSMALLINT                511<br />
SQLSMALLINT *       0x02AB9C50<br />
<br />
odbcad32        214-1a70 EXIT  SQLGetDiagRecW  with return code 0 (SQL_SUCCESS)<br />
SQLSMALLINT                  2 &lt;SQL_HANDLE_DBC&gt;<br />
SQLHANDLE           0x07311BA0<br />
SQLSMALLINT                  1<br />
SQLWCHAR *          0x02AB9C04 [       5] &quot;HY000&quot;<br />
SQLINTEGER *        0x02AB9EB3 (2003)<br />
SQLWCHAR *          0x03F5EB58 [     141] &quot;[MySQL][ODBC 8.0(w) Driver]Can&#039;t connect to MySQL server on &#039;xxxxxxxxx.rds.amazonaws.com:3306&#039; (10060)&quot;<br />
SQLSMALLINT                511<br />
SQLSMALLINT *       0x02AB9C50 (141)<br />
<br />
odbcad32        214-1a70 ENTER SQLFreeHandle<br />
SQLSMALLINT                  1 &lt;SQL_HANDLE_ENV&gt;<br />
SQLHANDLE           0x07310728<br />
<br />
odbcad32        214-1a70 EXIT  SQLFreeHandle  with return code -1 (SQL_ERROR)<br />
SQLSMALLINT                  1 &lt;SQL_HANDLE_ENV&gt;<br />
SQLHANDLE           0x07310728<br />
<br />
DIAG [HY010] [Microsoft][ODBC Driver Manager] Function sequence error (0)]]></description>
            <dc:creator>Sami Kamber</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Mon, 08 Jul 2024 03:03:04 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,724829,724829#msg-724829</guid>
            <title>ODBC Connector broke with Win2019 update (1 reply)</title>
            <link>https://forums.mysql.com/read.php?37,724829,724829#msg-724829</link>
            <description><![CDATA[ I have several legacy vbscript/ASP apps that were connecting to MySQL 8 via ODBC driver 8.0. In the past week, something changed that is preventing all of those apps from being able to connect to MySql. <br />
<br />
I&#039;ve tried upgrading drivers to 8.4, double checked the connection strings, verified successful test from the 64 bit ODBC administration, and can access the databases from php and the workbench. Even tried dropping back to 5.3 with the same results.<br />
<br />
I don&#039;t see any MySql drivers in the 32 bit ODBC administrator, even when staring it from the SysWOW64 folder.<br />
<br />
I&#039;m at a loss and need to get these apps running again. The error message is:<br />
<br />
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified<br />
<br />
Connection String:<br />
<br />
{DRIVER=MySQL ODBC 8.4 Unicode Driver}; <br />
UID=*******;USER=*********;PASSWORD=*************;<br />
SERVER=localhost;PORT=3306;_<br />
NO_SCHEMA=1;DB=*******;DATABASE=*******;]]></description>
            <dc:creator>Stu Stevenson</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Tue, 18 Jun 2024 05:00:16 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,724555,724555#msg-724555</guid>
            <title>MySql ODBC driver on Windows 11 (1 reply)</title>
            <link>https://forums.mysql.com/read.php?37,724555,724555#msg-724555</link>
            <description><![CDATA[ Hallo,<br />
<br />
I have downloaded both the mdac28sdk.msi and the zip file(s) mysql-connector-odbc-8.4.0-winx64-debug.zip and mysql-connector-odbc-8.4.0-winx64.zip .<br />
<br />
I ran the .msi file but cannot see the MySql ODBC driver. <br />
<br />
I followed the advice on several web sites such as <a href="https://docs.informatica.com/integration-cloud/data-integration-connectors/current-version/mysql-connector/introduction-to-mysql-connector/administration-of-mysql-connector/installing-mysql-odbc-driver/installing-mysql-odbc-driver-on-windows.html"  rel="nofollow">https://docs.informatica.com/integration-cloud/data-integration-connectors/current-version/mysql-connector/introduction-to-mysql-connector/administration-of-mysql-connector/installing-mysql-odbc-driver/installing-mysql-odbc-driver-on-windows.html</a> <br />
and <br />
<a href="https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-configuration-dsn-windows-5-2.html"  rel="nofollow">https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-configuration-dsn-windows-5-2.html</a><br />
<br />
I followed the advice on these pages, restarted my laptop several times but still do not see the MySql ODBC drivers in the ODBC Data Source Administrator GUI.<br />
<br />
I even edited the Registry to ensure that there is no default value for the MySql ODBC key.<br />
<br />
Any advice on how to resolve this challenge?<br />
<br />
Phlip Pretorius]]></description>
            <dc:creator>PHLIP Pretorius</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Mon, 08 Jul 2024 06:31:54 +0000</pubDate>
        </item>
        <item>
            <guid>https://forums.mysql.com/read.php?37,723148,723148#msg-723148</guid>
            <title>host_cache operation (1 reply)</title>
            <link>https://forums.mysql.com/read.php?37,723148,723148#msg-723148</link>
            <description><![CDATA[ We have multiple MySQL servers running 5.7 and 8.x. We are encountering errors with connections to these hosts and when we attempt to connect via telnet to verify network connectivity, we are getting the error:<br />
<br />
Host &#039;x.x.x.x&#039; is blocked because of many connection errors; unblock with &#039;mysqladmin flush-hosts&#039;Connection closed by foreign host.<br />
<br />
We run flush hosts to clear the cache but i am trying to find out if the host_cache counter resets itself for a particular ip address as part of normal operation (maybe after a successful connection from the ip address).<br />
<br />
If the value only goes up and would never reset based upon the default behavior, is there any tuning that can be done short of disabling the setting or putting the value to a theoretically unreachable number?]]></description>
            <dc:creator>Louis Seefried</dc:creator>
            <category>Connector/ODBC</category>
            <pubDate>Mon, 08 Jul 2024 03:07:41 +0000</pubDate>
        </item>
    </channel>
</rss>
