Forum Discussion

PauSempere's avatar
PauSempere
New Member
10 years ago
Solved

Error 400 Bad Request when publishing a PBIX file

Hi folks, 

 

using the last versions of Power BI and Enterprise Gateway I am trying to publish a PBIX file connecting to a on-premises SSAS server, but I am getting an Error 400 (Bad Request) when doing so. In the detailed error description I found this error

 

HttpStatusCode
BadRequest

ErrorDetails
{"error":{"code":"ModelHasNoPowerBIDMMoniker","pbi.error":{"code":"ModelHasNoPowerBIDMMoniker","parameters":{},"details":[]}}}

ErrorCode
ModelHasNoPowerBIDMMoniker

 

The gateway works correctly though, and I can see live data from the portal when I upload a new PBIX file with the same SSAS connection and any graph is added. 

 

I have not found any extra info about this error, any ideas about what can it be? 

 

Thank you in advance. 

 

Pau Sempere

  • Anonymous's avatar
    Anonymous
    10 years ago

    PauSempere I don't have any specifics that can directly help, but i've read other threads in which something in the PBIX file corrupted and creating a copy (save as) to a new PBIX file resolved some internal error in the model. You could give that a shot, and see if the same error occures when uploading the new file. If you are having success connecting to the same datasource, I would assume it has something to do with the PBIX file itself.

3 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    PauSempere I don't have any specifics that can directly help, but i've read other threads in which something in the PBIX file corrupted and creating a copy (save as) to a new PBIX file resolved some internal error in the model. You could give that a shot, and see if the same error occures when uploading the new file. If you are having success connecting to the same datasource, I would assume it has something to do with the PBIX file itself.

    • PauSempere's avatar
      PauSempere
      New Member

      Hi Anonymous, 

      I first tried copying the file and renaming it and it didn't work, but using "Save as" it solved the inner problem with the file and I was able to publish it with no problem. 

       

      Thank you!

       

      Regards.

      • Johanno's avatar
        Johanno
        Icon for Continued Contributor rankContinued Contributor

        Thank you! I removed the dataset without removing the reports first and then I got this error.

         

        An easy Save as solved the problem.