Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago
Solved

Can't upload report to report server (January 2021)

Hi,

 

I'm having some issues uploading Power BI reports to Report Server. I get errors both when Saving As and when uploading from within Power BI itself.

 

The errors I'm receiving are, respectively:

 

  • Upload via Report Server: "There was an error uploading your .pbix file. Verify that the file has not been corrupted and that the file extension matches the format of the file."
  • Save As via PBI Desktop: "An error occurred while attempting to save the report to Power BI Report Server"

The versions I'm using are: january 2021 (server and client)

 

any idea ? nothing appear on log except error 400 bad request.

thanks in advance.
regards

 

PBIX Reports
Publish
  • Anonymous's avatar
    Anonymous
    5 years ago

    Dear Benjamin

    finally, on our prod server, all has been resolved with new January release.
    hope it will be the case for you also.

     

21 Replies

    • Anonymous's avatar
      Anonymous
      Not applicable
      5 years ago

      Hello Ahmed,

      thanks for reply. Yes, I see the post, and we will check for proposed solution (delete database ??? not sure this is a good idea, but why not). Moreover, we upgrade the report server from october 2020, and we were able to upload report...

       

  • josef78's avatar
    josef78
    Icon for Memorable Member rankMemorable Member
    5 years ago

    Which version you are using, new build from January 8th or new version from January 21th?

    Please check id your server version is 1.10.7698.27886, and Desktop version is 2.88.1382.0 exactly.

     

    Is this issue present in any case (including clean created pbix), or only for some specific files?

     

    • Anonymous's avatar
      Anonymous
      Not applicable
      5 years ago

      Hello Josef

      yes, version are 1.10.7698.27886 (server) and Desktop version is 2.88.1382.0 exactly. This occurs for all pbix, and also the newly created.

       

      on the rspowerbi log files, we have something like this when trying to upload / publish report:

      2021-02-03 13:56:15.8762|INFO|4|Received request POST /api/reportproperties| RequestID = s_ae385ca0-4cfb-40c2-beee-2295067bda29
      2021-02-03 13:56:15.8762|ERROR|4|HttpRequestContext returned false for IsLocal.| RequestID = s_ae385ca0-4cfb-40c2-beee-2295067bda29
      2021-02-03 13:56:15.8762|INFO|4|Sending response. Response code loginusername 400, Elapsed time 0:00:00,0011676| RequestID = s_ae385ca0-4cfb-40c2-beee-2295067bda29

      • josef78's avatar
        josef78
        Icon for Memorable Member rankMemorable Member
        5 years ago

        I don't have any idea,... but it can be related to authorisation (maybe between RSPortal and RSPowerBI). You are using ntlm or kerberos authorisation?

        Also try check setting in report server configuration manager, specialy Web Service URL and Web Portal URL (there must be defined indentical servers and protocols (http vs https, and using hostname vs fqdn). 

        Also check RSPortal logs (there must be related entries).

  • Petebro's avatar
    Petebro
    Icon for Microsoft Employee rankMicrosoft Employee
    5 years ago

    Are you still having issues uploading/publishing reports to your server? This is not widely reported but I'm wondering if there is a smaller issue hiding with specifics features/data source types.

     

    -Pete

    • Anonymous's avatar
      Anonymous
      Not applicable
      5 years ago

      Dear Pete,

      yes, we still have issue. It concerns dev server, but for other issue on prod server, we should soon update also prod server to this version, hopping we could be able to still upload / publish power bi report

      • Petebro's avatar
        Petebro
        Icon for Microsoft Employee rankMicrosoft Employee
        5 years ago

        Is it every PBIX or specific ones with types of datasources/features?

    • Benjamin_P's avatar
      Benjamin_P
      Frequent Visitor
      5 years ago

      Hello Pete

       

      I have the same Problem with my Production Report Server. I first tried the new Update on our Test Server, all seems to work there. 

      I also tried to download an existing Power BI report from the server and upload it unchanged to a new location, but i get the same Error as described by Cascador84.

      We have Power BI Desktop Version 2.88.1382.0 32-bit (Januar 2021) and Report Server Version: 1.10.7698.27886 (Januar 2021)

       

      regards

      Benjamin

      • Anonymous's avatar
        Anonymous
        Not applicable
        5 years ago

        Dear Benjamin

        finally, on our prod server, all has been resolved with new January release.
        hope it will be the case for you also.

         

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    I will upload after save file. pbix in my computer. 

    after that upload again.

  • Anonymous's avatar
    Anonymous
    Not applicable
    4 years ago

    Hi I have same issue with power bi report server

    My report server version is 1.12.7936.39665(September 2021)
    Power bi desktop version is
    2.97.2222.0 (September 2021)

    Unable to upload report to server as I'm getting error

     

     

     

     

     

     

    • chrisvandijk's avatar
      chrisvandijk
      New Member
      2 years ago

      I had a simmilar issue, but revoled it partially it seemed to work over http, but somehow a self signed cert from our DC and enabling https on the webportal link broke the capablilty to upload. hope this helps somebody

  • Anonymous's avatar
    Anonymous
    Not applicable
    3 years ago

    I am facing the similar issue.
    Earlier when I was trying in a version prior to september 2022, it was showing error for many to many join is not supported. Then as when I had changed the join to one to many, it was showing me file corrupt error, but now i was using september 2022 version.
    after all the tries, I again trid my old file with many to many join but that somehow worked.
    Not sure where the error was..