none
SSRS 2016 Mobile Reports won't render on mobile device RRS feed

  • Question

  • SQL 2016 RTM

    SQL 2016 RTM

    SQL2016 RTM

    SQL 2016 RTM

    Mobile Report Builder 1.0.3836.0

    I'm working on a proof of concept for a few different clients using the Mobile BI reporting capabilities in SSRS 2016. The reports run and work correctly inside of SSRS running on a desktop system. I'm trying to access the reports through the power BI app with direct connection to the SSRS server on the demo server. I'm able to connect to the SSRS server, get a list of the reports on and attempt to run them.  I have one mobile report that is just using the same data set and everything runs correctly.  I then create a new report and connect to backend data sources (both SSAS-Tabular and SQL).  The direct connected reports fire up and work correctly on the window browser.  When I attempt to run them on the droid device I get the descriptive error "an error has occurred please try again later".  Review the logs reveals a single error each time that I run the report.  I have turned on basic authentication and can connect to the server (both windows / droid) and see the folders and mobile report lists etc.

    Log error message

    Microsoft.ReportingServices.Portal.WebHost!reportserverwebapp!143!06/29/2016-14:48:13:: e ERROR: [y7vfx59q]: XSRF Failed (NonceCookieNotFound)
    Microsoft.ReportingServices.Portal.WebHost!reportserverwebapp!143!06/29/2016-14:48:13:: i INFO: [y7vfx59q]: 172.40.124.207: POST /api/v1.0/CatalogItems%28d6f021ce-5eb4-41fe-8a4a-1cf96568d014%29/Model.DataSet/Model.GetData - Response 403 - 0:00:00.0008755

    Is there a configuration setting somewhere that I'm missing?

    Wednesday, June 29, 2016 7:10 PM

Answers

  • There seems to be some type of name resolution problem.  Changing to the IP address of the server corrected the issue.  I'm working with my internal IT to figure out the issue there.  Just wish the error message gave a little more to go from.
    • Marked as answer by MarkLoew Wednesday, July 6, 2016 7:59 PM
    Wednesday, July 6, 2016 7:59 PM

All replies

  • Hi MarkLoew,

    Thank you for your question.  

    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.  

    Thank you for your understanding and support. 

    Thanks,   

    Xi Jin.

    Monday, July 4, 2016 1:22 AM
    Moderator
  • There seems to be some type of name resolution problem.  Changing to the IP address of the server corrected the issue.  I'm working with my internal IT to figure out the issue there.  Just wish the error message gave a little more to go from.
    • Marked as answer by MarkLoew Wednesday, July 6, 2016 7:59 PM
    Wednesday, July 6, 2016 7:59 PM
  • Hi Mark,

    We will take this into consideration and make improvements in SSRS 2016. Thanks for you feedback.

    Thursday, July 21, 2016 2:27 AM