Forum Discussion

WSS12610's avatar
WSS12610
Copper Contributor
Nov 28, 2022

Invalid or unknown format type 'MISONCSV'. Dynamics F&O Export to Data Lake, CDM Util

To give some context:

We have a data feed out of Microsoft Dynamics F&O, Exporting data tables to our Azure Data Lake Gen 2. This is then picked up by Synapse as tables. I created the tables using the CDM util.

 

This has been working perfect for the last couple of months. As of today all tables are throwing this error:

Invalid or unknown format type 'MISONCSV'.
When I query, i.e 
SELECT * FROM [dbo].[Currency]
 
The table comes from a CSV in the Datalake I tried opening it using OPENROWSET which has the same error.

CSV looks fine to me and lines up with the cdm.json file.

Can't find any mention of this error online so not really sure where to start looking.
 
 
 
 

 


 

  • fentonmFH 

    If you are experiencing the following error message within Synapse Serverless SQL Pool for OPENROWSET(), remove the PARSER_VERSION='2.0' and let Synapse Serverless SQL Pool use the default CSV parser or CSV PARSER_VERSION='1.0' (the only limitation is that you will not be able to use the HEADER_ROW option). This error message is specific to CSV parser version 2.0.

    "Invalid or unknown format type 'MISONCSV'"

    Also, reduce the max VARCHAR / NVARCHAR size to 4000

  • fentonmFH's avatar
    fentonmFH
    Copper Contributor
    I have exactly the same error. My CSV file is a simple save as CSV out of Excel. All my other CSV files work fine.
    • Touhidur_Rahman's avatar
      Touhidur_Rahman
      Copper Contributor

      fentonmFH 

      If you are experiencing the following error message within Synapse Serverless SQL Pool for OPENROWSET(), remove the PARSER_VERSION='2.0' and let Synapse Serverless SQL Pool use the default CSV parser or CSV PARSER_VERSION='1.0' (the only limitation is that you will not be able to use the HEADER_ROW option). This error message is specific to CSV parser version 2.0.

      "Invalid or unknown format type 'MISONCSV'"

      Also, reduce the max VARCHAR / NVARCHAR size to 4000

      • WSS12610's avatar
        WSS12610
        Copper Contributor
        Not sure what happened but this issue somehow fixed itself. I did have a ticket in with Microsoft so maybe they did something.

Resources