topic Re: Unable to render paginated report - One or more parameters required to run the report have not been in Service

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

AvPowerBI — Wed, 09 Dec 2020 21:12:22 GMT

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

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

Anonymous — Wed, 01 Jul 2020 01:03:21 GMT

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

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

AvPowerBI — Wed, 01 Jul 2020 09:09:10 GMT

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

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

Anonymous — Mon, 06 Jul 2020 09:50:34 GMT

Anonymous AvPowerBI facing the same issue suddenly. any clue on the solution?

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

AvPowerBI — Mon, 06 Jul 2020 10:24:55 GMT

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...

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

rpatkar — Sat, 12 Sep 2020 22:51:35 GMT

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!

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

Anonymous — Fri, 18 Sep 2020 13:14:00 GMT

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.

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

rpatkar — Fri, 18 Sep 2020 23:50:17 GMT

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

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

Anonymous — Mon, 21 Sep 2020 13:36:36 GMT

Same issue manifested for me today. Was this ever resolved and explained?

Thanks,

Craig

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

rpatkar — Mon, 21 Sep 2020 13:42:19 GMT

hi Craig,

Please provide the request Id from error dialog and answers to the 3 questions I posted above. This will help me investigate better. Thanks!

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

Anonymous — Mon, 21 Sep 2020 14:39:11 GMT

Thanks rpatkar

Here is an example of the error:

Unable to render paginated report
One or more parameters required to run the report have not been specified.
Activity ID: 21623694-c49a-4490-5377-323470e8f835
Request ID: 21623694-c49a-4490-5377-323470e8f835
Correlation ID: 488b03d4f1254b02972338b0d5ef80b6
Status code: 200
Time: Mon Sep 21 2020 09:43:31 GMT-0400 (Eastern Daylight Time)
Cluster URI: https://canadacentral.pbidedicated.windows.net/webapi/capacities/356362E6-A553-4E04-852D-8034A69784C5/workloads/RsRdlEngine/rs/automatic/v1.0

As for the questions ...

No, I have not opened a support ticket yet. Thought I'd check on this thread first to see if there was a DIY resolution.
It's a bit complicated and ties in with Q3.-- see explanation below.
Yes, the report uses a hidden parameter to control data security (RLS).

Explantions for #2 & 3:

The report is embedded in a web app (app owns data) which is where the error message appears. The embedding app passes a value to the hidden parameter to restrict the data displayed (RLS).
The report renders without error when opened in Report Builder, and in the Power BI Service only if the hidden parameter is unhidden (report is not usable in Power BI Service otherwise because it doesn't have the hidden parameter value there).
The data source is an Azure SQL database in the same subscription/tenant. No gateway needed.

No changes were made to the report or data source. Users started reporting the error early this morning (EDT).

If there is no simple resolution, I can log this same information to a support ticket.

Thanks,
Craig

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

Anonymous — Mon, 21 Sep 2020 21:01:16 GMT

We have the same problem. It all started today and has pretty much the same approach to paginated reports and RLS. I have oppened a support ticket but no answer yet. I'll let you now if i get any solution for the problem.

/Nick

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

rpatkar — Tue, 22 Sep 2020 05:27:16 GMT

hi Craig and Nick,

We have identified an issue with using hidden parameters. This scenario regressed with most recent deployment and we are working on fixing the issue. For your scenarios, did you pass the hidden parameter through URL from web appt to the embedded paginated report? Please do file a support case to ensure timely communication regarding the fix.

Thanks,

Rohit

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

Mema — Tue, 22 Sep 2020 12:56:51 GMT

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/workloads/RsRdlEngine/rs/automatic/v1.0

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

Anonymous — Tue, 22 Sep 2020 13:57:10 GMT

Hi rpatkar,

Yes, we are passing the hidden parameter value via URL.

I filed a support case for this yesterday (#120092124008667). The agent I spoke to followed up overnight to say that he had escalated the issue to the backend engineering team.

Thanks,
Craig

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

rpatkar — Tue, 22 Sep 2020 17:34:15 GMT

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!

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

Mema — Wed, 23 Sep 2020 08:09:23 GMT

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

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

Anonymous — Wed, 23 Sep 2020 10:51:07 GMT

We have the same error. We are using hidden parameters in our reports.

Unable to render paginated report
One or more parameters required to run the report have not been specified.
Activity ID: 2d2b6cd2-43e9-cf5a-de25-da8a19c35ab8
Request ID: 2d2b6cd2-43e9-cf5a-de25-da8a19c35ab8
Correlation ID: 43be0dbfc2f448afa5fe2beac4eb75d1
Status code: 200
Time: Tue Sep 22 2020 12:05:01 GMT+0300 (Moscow Standard Time)
Cluster URI: https://eastus2.pbidedicated.windows.net/webapi/capacities/6E1C173C-FF5D-40F8-846B-1874B13482BA/workloads/RsRdlEngine/rs/automatic/v1.0

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

Anonymous — Wed, 23 Sep 2020 20:26:10 GMT

FYI ... Today, MS Support confirmed this issue and informed me that a fix in in the works:

Issue Definition: RDL reports with hidden parameters fails to render with Error as "Unable to render paginated report One or more parameters required to run the report have not been specified".
Resolution: Backend team did the investigation and confirmed that they have identified the issue and currently they are working on a fix which is expected to be deployed by 10/2/2020.

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

Anonymous — Thu, 08 Oct 2020 14:07:34 GMT

Is anyone aware if this fix went into Production? If so, must users recreate their subscriptions now? We are still receiving error messages on our old/existing subscriptions.