Error mirroring tables on Prem SQL to Fabric

[cseajs]

We have 3 different databases on prem that I am trying to mirror to Fabric.  Twenty of the tables sync with no issues but in all 3 instances there are 2 tables ( all the same tables) that are having issues syncing.  It cannot be a data issue since the data is different in all 3 instances but the error makes me think it is a data / database issue.  The error is below.  

We encountered an error while parsing data file being used, please fix the file and try again. The error is: Exception reading the data file. Exception: Index was outside the bounds of the array., ErrorCode: InternalError, ErrorCode: InputValidationError

[v-sdhruv]

Hi @cseajs ,

Just wanted to check if you had the opportunity to review the information provided. 
If you still face any issues feel free to reach out, we would be happy to address your query
Thank you.

[v-sdhruv]

Hi @cseajs ,

Just wanted to check if you had the opportunity to review the information provided. 
If any of the responses has addressed your query, please accept it as a solution  so that other members can fint it easily.
Thank you.

[v-sdhruv]

Hi @cseajs ,

Just wanted to check if you had the opportunity to review the information provided.  If the response has addressed your query, please accept it as a solution  so other members can easily find it.
Thank you.

[v-sdhruv · Accepted solution]

Hi @cseajs ,

The error suggests that the issue is likely related to how the data is being parsed—possibly due to malformed or inconsistent structure in the source files or tables  you can follow the checks suggested by @mabdollahi .

Additonally, you can
1.Try loading the tables manually into OneLake and use the “Load to Table” option to see if the issue reproduces.
2. Enable raw data preview in your pipeline to inspect malformed rows.

Hope this helps!
If the response has addressed your query, please accept it as a solution so other members can easily find it.
Thank you.

[mabdollahi]

Hi @cseajs ,
The issue is likely due to unsupported or mismatched data types in those two specific tables; especially in primary keys or indexed columns. Even though the data is different, the table structure might include types like geometery, hierarchyid, or datetime2(7) that Fabric doesn't support well. Double-check the schema and data types across all three databases for those tables, clean up any null-only columns, and try syncing again.

Regards,
Mehrdad Abdollahi