Quantcast
Channel: MySQL Forums - Connector/ODBC
Viewing all 1136 articles
Browse latest View live
↧

automation error specified module could not be found (no replies)

September 23, 2021, 8:18 am
$
0
0
Hello,

Following a migration of database from MySQL server 5.0.68 to 8.0.26, I tested existing xlsm files.

On old Win10 user stations equipped with Office 2007 or 2010, no problem, the old macros have all run well with the mysql-connector-odbc-8.0.26-win32.msi driver and the new MySQL server 8.

But on the new PC Win10 + Office2016, we have the msgBox: "The method 'Open' of the object '_Connection' has failed", correspondind to the detailed error:
: Description : "automation error specified module could not be found." String: ADOMySQL.OpenConnection

I checked the additional macros and the VBA references used, they are identical on the old and new computers.

The driver is well installed in Win64 and Win32 for security; and checked via odbcad32.

If anyone has an idea, I'm interested because I don't have any more...
↧
Search

SSMS Linked Server Connection Issue (no replies)

September 24, 2021, 5:35 am
$
0
0
I'm trying to create a linked server from my SSMS to a MySQL db. No matter what I do, I get the following error:

Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "<Linked Server Name>".
OLE DB provider "MSDASQL" for linked server "<Linked Server Name>" returned message "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified". (Microsoft SQL Server, Error: 7303)

I've selected/entered the following for my linked server:
Other Data Source
Provider: Microsoft OLE DB Provider for ODBC Drivers
Product Name: MYSQL
Data Source: I left this blank
Provider String: DRIVER=(MySQL ODBC 8.0 ANSI Driver); SERVER=xxx.xxx.xxx.xxx; PORT=xxxx; DATABASE=<db name>; USER=<user name>; PASSWORD=<password>; OPTION=3;

I've also tried other versions of the Provider string:
DRIVER=(MySQL ODBC 8.0 Unicode Driver); SERVER=xxx.xxx.xxx.xxx; PORT=xxxx; DATABASE=<db name>; USER=<user name>; PASSWORD=<password>; OPTION=3;

I have also ensured I have the latest ODBC drivers (both 32 and 64 installed). I have been able to make an ODBC Server DSN connection successfully. If I try to create the Linked Server referencing the server DSN I get the same error:

Provider: Microsoft OLE DB Provider for ODBC Drivers
Product Name: MYSQL
Data Source: MySQL Quantum Black X64
Provider String: I left blank

What do I need to do to make the linked server work?
↧
↧

MySQL (no replies)

October 3, 2021, 4:55 am
$
0
0
I have a ODBC Connection on an Excel Workbook. I created the connection through Access.

Both Access and Excel repeatedly ask for credentials, when I open the file and when I refresh the data.

I would to know how I can turn this off and make my credential entry enduring.

I have ignored the issue while developing the application, but now need resolve this issue before deployment. Constantly entering credentials will create a productivity issue.

Any help welcome.
↧

MYSQL ERRORS ON SPECIFIC COMPUTERS (no replies)

October 5, 2021, 9:11 am
$
0
0
I am using MYSQL CONNECTOR as a driver for ODBC connection to a MYSQL database.
It is generally working nicecly, but I recently encountered an unexpected problem when the program runs on certain computers.

I am aware of the problem by getting a message from the server that indicates a SQL syntax error. The message is truncated, so I cannot see enough to really see what the error is.

From some investigation I have found this pattern:
If I generate a SQL query and issue it as a command, this seems to work on any computer.

Example (always works) -------------------------------

dim query as string
Dim cmd As New ADODB.Command
cmd.ActiveConnection = conn (valid working connection)
query = "UPDATE TABLENAME SET FIELDNAME = 'SOMETHING' WHERE OTHERFIELD = 'x';
cmd.CommandText = query
cmd.Execute


