MySQL Forums
Forum List  »  MySQL Workbench

Migrating Data from FileMaker Pro to MySQL
Posted by: Chandni Gorajiya
Date: July 19, 2020 04:26PM

I am trying to migrate FileMaker database into MySQL. For this I have installed FM odbc drivers and also set up a system DSN. This DSN connection was tested successfully.

On Workbench , I have selected database as "Generic RDBMS" and Connecion Method = "ODBC data soure".

When I click on "Test Connection " button it is throwing below error.


Starting...
Connect to source DBMS...
- Connecting to source...
Connecting to ...
Opening ODBC connection to DSN=Assets...
Traceback (most recent call last):
File "C:\Program Files\MySQL\MySQL Workbench 8.0 CE\modules\db_generic_re_grt.py", line 693, in connect
return GenericReverseEngineering.connect(connection, password)
File "C:\Program Files\MySQL\MySQL Workbench 8.0 CE\modules\db_generic_re_grt.py", line 147, in connect
con = db_driver.connect(connection, password)
File "C:\Program Files\MySQL\MySQL Workbench 8.0 CE\workbench\db_driver.py", line 95, in connect
connection = library.connect(connection_string, password=password)
pyodbc.Error: ('28000', '[28000] [FileMaker][FileMaker] User ID must be specified (3069) (SQLDriverConnect); [28000] [FileMaker][FileMaker] User ID must be specified (3069)')

Traceback (most recent call last):
File "C:\Program Files\MySQL\MySQL Workbench 8.0 CE\workbench\wizard_progress_page_widget.py", line 71, in run
self.func()
File "C:\Program Files\MySQL\MySQL Workbench 8.0 CE\modules\migration_source_selection.py", line 456, in task_connect
username = self.main.plan.migrationSource.connection.parameterValues.userName
KeyError: 'grt.Dict key must be a string'
ERROR: Error during Connect to source DBMS: 'grt.Dict key must be a string'
ERROR: Exception in task 'Connect to source DBMS': KeyError('grt.Dict key must be a string',)

Failed

Options: ReplyQuote


Subject
Views
Written By
Posted
Migrating Data from FileMaker Pro to MySQL
1351
July 19, 2020 04:26PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.