Forum Discussion
Post PatronUnable to render paginated report - One or more parameters required to run the report have not been
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
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.
30 Replies
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.0Hi 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
AvPowerBIHi @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
rpatkarPower BI Team
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!
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.0As 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
annwallingerAdvocate I
I narrowed it down to determine that if you pass the parameter on the URL and then you have ANY cascading parameters (even not related to the hidden one) that cause a parameter update, the hidden url parameter gets dropped. I have a case open and MSFT has been able to reproduce the error and is working on it.
- rpatkar
hi JulieF, team is currently working on issue reported by annwallinger. Are you seeing same issue? i.e. issue when using hidden parameters AND cascading parameters on the URL? If it's a different issue then please open a support ticket with Microsoft as will need to gather diagnostic information. Thanks!
rpatkar: We are also seeing what looks like the same issue as annwallinger. Users are receiving errors "There was an error with your subscription... Report Processing error... One or more parameters required to run the report have not been specified..." These messages list different paramters (not always the same parameter that is missing). These happen to subscriptions that ran successfully for a time and suddenly to not run. Other subscriptions without changes to the reports. We also use hidden parameters and cascading prompts. We are seeing this on multiple different reports. I am happy to create a support ticket if this is different.
- rpatkar
hi JulieF, please create a support ticket. Issue here is perhaps related to the one reported by annwallinger but since you are using subscriptions and are not using RDL embedded, the code paths are a bit different and at minimum from product team we will like to verify that your scenario also gets fixed as part of fixing issue reported by annwillinger. Thanks!