Forum Discussion

MichBDO's avatar
MichBDO
Frequent Visitor
3 years ago

Publishing error: unknown error for a pipeline

I created a pipeline which includes a single copy data activity.

The source in the copy activity points to a XLSX file in a lakehouse file folder. The destination points to a new table in the lakehouse named 'SourceCSV' (yet to be created through this copy activity).

When trying to save I got the error:

Publishing error: {"code":UnknownError","pbi.error":{"code":{UnknownError"}}

I cannot find the exact cause of this error. 

7 Replies

  • Hi, in pipeline case, you have to take care of import scheme option, there you need to map the column names and data types, then you will get succeeded output.

     

     

    If I answer your question, please mark it as solution.

    • MichBDO's avatar
      MichBDO
      Frequent Visitor

      The error in that post is the same but the solution is not applicable to my case. I'm not using parameterization in my table name. And I have also tried changing the destination from table to file which still gives the same error so it is not the same problem.

      • ajarora's avatar
        ajarora
        Icon for Microsoft Employee rankMicrosoft Employee

        Thanks for confirming. Can you log a support ticket with enough details ? If not, can you share your workspace id and a rough timestamp when this happened ?

  • MichBDO's avatar
    MichBDO
    Frequent Visitor

    Hi Sudhav, thank you for responding.

    The file was too big to import a schema so I first imported the file with just the headers and then changed the source back to my large excel file.

    I still get the same error as I did the before.

  • MichBDO's avatar
    MichBDO
    Frequent Visitor

    The 'Unkown error' is now replaced by a 'RequestValidationFailed' error.
    I have tried replacing the xlsx file with a csv file with the same data. Here it does work. Therefore I'm a bit confused as to why this error only shows for an xlsx file. Maybe due to an encryption on the excel file? Although I didn't encrypt it and it also doesn't show any encryption.