Paginated Report Credentials Issue

[Anonymous]

This is my first time using Power BI Report Builder let alone attempting to deploy and run a report in app.powerbi.com. I created the report as I would have when using Reporting Services, connection type of Microsoft SQL Server and a couple of Stored Procedures to fetch my data. Everything works fine locally, as it should. The Power BI Admin created a Gateway to the local server so when I deployed to the service I made sure the SQL connection mapped to the Gateway. However, when I run the report I get this error:

Data for this report could not be fetched. The data source was found, but the credentials or identity used to connect to the data source were incorrect. Please update the credentials for this report before trying again.

I am assuming it's just something I have missed in the setup but I don't have enough experience in Power BI to troubleshoot it. I did deploy an actual Power BI Report that uses the same connection and Stored Procedures and it works fine. So it seems to just be an issue with the Paginated Report.

[Anonymous]

It ended up being EXECUTE permissions on a Stored Procedure being missing, thanks for the input!

[Wikkleyn_81 · Accepted solution]

Hi @Anonymous  ,
When we encounter this issue, it's usually related to the permissions of the user configured in the Gateway connection's authentication. During development, you're typically using your own credentials which, as you mentioned, have all the necessary permissions.
Please double-check the permissions assigned to the user configured in the Gateway connection to ensure they match what’s required.

[Anonymous]

That was my initial thought too but the Power BI report using that same Gateway renders, so that makes me think the Gateway is fine but something in the Paginated Report needs to be updated. But I will verify with the Admin. Thanks!

[tayloramy]

Hi @Anonymous, 

When you upload a Power BI report, it will cache the data in the report file. After you upload it, does a semantic model refresh work successfully? If yes then it's not the gateway. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.  

[Anonymous]

Ah, did not know that, it did throw an error when I forced a Refresh. Might be cooking with gas now. Thanks!

[tayloramy]

Hi @Anonymous, 

This means that the credentials set up in the gateway connection are incorrect. 

Please have your admin update the gateway connection with correct credentials and try again. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.