Bug #76926 | Access to MySQL migration results in unknown attribute ‘getOS’ | ||
---|---|---|---|
Submitted: | 4 May 2015 10:39 | Modified: | 18 May 2015 23:03 |
Reporter: | Salih Yasin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Migration | Severity: | S2 (Serious) |
Version: | 6.3 | OS: | Windows (7 PRO 64bit) |
Assigned to: | CPU Architecture: | Any | |
Tags: | access, getOS, migration |
[4 May 2015 10:39]
Salih Yasin
[4 May 2015 12:52]
Milosz Bodzek
Thank you for your bug report.
[5 May 2015 3:08]
David Bubnoski
Have the same problem with the same symptoms on Windows 8.1 using MySQL Workbench 6.3 32-bit version. SCHEMA is successfully migrated, but data is not.
[10 May 2015 18:59]
Roger Goetzendorff
Same for me. MySQL Workbench 6.3 CE, WIN 7 pro 64bit, Access 2010 64bit. Not only no data is migrated; also the copymigrateddata script is not generated.
[10 May 2015 19:02]
Roger Goetzendorff
... worked before switching to MýSQL Workbench+Office 2010 to 64 bit. 32bit all was OK.
[18 May 2015 23:03]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Workbench 6.3.4 release, and here's the changelog entry: When migrating from Microsoft Access, the "Data Transfer Setup" step would fail and throw the following exception: "Error - Unhandled exception: unknown attribute 'getOS'". In other words, the tables were created but the data was not migrated to MySQL. Thank you for the bug report.
[21 May 2015 15:08]
Ochbayar Jargal
have exact same problem with win 7 Ent ver.6.1 and Office 2010 32 bit ver.14.0.7. so when would be next release?
[29 May 2015 17:10]
Nick Bowen
I was experiencing this bug as well migrating from Access 2010 32 bit to MySQL Workbench 6.3.3 32 bit. The only way I was able to work around it was to uninstall Workbench and reinstall an older version. Using 6.2.4 I was successfully able to perform data transfer and complete migration.
[22 Jun 2015 19:39]
Padmahas B N
I was experiencing the same problem here, but I upgraded to workbench 6.3.4 32 bit and the problem was gone.