Forum Discussion

mkbytes's avatar
mkbytes
Regular Visitor
5 years ago

Cannot Publish a Pbix file

Hello, We are running October 2020 version of PBI report server on prem. Paginated reports are currently in use, but we cannot upload a pbix report. I'm currently using the matching PBI desktop vers...
Report Server On premises
Petebro's avatar
Petebro
Icon for Microsoft Employee rankMicrosoft Employee
5 years ago

Hi,

 

I'm trying to reproduce either issue and am unable to get an error publishing my report to the local reportserver with either the 64 or 32 bit version of desktop. Can you post the version of Power BI Desktop for Report Server you are using?

 

This is the expected version:

  • Version: 2.86.961.0 32-bit (October 2020)
  • Version: 2.86.961.0 64-bit (October 2020)

 

-Pete

Anonymous's avatar
Anonymous
Not applicable
5 years ago

Desktop Version: 2.86.961.0 64-bit (oktober 2020)

Server Version 1.9.7604.41261 (October 2020)

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

    Could you look at the PBIDesktop*.log file for any error messages?

    To get to the log go to the options dialog, then the diagnostics tab. There is a link to the traces folder there.

     

    I'm still unable to reproduce this with the same versions (and even got a localized version of desktop thinking maybe it was related to that).

    • Anonymous's avatar
      Anonymous
      Not applicable
      5 years ago

      I think i found something related to the error in the log file:

       

      DataMashup.Trace Warning: 24579 : {"Start":"2020-11-03T17:57:53.4940584Z","Action":"PBI.PQ.SaveDiscardInternal","actionId":"SaveDocumentInternal","entryPoint":"EditorRibbonButtonPowerBISharePublish","errorCode":"ServerNotReachable","message":" at Microsoft.PowerBI.Client.Windows.SSRSService.SSRSPbixFile.<Save>d__28.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.PowerBI.Client.Windows.Services.FileManager.<CopyTempToFile>d__33.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.PowerBI.Client.Windows.Services.FileManager.<TrySaveBIPackage>d__28.MoveNext()","wasRetried":"False","retryReason":"","parentId":"3e812f42-1646-402f-8a7d-0a0917f1849d","isError":"True","sessionId":"799ac05d-4377-4271-ac85-ed4a70c77d39","deviceId":"9ba80868","userId":"a657900e-f028-4bd5-8356-fbbdf604c574","isInternal":"False","authenticatedUserId":"Unknown","ProductVersion":"2.86.961.0 (20.10)","ActivityId":"2296ae04-f5e4-43af-ade5-de2d7aec9ab2","Process":"PBIDesktop","Pid":116108,"Tid":1,"Duration":"-00:00:00.0002562"}
      • Anonymous's avatar
        Anonymous
        Not applicable
        5 years ago

        Maybe this can be of help as well. These lines are just above the previous line:

         

        DataMashup.Trace Information: 24579 : {"Start":"2020-11-03T17:57:53.2410690Z","Action":"JsonSerializer/TryDeserialize","Result":true,"ProductVersion":"2.86.961.0 (20.10)","ActivityId":"00000000-0000-0000-0000-000000000000","Process":"PBIDesktop","Pid":116108,"Tid":1,"Duration":"00:00:00.0001546"}
        DataMashup.Trace Information: 24579 : {"Start":"2020-11-03T17:57:53.3424864Z","Action":"JsonSerializer/TryDeserialize","Result":true,"ProductVersion":"2.86.961.0 (20.10)","ActivityId":"00000000-0000-0000-0000-000000000000","Process":"PBIDesktop","Pid":116108,"Tid":1,"Duration":"00:00:00.0002794"}
        DataMashup.Trace Warning: 24579 : {"Start":"2020-11-03T17:57:52.9604204Z","Action":"PBI.Win.SaveReportToSSRS","result":"ServerNotReachable","parentId":"3e812f42-1646-402f-8a7d-0a0917f1849d","isError":"True","sessionId":"799ac05d-4377-4271-ac85-ed4a70c77d39","deviceId":"9ba80868","userId":"a657900e-f028-4bd5-8356-fbbdf604c574","isInternal":"False","authenticatedUserId":"Unknown","ProductVersion":"2.86.961.0 (20.10)","ActivityId":"e544a76c-8bef-4b89-9183-c7ed7430ba71","Process":"PBIDesktop","Pid":116108,"Tid":1,"Duration":"00:00:00.5262420"}

        The part where it says  "authenticatedUserId":"Unknown", may have something to do with the error!?

        When I run go to the Report Server web UI I always have to put in my credentials in a basic dialog. I am using the same credentials when publishing the report. But I get the feeling that our report server somehow does not pick up the AD-user when using Google Chrome.