may 2022 update
3 TopicsMatrix Table format error in Power BI server after May 2024 update
Hi Community, I am having issues on the Matrix Table format after updating to May 2024. I have tons of reports with the matrix table format, and after updating the report in May 2024 Server, the Matrix table's format is distorted. The "Stepped layout" was replaced in the new update. I tried to use the Tabular format, but problem still exists. Need your help please. See below snipshot. Thank you for your help.Solved1.4KViews0likes3CommentsThe server is unavailable when publishing reports from non-domain devices (Report Server May 2022)
Good day! Friends, our development team installed a Report Server update in early June 2022 (May 2022). As a result, the publication of reports from devices that are not the company's domain devices stopped working. That is, from a working device in the domain, the Report Server is visible and publication occurs, and if you do this from a home PC that is not in the domain, we get the error "The Server is unavailable". Earlier in the January update of the Report Server, there were no problems with this. Tell me, please, what could be the problem? where to dig? The company's infrastructure has not changed in any way, the problem is precisely in the update. I attach a picture (error). Thanks @Petebro, @PBIRS, @ReportServer771Views0likes2CommentsBug in CommentBelongsToUser stored procedure ReportServer database
Have May 2022 installed using custom authentication, user can create comments but then if they try to delete a comment, error pops up stating An error has occurred. An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. When reviewing RSPortal log file it adds in System.Data.SqlClient.SqlException: Procedure or function 'CommentBelongsToUser' expects parameter '@UserSid', which was not supplied. Since this is custom authentication their is no @UserSid. If I modify stored procedure to set a default of NULL to the @UserSid parameter the issue is resolved, though this will likely get ovewrote on any SQL Server or Report Server patching. Would think this should be addressed1.1KViews0likes3Comments