Bug #98404 MYSQL not avalable on Excel 365 ribbon
Submitted: 26 Jan 2020 9:50 Modified: 26 Jan 2020 22:11
Reporter: Bill Hildyard Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL for Windows: MySQL for Excel Severity:S3 (Non-critical)
Version:1.3.8 OS:Windows (10)
Assigned to: CPU Architecture:x86

[26 Jan 2020 9:50] Bill Hildyard 
Description:
Went though the process of installation using the installer all went well till it would recognise Studio Visual installation, Googled that issue which advised to install MYSQL for visual Studio 1.2.9, then installed MySQl for Excel 1.3.8. Which install in shows in add/remove, it shows in the list of COM Add-ins, but is not showing on the Excel ribbon, re-installation made no difference.

How to repeat:
Install Mysql installer, install MYSQL for visual Studio 1.2.9, install MySQl for Excel 1.3.8
[26 Jan 2020 22:09] MySQL Verification Team 
MySQL For Excel 365

Attachment: 98404.png (image/png, text), 40.65 KiB.
[26 Jan 2020 22:11] MySQL Verification Team 
Thank you for the bug report. See attached screenshot.
[26 Jan 2020 22:15] MySQL Verification Team 
Installed 1.3.8

Attachment: 98404_1.png (image/png, text), 10.04 KiB.
[18 Apr 2021 10:20] Andrea Clementi 
Same problem here.
The plugin worked for some time, then crashed and since that moment it disappeard from the ribbon, and is marked as disable in Excel->Options->Addins.
I tried to clean everything (remove the plugin from Excel, uninstall MySql for Excel from Windows, and also clean every remaining key inside the registry, and then reinstall (I tried many time in different combinations) but the plugin won't come back.
My computer has Windows 10 20H2 with Excel 2013 (build 13901.202336)

In a similar computer MySql For Excel works perfectly. The only difference to me is that in the computer where the plugin is not working it crashed once (and since the crashed it stop working)  while in the second computer it never crashed.

Inside Excel options, the plugin is listed as a COM plugin in both computer, so this is not a problem as reported in different bug and also in the official plugin FAQ by Oracle.

Any suggestion to have the plugin working again is appreciated.
Thank you