Forum Discussion

GuillaumeBer's avatar
GuillaumeBer
Advocate I
3 years ago
Solved

Unable to Publish Pipeline : {"code":UnknownError","pbi.error":{"code":{UnknownError"}}

I created my first Fabric Data Factory pipeline (from data copy wizard) and when I tried to save and run it,  I got the following error message :

Request failed with 500(Internal Server Error): {"error":{"code":"UnknownError","pbi.error":{"code":"UnknownError"}}}, requestid: 79d3e74a-a71f-bf73-d32c-345e4b6a0695"


see ID#2306050050002903

  • GraceGu's avatar
    GraceGu
    3 years ago

    Yes, it is a bug - Table action parameterization causes the error. Bug is tracked internally. 

     

  • Fix is in rollout. Tentive ETA to be available for all regions is mid Jul. 

12 Replies

  • SamWilliams's avatar
    SamWilliams
    Regular Visitor

    I'm getting a similar error when publishing a dataflow gen2:

     

    ---------- Message ----------

    Unhandled HTTP Request Exception. Status Code: 500. Reason: undefined. Response Text: {"error":{"code":999999,"message":"Something went wrong, please try again later. If the error persists, please contact support.","details":null}}.

     

    ---------- Stack ----------

    ApiResponseError: Unhandled HTTP Request Exception. Status Code: 500. Reason: undefined. Response Text: {"error":{"code":999999,"message":"Something went wrong, please try again later. If the error persists, please contact support.","details":null}}.

        at Bt.handleLoadEvent (https://us.prod.powerquery.microsoft.com/DataflowsApp/scripts/app.a596db03743bdca27024.bundle.js:2:96923)

        at XMLHttpRequest.<anonymous> (https://us.prod.powerquery.microsoft.com/DataflowsApp/scripts/app.a596db03743bdca27024.bundle.js:2:97966)

     

    ---------- Session ID ----------

    da688575-994f-4418-8bd8-d3fb04446690

     

    Was working Friday, so I expect there is a service issue.

      • GraceGu's avatar
        GraceGu
        Microsoft Employee

        I can repro this.

        It is likely caused by: inside copy activity, generated parameterization does not work. 

         

        Work-around: Remove the paraterization, manually set this table action, then save. 

         

         

    • Jotheesh's avatar
      Jotheesh
      Frequent Visitor

      I am seeing similar issue and it's consistent

  • ajarora's avatar
    ajarora
    Microsoft Employee

    The above mentioned bug on pipelines will not impact dataflows, please start a separate thread for it.

  • MichBDO's avatar
    MichBDO
    Frequent Visitor

    I also get this error although I have the Table action on 'Append'. My source is a single XLSX file in a file folder in the lakehouse and the destination is a table in the lakehouse. What could be the cause of this?