topic Re: Power BI Report Server January 2025 bug in Report Server

Power BI Report Server January 2025 bug

TomOm — Mon, 20 Jan 2025 10:44:42 GMT

I installed server January 2025 version. After install publisher role and content manager don't have manage privileges to file.

Re: Power BI Report Server January 2025 bug

mfarhanjamil — Mon, 20 Jan 2025 12:06:35 GMT

After installing Janaury 2025 updates, more info button for reports or folder is giving error "The permissions granted to user 'domain\user' are insufficient for performing this operation.

Re: Power BI Report Server January 2025 bug

Kostya_Rico — Mon, 20 Jan 2025 13:28:07 GMT

The same for us! Even on fresh install.

Re: Power BI Report Server January 2025 bug

Anonymous — Tue, 21 Jan 2025 01:59:18 GMT

Hi,Kostya_Rico and mfarhanjamil .Thank you for your feedback.
Hello,@TomOm .I am glad to help you.
You can try to grant permissions to users.
URL:

reporting services - The permissions granted to user are insufficient for performing this operation (rsAccessDenied) - Stack Overflow

I have noticed that the issues are all occurring after Power BI Report Server has been updated to the January 2025 version. So I can not rule out this as an update issue at this time.
I've checked the relevant report server information, but I'm not aware of any similar known issues at this time
I think you can create a Microsoft Support Ticket to get more help.
This will allow you to get more information about your environment configuration as well as error messages to help quickly determine the cause of the problem.
Thank you for your support of Power BI.
The Link of Power BI Support:

Microsoft Fabric Support and Status | Microsoft Fabric

I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian

Re: Power BI Report Server January 2025 bug

nubeli69 — Tue, 21 Jan 2025 11:45:17 GMT

Same thing here, after instaling January 2025 PBIRS, after click 3 dots raize error "The permissions granted to user 'DOMAN\USER' are insufficient for performing this operation."

Re: Power BI Report Server January 2025 bug

ashamashov — Tue, 21 Jan 2025 12:45:10 GMT

The same error after January 2025 update. I solved this problem by adding the required users or user groups in Site Settings-Security with the System User role. I'm not sure if this is a workaround or a working solution

Re: Power BI Report Server January 2025 bug

d_gosbell — Wed, 22 Jan 2025 03:55:18 GMT

This is the expected behaviour. From the docs: Grant users access to a report server - SQL Server Reporting Services (SSRS) | Microsoft Learn

Re: Power BI Report Server January 2025 bug

Kostya_Rico — Wed, 22 Jan 2025 07:51:26 GMT

Hello! Thanks a lot for clarifying the issue!

But how does it come we've been updating the server for couple of years and such problem popped up only now? I mean our users were granted access on folders and items level, not touching 'system user' server role and this has been working until now.

Re: Power BI Report Server January 2025 bug

TomOm — Wed, 22 Jan 2025 10:42:10 GMT

The documentation has a modification date between May 2024 and January 2025. So maybe the manufacturer has quietly prepared us for this change 😁

Re: Power BI Report Server January 2025 bug

benjaminb — Wed, 22 Jan 2025 19:06:18 GMT

We have released a new build today to address this issue. It can be found here: Download Microsoft Power BI Report Server - January 2025 from Official Microsoft Download Center

Re: Power BI Report Server January 2025 bug

R1k91 — Fri, 24 Jan 2025 10:48:15 GMT

just faced this on 3 servers on our client.

fixed installing Version1.22.9153.7886(January 2025) as suggested by @benjaminb

no need to change any permission.

Re: Power BI Report Server January 2025 bug

nikolailic2 — Fri, 24 Jan 2025 11:04:14 GMT

Tnx for the help, this patch solve our problem.

Re: Power BI Report Server January 2025 bug

TomOm — Sun, 26 Jan 2025 14:16:58 GMT

I confirm, this patch solve our problem

Re: Power BI Report Server January 2025 bug

intgd — Mon, 12 May 2025 13:57:38 GMT

We are still facing problem with DAX Measures visuals on Power BI RS Desktop (32 bit).

It seems MSFT has updated PBI RS (server) but never fixed the PBI RS Desktop (32 bit) .

I have compared (SHA1 hash) the installer exe (PBI RS Desktop 32 bit) , released on Jan 13, 2025 and Jan 22, 2025, both are exact match. This confirms MSFT never fixed the Desktop side of things.

If anyone has seen PBI RS Desktop issue, please comment ?

Re: Power BI Report Server January 2025 bug

intgd — Mon, 12 May 2025 15:12:25 GMT

@benjaminb We are still facing problem with DAX Measures visuals on Power BI RS Desktop (32 bit).

It seems MSFT has updated PBI RS (server) but never fixed the PBI RS Desktop (32 bit) .

I have compared (SHA1 hash) the installer exe (PBI RS Desktop 32 bit) , released on Jan 13, 2025 and Jan 22, 2025, both are exact match. This confirms MSFT never fixed the Desktop side of things.

If anyone has seen PBI RS Desktop issue, please comment ?

Re: Power BI Report Server January 2025 bug

benjaminb — Mon, 12 May 2025 18:54:20 GMT

Could you please try the latest Power BI Desktop build from Download Microsoft Power BI Desktop from Official Microsoft Download Center? If the issue persists, please post the issue to desktop section.

Re: Power BI Report Server January 2025 bug

intgd — Mon, 12 May 2025 19:54:44 GMT

I am using Version: 2.138.2255.0 32-bit (January 2025) Power BI RS desktop . It was release on Jan 22, 2025. I am getting the issue on this version .

Downloaded from - Download Microsoft Power BI Report Server - January 2025 from Official Microsoft Download Center

Re: Power BI Report Server January 2025 bug

intgd — Wed, 14 May 2025 19:57:36 GMT

Thanks, added to Desktop section - https://community.fabric.microsoft.com/t5/Desktop/Issue-with-DAX-Measures-visuals-Power-BI-RS-Desktop-32-bit/m-p/4693050#M1402341

Re: Power BI Report Server January 2025 bug - still occour in june version

TomOm — Fri, 01 Aug 2025 09:04:45 GMT

In version 15.0.1118.134 scheduled refresh missing for publisher role.