MySQL Bugs: #65939: Names piped error 40. Crash SQL Server 2012 Service with linked server

Bug #65939	Names piped error 40. Crash SQL Server 2012 Service with linked server
Submitted:	18 Jul 2012 14:27	Modified:	20 Jul 2012 12:09
Reporter:	Bruno BARON	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	5.1.11	OS:	Any
Assigned to:	Bogdan Degtyariov	CPU Architecture:	Any
Tags:	Linked;sql server 2012, regression

Description:
Names piped error 40. Crash SQL Server Service

No problem with 5.1.5 odc on the same server. Not tested the intermediat versions

How to repeat:
Try to install linked server with odbc 5.1.11

Bruno,

Can you please be more specific, when exactly does the crash occur?
Is it crashing when you create the linked server or when you try to run a query?

Hello,
The sql server Service crash with error 40 when the linked server attempt to connect at the MySQL Database
Regards

Hello,
The sql server Service crash with error 40 when the linked server attempt to connect at the MySQL Database
Regards

Thanks for your reply.
This problem might be related to the crash bug report 65200, which caused
MySQL ODBC Driver 5.1.11 to crash over table names that have 15 symbols 
or more.

Can you connect to MySQL server using the mysql command line and
send me the list of table names there (replace my_database_name with
the real name of your database)?

mysql> use my_database_name;
mysql> SHOW TABLES;

Hello,
Here is the list of tables:
AddressBook
AddressBookEmail
AddressBookFAX
BarcodeRoute
CoverPages
DIDRoute
DistroList
DynConf
FaxArchive
FaxCategory
Modems
SysLog
UserAccount
UserPasswords
agent_stats
astdb
asterisk_extensions
asterisk_extensions_seq
asterisk_fax
asterisk_hotel
asterisk_voicemail
cdr
cdr_2009_02
cdr_2009_03
cdr_2009_04
cdr_2009_05
cdr_2009_06
cdr_2009_07
cdr_2009_08
cdr_2009_09
cdr_2009_10
cdr_2009_11
cdr_2009_12
cdr_2010_01
cdr_2010_02
cdr_2010_03
cdr_2010_04
cdr_2010_05
cdr_2010_06
cdr_2010_07
cdr_2010_08
cdr_2010_09
cdr_2010_10
cdr_2010_11
cdr_2010_12
cdr_2011_01
cdr_2011_02
cdr_2011_03
cdr_2011_04
cdr_2011_05
cdr_2011_06
cdr_2011_07
cdr_2011_08
cdr_2011_09
cdr_2011_10
cdr_2011_11
cdr_2011_12
cdr_2012_01
cdr_2012_02
cdr_2012_03
cdr_2012_04
cdr_2012_05
cdr_2012_06
cdr_index
cdr_pre
cel
horde_datatree
horde_datatree_attributes
horde_datatree_seq
horde_histories
horde_histories_seq
horde_locks
horde_log
horde_prefs
horde_sessionhandler
horde_tokens
horde_users
horde_vfs
ivr
ivr_2009_07
ivr_2009_09
ivr_2009_10
ivr_2009_11
ivr_2009_12
ivr_2010_01
ivr_2010_02
ivr_2010_03
ivr_2010_04
ivr_2010_05
ivr_2010_06
ivr_2010_07
ivr_2010_08
ivr_2010_09
ivr_2010_10
ivr_2010_11
ivr_2010_12
ivr_2011_01
ivr_2011_02
ivr_2011_03
ivr_2011_04
ivr_2011_05
ivr_2011_06
ivr_2011_07
ivr_2011_08
ivr_2011_09
ivr_2011_10
ivr_2011_11
ivr_2011_12
ivr_2012_01
ivr_2012_02
ivr_2012_03
ivr_2012_04
ivr_2012_05
ivr_2012_06
ivr_index
network_dhcpd_static
network_firewall
network_firewall_forwarding
network_firewall_services
network_ipaddr
nic_data
nic_network
nic_status
phones_history
queue_agent_stats
queue_cdr
queue_cdr_2009_02
queue_cdr_2009_03
queue_cdr_2009_04
queue_cdr_2009_05
queue_cdr_2009_06
queue_cdr_2009_07
queue_cdr_2009_08
queue_cdr_2009_09
queue_cdr_2009_10
queue_cdr_2009_11
queue_cdr_2009_12
queue_cdr_2010_01
queue_cdr_2010_02
queue_cdr_2010_03
queue_cdr_2010_04
queue_cdr_2010_05
queue_cdr_2010_06
queue_cdr_2010_07
queue_cdr_2010_08
queue_cdr_2010_09
queue_cdr_2010_10
queue_cdr_2010_11
queue_cdr_2010_12
queue_cdr_2011_01
queue_cdr_2011_02
queue_cdr_2011_03
queue_cdr_2011_04
queue_cdr_2011_05
queue_cdr_2011_06
queue_cdr_2011_07
queue_cdr_2011_08
queue_cdr_2011_09
queue_cdr_2011_10
queue_cdr_2011_11
queue_cdr_2011_12
queue_cdr_2012_01
queue_cdr_2012_02
queue_cdr_2012_03
queue_cdr_2012_04
queue_cdr_2012_05
queue_cdr_2012_06
queue_cdr_index
queue_log
queue_log_2011_01
queue_log_2011_02
queue_log_2011_03
queue_log_2011_04
queue_log_2011_05
queue_log_2011_06
queue_log_2011_07
queue_log_2011_08
queue_log_2011_09
queue_log_2011_10
queue_log_2011_11
queue_log_2011_12
queue_log_2012_01
queue_log_2012_02
queue_log_2012_03
queue_log_2012_04
queue_log_2012_05
queue_log_2012_06
queue_log_index
queue_stats
queue_stats_agent
rt_agents
rt_asterisk_events
rt_calls_holdtime
rt_channels
rt_contexts
rt_cos
rt_custom_apps
rt_dahdi
rt_dahdi_groups
rt_data
rt_directories
rt_features_codes
rt_filesystems
rt_hotdesks
rt_meetme_rooms
rt_meetme_users
rt_network_dhcp
rt_network_intfs
rt_online
rt_parklots
rt_peers
rt_perms
rt_phones
rt_queues
rt_queues_agents
rt_queues_asterisk
rt_queues_callers
rt_queues_members
rt_queues_members_stats
rt_queues_stats
rt_speeddials
rt_sys_fans
rt_sys_memory
rt_sys_processes
rt_sys_temp
rt_sys_voltage
rt_tenants
rt_voicemails
rt_voipaccounts
scopserv_attributes
scopserv_config
scopserv_data
scopserv_data_seq
server_backup
server_backup_history
server_monitor_history
server_update_history
tagcode

Regards

Thanks.

I see the table with 27 symbols: network_firewall_forwarding
It could crash the driver.
This report is a duplicate of bug #65200.
I would recommend using 5.1.10 till the new version 5.1.12 is released.

If you create a small database for testing and a few tables with short names in it (such as tab1, tab2, tabN...) the MSSQL Linked Server will not crash. This means that the problem is really in SQLTables ODBC function and downgrading to 5.1.10 will help.

ok. Thank You.

Hello,
I don't find the version 5.1.10 for download on your site ...
Can youd give me the uri please ...
Regards