web portal
8 TopicsSlow On-Premise Report Server Performance /powerbi/api/explore/reports/.../querydata
I am experiencing some slowness on only the Web portal of our Power BI Reports Server (on-premise) install. May 2022 version deployed. The desktop client is not affected. It is only the web portal that is slow. I am testing with a tinny report. One tab, 2 visuals, one data table with fewer than 100 records and around 20 columns. Should be fast and is fast in the desktop. All reports on the server are similar, but I will focus on this small report to isolate the issue. The report loads slowly, usually 40 seconds before you can interact with it. But it might be better to focus on the slow interactions. If I click a line item in one visual, it takes an average of 5 seconds to filter the other visual. Using the network monitor I can see that it is a call to https://[FQDN]/powerbi/api/explore/reports/[Report GUI]/querydata that is taking all of time. I have seen similar posts to the "me" endpoint taking a lot of time but that is not our issue. Running a browser on the server where PBI SSRS service is installed, using a “localhost” URL, has the same issue, so I don’t think this is a network issue between the browser and PBI server. I don't believe at this point it should be contacting the SQL server, but someone correct me if that is in error. Could anyone point me in a direction to start looking into this?Solved7KViews0likes5CommentsDeprecated REST API request slows down the portal drastically
Hello, I have a problem on my portal with the API request `/api/v.2.0/me`. I'm running my report server locally, and my portal is super slow (12 seconds for each page) I looked at the network, and the request for catalog items is done instantly. Then I discovered that SSRS is doing the /me request to see what my role is after giving me that data... The me request was the catalog items from showing. Also it says in the cookies that this request is deprecated. Is there/will there be a fix for this ? Thank you,Solved1.5KViews0likes2CommentsUser Specific Reports
Hi there I do have a single report that can be fitted per location, we do have around 15 locations. So to share same report por each specific user y had to change values in a table in order to share to specific user only specific data, and 15 reports published I'm wondering if I can have just 1 single report shared, setup user and locations and present only the specific information to the specific user.Solved2.7KViews0likes4CommentsProblem with display of large Reports on March 2018
We have updated to March 2018 release last weekend. Everything seems to work fine, but we have a very odd job stopper. We have reports with large datasets, where users show up a report and then download it in Excel. The Report viewer is not working any more, it crashes after several seconds of loading. I checked the logs on the server without any error messages, executionlog shows the same for the report server the report was rendered sucessful, but for the user there is nothing. I hunted down the whole in the browser and found an error message after some waiting: Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=Microsoft.ReportingServices.Rendering.HtmlRenderer.RendererResources.jquery.min.js:2 Uncaught RangeError: Maximum call stack size exceeded at r.fn.init.push (<anonymous>) at Function.ga [as find] (Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=Microsoft.ReportingServices.Rendering.HtmlRenderer.RendererResources.jquery.min.js:2) at r.fn.init.find (Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=Microsoft.ReportingServices.Rendering.HtmlRenderer.RendererResources.jquery.min.js:2) at new r.fn.init (Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=Microsoft.ReportingServices.Rendering.HtmlRenderer.RendererResources.jquery.min.js:2) at r (Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=Microsoft.ReportingServices.Rendering.HtmlRenderer.RendererResources.jquery.min.js:2) at ResizeTablixRows (Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=Microsoft.ReportingServices.Rendering.HtmlRenderer.RendererResources.Html5Renderer.js:1) at PostRenderActions (Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=Microsoft.ReportingServices.Rendering.HtmlRenderer.RendererResources.Html5Renderer.js:1) at Microsoft.Reporting.WebFormsClient._ReportPage.OnReportVisible (Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=ViewerScript:1) at Microsoft.Reporting.WebFormsClient._ReportArea.MakeReportVisible (Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=ViewerScript:1) at Microsoft.Reporting.WebFormsClient._ReportArea.OnReportPageLoaded (Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=ViewerScript:1) ga @ Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=Microsoft.ReportingServices.Rendering.HtmlRenderer.RendererResources.jquery.min.js:2 find @ Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=Microsoft.ReportingServices.Rendering.HtmlRenderer.RendererResources.jquery.min.js:2 r.fn.init @ Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=Microsoft.ReportingServices.Rendering.HtmlRenderer.RendererResources.jquery.min.js:2 r @ Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=Microsoft.ReportingServices.Rendering.HtmlRenderer.RendererResources.jquery.min.js:2 ResizeTablixRows @ Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=Microsoft.ReportingServices.Rendering.HtmlRenderer.RendererResources.Html5Renderer.js:1 PostRenderActions @ Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=Microsoft.ReportingServices.Rendering.HtmlRenderer.RendererResources.Html5Renderer.js:1 OnReportVisible @ Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=ViewerScript:1 MakeReportVisible @ Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=ViewerScript:1 OnReportPageLoaded @ Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=15.0.2.402&Name=ViewerScript:1 Anyone out there experiencing the same problem and has a solution for me, how to solve it? We use the report daily and it worked sucessfully until the update. Thanks for your help, best regards, Thomas843Views0likes0CommentsCan not see the Report Server Web Portal
Hi, I've already installed SQL Server 2017, SQL Server Analysis Services, Power BI Desktop (report server edition) and Power BI Report Server.exe to my new server. When I try to reach the web portal below, I reached the page of SQL Server Reporting Services instead of Power BI Report Server. What else do I have to do to see the Power BI Report Server web portal? http://servername/ReportsSolved29KViews0likes6CommentsStoring data and visualization in a cloud and access them without a VPN Connection
Hello, is it possible to make my data, which are stored in a cloud (with a win server), accessible to the outside thgrough the report server? I would like to access my dashboard without a VPN Connection and just to type the website address via a webbrowser and see my dashboard. Is this possible? In case it works, is it just possible to see the dashboard with a user licence? Do I need for this Idea Power BI Premium? (to embed the dashboard) best regards842Views0likes0CommentsReporting Services Error about version of the report server database
Hi all, After I install report server, start service and connect to SQL server success. But when i access to web portal, I received an error: Reporting Services Error The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is '2017'. The expected version is '162'. (rsInvalidReportServerDatabase) Get Online Help SQL Server Reporting Services I don't know why. I install Report Server in Windows Server 2012 and Config to SQL Server 2012. Thanks for your help!Solved16KViews0likes2Comments