Example (doesn't work on some compuers) ------------
Set recset = New ADODB.Recordset
query = "SELECT * FROM TABLENAME;"
recset.Open query, conn, adOpenDynamic, adLockOptimistic
recset.fields("FIELDNAME") = "SOMETHING"
recset.update
recset.close

It seems to me that the ODBC recordset is converting the action into a MYSQL query and sending it to the database, and hence the error comes up as a syntax problem. However, when I send the SQL query directly as a command, it doesn't cause this problem.

I have some suspicion that the problem may relate to a language or locale setting, but the different computers seem to be the same as far as I can tell.

Does anyone know how I can see the actual SQL query that the recordset object is sending to the server? Or know how the recordset (update) method works to send differently from the command.execute method?

I may be forced to rewrite my code to use only the command route, but the recordset methodology is much more convenient and, (I was hoping) more efficient.

In case it helps, the connection to the MYSQL server is like this:
constring = "DRIVER=MySQL ODBC 8.0 Unicode Driver;"

constring = constring & "PORT=3306;SERVER=xxxxxx;"
constring = constring & "database=defschema"

Thanks in advance for any insights...
↧

DSN Configuration on Centos: Wrong or unknown protocol (no replies)

October 7, 2021, 5:10 am
$
0
0
A DSN configuration on Centos Linux 7 is not working anymore.

I am not sure if this was caused by an OS update or similar.

When testing the DSN configuration by using the isql command, the following output is produced:

[root@server etc]# isql -v DSNDGESQL01pflAnsi
[S1000][unixODBC][MySQL][ODBC 8.0(a) Driver]Wrong or unknown protocol
[ISQL]ERROR: Could not SQLConnect

The DSN configuration looks as follows:

[DSNDGESQL01pflAnsi]
Driver = /usr/lib64/libmyodbc8a.so
Description = Connector/ODBC 8.0 ANSI Driver DSN
SERVER = serveradress
CHARSET = UTF8MB4
PORT = 3306
USER = user
Password = password
Database = DBName
OPTION = 4
SOCKET = /var/lib/mysql/mysql.sock

The Server can connect to the SQL server through mySQL Shell with the same adress, user and password as provided in the DSN configuration.

I could not find anything explaining where a "wrong protocol" was provided.

Has anyone ever experienced a similar issue?

Kind regards.
↧
↧

Turning Of Encryption Between ODBC to Localhost Database (no replies)

October 10, 2021, 9:50 pm
$
0
0
Hi,

I am hoping that I have found the right place.

I have been tasked with optimizing our server.

I am trying to turn off encryption and decryption for SQL requests made to localhost.
But would like to be able to encrypt requests sent to replication databases.

I have noticed that there is a large portion of exclusive samples come from the TaoCrypt library doing encryption, decryption, and transform.

TaoCrypt::AES::decrypt 5,998 5,998 1.42% 1.42%
TaoCrypt::SHA::Transform 4,954 4,954 1.17% 1.17%
TaoCrypt::AES::encrypt 4,296 4,296 1.01% 1.01%

Looking into this a bit more, I have found the following stack trace:

TaoCrypt::AES::encrypt
TaoCrypt::Mode_BASE::CBC_Encrypt
yaSSL::`anonymous namespace`::buildMessage
yaSSL::sendData
vio_ssl_write
net_write_raw_loop
net_write_packet
net_flush
net_write_command
cli_advanceed_command
mysql_send_query
mysql_real_query
do_query
my_SQLExecute

This is basically the same for TaoCrypt::AES::decrypt.

In this test, the database is not issuing replication commands.
I would like to be able to employ encryption & decryption to non-local host databases.

I am using MySQL ODBC 5.3 Unicode driver.

What I have tried to do:
In the MySQL Connector/ODBC GUI window

Under the connections tab
[x] Disable default SSL

Under the SSL tab
[X] Disable TLS Version 1
[X] Disable TLS Version 1.1
[X] Disable TLS Version 1.2

I have been unable to find any documentation on this subject otherwise.

I am hoping that you would be able to provide me with how or guide me to the correct documentation so that I can turn off commands being encrypted and decrypted for requests being sent from ODBC to the database on the same server.

Sincere Regards,
Carl
↧

ODBC Connection Faliure (1 reply)

October 14, 2021, 10:33 am
$
0
0
Connection Failed
MYsql ODBC8.0(w) driver can't connect to mysql server on
158.230.38.77,3306(10060)

The above message appear when I try to establish ODBC conncetion

Pls help me to correct the situation
↧

Display size column width parameter odbc.ini (no replies)

November 1, 2021, 8:37 am
$
0
0
Is there an ODBC parameter that will allow us to set the maximum display size of a returned column from mySQL, or is there default width we need to override? Currently the result is being truncated at 300 characters and the column type is JSON. Is there perhaps an odbc.ini setting to override, or an MySQL setting to stop limiting it?

The equivalent command in isql is -L<n> where n is the width we want to display.

E.g. isql -L5000

Thanks in advance.
↧
Search

MySQL Connector/ODBC 8.0 27 64x installation Windows11 (2 replies)

November 9, 2021, 1:10 am
$
0
0
Hi!
I can't to install MySQL Connector/ODBC 8.0 27 64x on Windows11 and appears error:

Error 1918.Error installing ODBC driver MySQL ODBC 8.0 ANSI Driver, ODBC error 13: The setup routines for the MySQL ODBC 8.0 ANSI Driver ODBC driver could not be loaded due to system error code 193: .. Verify that the file MySQL ODBC 8.0 ANSI Driver exists and that you can access it.

Can anybody help me?
↧
↧

ODBC driver (1 reply)

January 3, 2022, 12:52 pm
$
0
0
Hi all,

We are using MySQL Odbc connector 5.3 to connect MS access . Unfortunately I always the below error. Can anyone suggest.

Error: Could not lock file
↧

Connecting to IBM DB2 database (no replies)

January 3, 2022, 7:46 pm
$
0
0
Good day everyone. I am new to MYSQL and I would like to write queries to connect to an DB2 database. I can connect to it utilizing WINSQL, MSACCESS and Crystal Reports. How do I accomplish this utilizing MYSQL?
↧

ODBC Connector 8.0 on Windows 11 ARM (no replies)

January 7, 2022, 3:46 am
$
0
0
Hi
Is it possible to install the unicode connector 8.0.27 on Windows 11 ARM?
Many thanks
↧

MySQL ODBC Connector 8.0.27 connect to old MySQL 5.0.38 database (no replies)

January 20, 2022, 4:04 pm
$
0
0
We are working on upgrade the MySQL to 8.0.27. Some of our customers still have old database on 5.0.38. We got error when try to use the 8.0.27 ODBC connector to connect to the 5.0.38.

Does the 8.0.27 ODBC connector support old 5.0.38 database? If not, is there any workaround to make it work?

Thanks.
Yao
↧
↧

ORACLE ODBC USING CONNECT TO MYSQL (1 reply)

January 24, 2022, 3:18 am
$
0
0
Dear experts,



I am working on setting up a MYSQL ODBC. and I tried to query with DB LINKS.

but it showed errors message. but, isql method can access mysql server.



i installed odbc with root. here is my question. why it is the different odbcinist when i commaned with oracle account.

so i guesss that when it try to connect with ORACLE HS, it can't find ODBC... please my experts save me..



[root@doj-stg-api-ora-01 etc]# odbcinst -j

unixODBC 2.3.4

DRIVERS............: /usr/local/etc/odbcinst.ini

SYSTEM DATA SOURCES: /usr/local/etc/odbc.ini

FILE DATA SOURCES..: /usr/local/etc/ODBCDataSources

USER DATA SOURCES..: /root/.odbc.ini

SQLULEN Size.......: 8

SQLLEN Size........: 8

SQLSETPOSIROW Size.: 8





su - oracle odbcinst -j



[oracle@doj-stg-api-ora-01 ~]$ odbcinst -j

unixODBC 2.3.1

DRIVERS............: /etc/odbcinst.ini

SYSTEM DATA SOURCES: /etc/odbc.ini

FILE DATA SOURCES..: /etc/ODBCDataSources

USER DATA SOURCES..: /home/oracle/.odbc.ini

SQLULEN Size.......: 8

SQLLEN Size........: 8

SQLSETPOSIROW Size.: 8



-------------------------------------------------------------------------------------------------------------------------

[root@doj-stg-api-ora-01 etc]# isql MYSQL "skbb"

+---------------------------------------+

| Connected! |

| |

| sql-statement |

| help [tablename] |

| quit |

| |





SQL> select * from auth_token@MYSQL;

select * from auth_token@MYSQL



ERROR at line 1:

ORA-28500: connection from ORACLE to a non-Oracle system returned this message:

ORA-02063: preceding line from MYSQL





setting HS_FDS_RSET_RETURN_ROWCOUNT to default of "FALSE"

setting HS_FDS_PROC_IS_FUNC to default of "FALSE"

setting HS_FDS_MAP_NCHAR to default of "TRUE"

setting HS_NLS_DATE_FORMAT to default of "YYYY-MM-DD HH24:MI:SS"

setting HS_FDS_REPORT_REAL_AS_DOUBLE to default of "FALSE"

setting HS_LONG_PIECE_TRANSFER_SIZE to default of "65536"

setting HS_SQL_HANDLE_STMT_REUSE to default of "FALSE"

setting HS_FDS_QUERY_DRIVER to default of "TRUE"

setting HS_FDS_SUPPORT_STATISTICS to default of "FALSE"

setting HS_FDS_QUOTE_IDENTIFIER to default of "TRUE"

setting HS_KEEP_REMOTE_COLUMN_SIZE to default of "OFF"

setting HS_FDS_GRAPHIC_TO_MBCS to default of "FALSE"

setting HS_FDS_MBCS_TO_GRAPHIC to default of "FALSE"

Default value of 64 assumed for HS_FDS_SQLLEN_INTERPRETATION

setting HS_CALL_NAME_ISP to "gtw$:SQLTables;gtw$:SQLColumns;gtw$:SQLPrimaryKeys;gtw$:SQLForeignKeys;gtw$:SQLProcedures;gtw$:SQLStatistics;gtw$:SQLGetInfo;gtw$:OPTTables;gtw$:OPTColumns;gtw$:OPTPrimaryKeys;gtw$:OPTForeignKeys;gtw$:OPTProcedures;gtw$:OPTStatistics"

setting HS_FDS_DELAYED_OPEN to default of "TRUE"

setting HS_FDS_WORKAROUNDS to default of "0"

setting HS_WORKAROUNDS to default of "0"

Exiting hgosdip, rc=0

ORACLE_SID is "MYSQL"

Product-Info:

Port Rls/Upd:0/0 PrdStat:0

Agent:Oracle Database Gateway for ODBC

Facility:hsa

Class:ODBC, ClassVsn:19.0.0.0.0_0024, Instance:MYSQL

Exiting hgogprd, rc=0

HOA 01/24 15:31:51.286248000: (hotker_ExecuteRpcs) ncrorpi: status = 0

HOA 01/24 15:31:51.289866000: (hotker_ExecuteRpcs) ncrorpi: status = 0

Entered hgoinit

HOCXU_COMP_CSET=1

HOCXU_DRV_CSET=846

HOCXU_DRV_NCHAR=873

HOCXU_DB_CSET=846

HS_LANGUAGE is AMERICAN_AMERICA.KO16MSWIN949

LANG=ko_KR.UTF-8

HOCXU_SEM_VER=122020

HOCXU_VC2_MAX=4000

HOCXU_RAW_MAX=2000

Entered hgolofn at 2022/01/24-15:31:51

No ODBC library specified.

Exiting hgolofn, rc=28500 at 2022/01/24-15:31:51

Exiting hgoinit, rc=28500 with error ptr FILE:hgoinit.c LINE:442 ID:Loading ODBC aray of function ptrs

HOA 01/24 15:31:51.290558000: (hotker_ExecuteRpcs) ncrorpi: status = 0

Entered hgoexit

HS Gateway: NULL connection context at exit

Exiting hgoexit, rc=0 with error ptr FILE:hgoexit.c LINE:118 ID:Connection context

HOA 01/24 15:31:51.290602000: (hotker_ExecuteRpcs) Exiting...

HOA 01/24 15:31:51.290623000: (horcrces_CleanupExtprocSession) Entered!

HOA 01/24 15:31:51.290631000: (horcrpooe_PopOciEnv) Entered!

HOA 01/24 15:31:51.290639000: (horcrfoe_FreeOciEnv) Entered!

HOA 01/24 15:31:51.290646000: (horcrfoe_FreeOciEnv) Exiting...

HOA 01/24 15:31:51.290653000: (horcrfse_FreeStackElt) Entered!

HOA 01/24 15:31:51.290661000: (horcrfse_FreeStackElt) Exiting...
↧

odbc can not get the whole utf8 string (no replies)

February 16, 2022, 1:04 am
$
0
0
I create a database with utf8:

connect mysql:

#mysql -h 192.168.26.42 -u root -p

mysql> show variables like 'collation_%';
+----------------------+-------------------+
| Variable_name | Value |
+----------------------+-------------------+
| collation_connection | utf8_general_ci |
| collation_database | utf8mb4_bin |
| collation_server | latin1_swedish_ci |
+----------------------+-------------------+
3 rows in set (0.00 sec)

then create a table:

mysql> create table test_tab(f1 int, f2 varchar(25));
Query OK, 0 rows affected (0.12 sec)

insert 1 row:
mysql> insert into test_tab values(1, "沙子沙子沙子沙子沙子");
Query OK, 1 row affected (0.02 sec)

ps:"沙子沙子沙子沙子沙子" is Chinese；

select row:
mysql> select f2 from test_tab where f1 = 1;
+--------------------------------+
| f2 |
+--------------------------------+
| 沙子沙子沙子沙子沙子 |
+--------------------------------+
1 row in set (0.00 sec)

I can get whe whole utf8 string;

##########################################
I config ODBC DSN like that:
[ssodb]
Driver=/usr/lib64/libmyodbc8w.so
SERVER=192.168.26.42
PORT=3306
Database=sso
CHARSET=UTF8

then run:
#isql ssodb root 123456 -v

select row with odbc:
SQL> select f2 from test_tab where f1 = 1;
+--------------------------+
| f2 |
+--------------------------+
| 沙子沙子沙子沙子+--------------------------+
SQLRowCount returns 1
1 rows fetched

I just can get "沙子沙子沙子沙子" but not "沙子沙子沙子沙子沙子";
How i can get the whole utf8 string with ODBC?
It seems ODBC just get 25/3 utf8 character； 25 is the size of column
f2；3 is ths utf8 character size;

ps:
unixODBC version:2.3.7/2.3.9
mysql-connector-odbc version:8.0.15/8.0.28
mysql server version:5.6.39
↧
Search

Error con SSL (2 replies)

February 16, 2022, 2:31 pm
$
0
0
[MySQL][ODBC 8.0(w) Driver]SSL connection error: error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol

Please helpme
↧

MySQL ODBC Win ARM (no replies)

March 15, 2022, 7:30 pm
$
0
0
M1 Mac running Win 11 (ARM) on Paralells. x86/x64 MySQL ODBC driver won't install.

Need the ARM version. And there is obviously an ARM Version of the driver but none are compiled for Win EXE.

I have not the first clue how to download the source and compile ARM driver with a EXE.

How can I be the only one trying to solve this?
↧
↧

mysql-connector-odbc-8.0.28-1.el7.i686 on Linux 7 not able to make odbc connection (no replies)

March 30, 2022, 2:44 am
$
0
0
I have written one test program and compiled it with both the versions of unixodbc2.25 and unixodbc latest version 2.3.9 and it was getting connected properly on with mysql-connector-odbc-8.0.28-1.el6.i686 version on both Linux7 and Linux 6.

Linux6 -indev-rhel6-3
/home/sunil.kumar/NX-10525> hn
indev-rhel6-3
/home/sunil.kumar/NX-10525> ./test1
Connected !
/home/sunil.kumar/NX-10525> ./test2
Connected !
/home/sunil.kumar/NX-10525>
Linux7 -inqa-rhel7-3
inqa-rhel7-3% ./test4
Connected !
inqa-rhel7-3% ./test5
Connected !
inqa-rhel7-3%
But when I write the same program and compile it with both the versions of unixodbc2.25 and unixodbc 2.3 version.
I installed mysql-connector-odbc-8.0.28-1.el7.i686 on Linux 7 it is not getting connected and core is dumped.

Linux7 -inqa-rhel7-4
/home/sunil.kumar/NX-10525> ./test3
Segmentation fault (core dumped)
/home/sunil.kumar/NX-10525/25Mar> ./test
Segmentation fault (core dumped)
/home/sunil.kumar/NX-10525/25Mar
↧

ODBC can't connect to server with certain passwords - how to circumvent? (no replies)

April 1, 2022, 6:14 am
$
0
0
We have MySQL 5.7.34 running on a Debian machine, and have installed the newest (at the time of writing this) version of the ODBC x64 driver on a Windows 10 x64 machine (ODBC x64 driver version 8.00.28.0).

We usually implement very long passwords for our database users and identify the users by sha256_password. We have wondered why a certain user couldn't connect from Windows to the databases on the server. It turned out that the problem depended on the password. We have nailed the problem down to the following statement:

If the password contains the string "}´" (without the quotes; that is, a closing curly brace followed by a forward tick), the ODBC connector can't connect to the respective server.

The mysql client program can connect, though, as well as various custom programs. That means that the ODBC x64 connector is faulty.

How can we work around that problem?

Thank you very much in advance!

----------
Steps to reproduce:

- Set up MySQL server 5.7.34 on a Linux machine (but I guess any other 5.7 version shows the same behavior).
- Create a database and a user who has access to that database.
- Assign the following password to the user (without the quotes): "}´"
- Let the user be identified with sha256_password.

- Install MySQL ODBC connector 8.00.28.0 64-bit on Windows 10 64 bit.
- Create a system DSN which connects to the server and the database created above, using the credentials of the user created above.
- Notably, enter "}´" (without the quotes) into the password field.
- Click "Test".

After clicking "Test", an error dialog appears, stating: "Invalid connection string attribute".

Note that it even doesn't say "Access denied". Obviously, it even doesn't get to the point where access is verified; it seems to give up before that point.
↧

MySQL ODBC DSN (no replies)

April 4, 2022, 8:49 am
↧
Viewing all 1136 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>