Unable to render paginated report - One or more parameters required to run the report have not been

[AvPowerBI]

Hi,

We have a number of rdl reports uploaded to the Power BI Service, we've had no issues with these reports and have been running fine for month but today for some reason we are getting the below error message on a few of the reports:

Copy

Any ideas why this has happened all of a sudden? Has there been an update to the Power BI service that has caused the reports to now fail to run? Anywhere I can check the logs that would show me this?

I can run the same rdl reports locally on Visual Studio with no issue?

Thanks

[v-shex-msft]

Hi @AvPowerBI,

What type of datasource are you worked? How you configure your parameters? Any specific setting enabled on these parameters?

Can you please share more detail information to help us clarify your scenario?

How to Get Your Question Answered Quickly 

Regards,

Xiaoxin Sheng

[AvPowerBI]

Hi @Xiaoxin,

Thanks for your reply.

All our connections point to an Microsoft Azure SQL Database (not aware of any changes to these servers).

Most reports will have a hidden parameter which will be using the built in function =User!UserID (to know which user has logged on and then this will be used to passed to a stored procedure to limit what data that user can see).

Some of the reports will have parameters to call the Calendar where the user will pick their date ranges (From and To). 
It could possibly be one of these two parameters but it's hard to know which one!?

Like I said before no one in our team has touched any of these reports and have been working fine since yesterday. We have dedicated Power BI server, so unless there has been an automatic update by Microsoft that has caused these reports to fail then I do not know as I wouldn't know where to check or go if there are any log files to tell me this; I cannot see any release notes by Microsoft about changes to the Power BI service? Or if our resources on our dedicated server has been limited which is causing the rendering of these parameters to not process correctly!?

I'm not sure now what the problem is!?

Thanks

[Anonymous]

Spoiler

@v-shex-msft @AvPowerBI facing the same issue suddenly. any clue on the solution?

[AvPowerBI]

Hi @Anonymous 

There is no fix for this from Microsoft, but it looks like there is an issue with the Calendar Date Pickers, so this is what I have done to get round this...

[rpatkar]

hey guys,

Power BI service deploys frequently and looks like we may have introduced a regression. We have made a few fixes during this time that should have fixed this issue. If you are still running into this issue, kindly provide the Request Id from the error dialog. Thanks!

[Mema]

I have this error and it always worked before, this is the error info:

Unable to render paginated report
One or more parameters required to run the report have not been specified.
Activity ID: 802866e4-fcf2-a077-9ab8-a83177da56eb
Request ID: 802866e4-fcf2-a077-9ab8-a83177da56eb
Correlation ID: 2ff2e3ec207e46a29db829fc350ed72d
Status code: 200
Time: Tue Sep 22 2020 13:53:12 GMT+0100 (British Summer Time)
Cluster URI: https://northeurope.pbidedicated.windows.net/webapi/capacities/2161C086-1457-43F6-8D0B-793E0B273ED3/...

[rpatkar]

hi Mema,

The call stack in backend traces looks similar to issue reported by Craig and Nick. Please confirm whether you are using hidden parameter, passed through URL. Thanks!

[Mema]

Yes, I am using hidden parameter passed through URL, just the one

[JulieF]

We are continuing to experience issues with subscriptions that were previously set up and running and then suddenly fail with the following error: Report_Processing_Error, One or more parameters required to run the report have not been specified.

The Request Id is: 6246db9a-2c52-482f-b421-8b3e0cea04e7

Our set up: Report Builder paginated reports published in PowerBI. Data Source = SSAS Tabular cube via a DAX connection.

We did not modify the report or the cube in any way between the time the subscription ran successfully and ran with the error. In addition, the filters/parameters we have set up all return data.

Is there a list of other factors that could impact the subscription this way? For example, if there is a powerbi update, does it negatively impact subscriptions? What if the service is restarted? We are grasping at straws, here. Thank you, in advance, for your assistance.

[rpatkar]

hi Julie,

Thank you for sharing the request Id. A few questions -

1. Have you already opened a customer support ticket on this issue? If you'd rather continue on the forums then please start a new thread with this issue. You can tag me there to get notified.

2. Does this issue should repro when you try to open the report in browser? If report is taking more than 10 minutes in fetching data from on-prem data source through the Gateway then please set an explicit timeout value in "Dataset Properties" for the dataset used in your RDL report.

3. Are you using hidden parameters in your report?

Thanks!

Rohit