MySQL Bugs: #84372: ERROR: Determine number of rows to copy: too many values to unpack

Bug #84372	ERROR: Determine number of rows to copy: too many values to unpack
Submitted:	30 Dec 2016 1:42	Modified:	30 Jan 2017 9:24
Reporter:	Juan Tellez	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Migration	Severity:	S2 (Serious)
Version:	6.3.8	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
Hello, I was working trying to migrate a database from MS SQL Server and it was working well until I got to the step of "Bulk Data Transfer" where I got this log:

Starting...
Prepare information for data copy...
Prepare information for data copy done
Determine number of rows to copy....
Counting number of rows in tables...
wbcopytables.exe --count-only --passwords-from-stdin --odbc-source="DSN=MSSQL;DATABASE=;UID=" --table-file=c:\users\xxxxx\appdata\local\temp\tmpudarwj
--table [C:\USERS\XXXXX\APPDATA\LOCAL\PUNTO DE VENTA\BISUTERIAINVENTARIODB.MDF]	[Bisuteria].[Inventario]
19:32:20 [INF][      copytable]: --table [C:\USERS\XXXXX\APPDATA\LOCAL\PUNTO DE VENTA\BISUTERIAINVENTARIODB.MDF]	[Bisuteria].[Users]
19:32:20 [INF][      copytable]: Opening ODBC connection to [unknown] 'DSN=MSSQL;DATABASE=;UID=;PWD=XXX'
19:32:21 [INF][      copytable]: ODBC connection to 'DSN=MSSQL;DATABASE=;UID=;PWD=' opened

ERROR: Determine number of rows to copy: too many values to unpack
Failed

In the DB I only have a few rows (less than 6 per table, with two tables). Does anyone knows a solution for this?

Thanks,

How to repeat:
Follow Migration Wizard, get to the Bulk Data Transfer Part and wait for the execution.

Suggested fix:
I can only think of a character problem within the data of the tables, but I don't know.

Thank you for the bug report. Please check the integrity of your database (I got an error message when trying to attach it). Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".