I have developed a Direct Query paginated report in Power BI Report Builder and published it to Power BI Service.
Once it's published I go into the report and try to select the parameters to generate the report, however I can only select a value for the first parameter and none of the others. the others remain greyed out. They are all working directly in the Power BI Report Builder app report preview, and some other users on my team are able to select and filter the parameters, whilst some are not.
We have verified that this is not a user access issue, since I logged into a test account and tried, and still experienced the issue, whereas someone else logged into the same test account and did not experience the issue.
I have tried adding *.powerbi.com as a trusted site on all my browsers (Chrome, Firefox, Edge) however it has not helped. I tried clearing my cache and cookies but no luck. I tried on incognito mode, and that allowed me to select the second parameter as well, however I could not select any more after that.
I'm really stuck on what could be specifically causing this issue and would love to hear if anyone else has experienced this or has any thoughts.
Image:
Related
In SSRS (2019), when I try to consume the reports from a remote machine (belonging to the same domain), I see behavior that I've never seen and can't explain (whatever the authentication mode).
See picture
With FireFox :
When I enter a folder and select a report, instead of showing me the report, I have the equivalent of another SSRS instance which is displayed instead. And this in an infinite way. Reports are not displayed. I don't understand where this is coming from at all.
SSRS Error
With Micorsoft Edge :
With Edge, authentication seems to fail, see attached image. And if I ever manage to authenticate myself, the GUI is frozen.
SSRS Edge
On SSRS serveur with Administrator account, all work perfectly.
I've completly uninstall SSR and re install it, with out any difference.
A couple of weeks ago, our Access application suddenly began to fail mysteriously. Comboboxes on random forms would not fill with rows when recordsources were set. These include forms that have not changed in years. Stepping through the code in the debugger always results in a successful outcome. Trying multiple times consecutively would occasionally work. One or two computers still work reliably, though these have a source control addon called Ivercy installed. When you run the deployed version (without the addon active) these machines show the same unreliability.
Last week, we found more issues including some forms and reports that would not populate on initial opening. Reselecting the same filter date (or other rowsource changes) once the form is open brings up the expected set of rows. Again, loading the form while stepping through the code always works.
These behaviours lead me to believe there is some sort of fault that has been introduced in a recent Access update. Has anyone else seen this kind of problem?
One instance of this issue occurs on a very simple, one page report that has no user code in it at all. I would have been willing to believe that we had been doing something systematically wrong in our code, but this code-less report seems to suggest otherwise.
My machine (which exhibits the problem) is using Microsoft 365 Apps for enterprise
Version 2105 (Build 14026.20308 Click-to-Run)
When running SSRS Reports that have many parameters that users will change and click view report to see different results, chrome security will intermittently prompt for Sign In. When it does, valid credentials will not work.
This started happening with the latest chrome update where the tabs because curved about two months ago.
IE and Edge work fine (albeit much slower)
The Datasource uses a sql login with full access to the SQL Server.
The end users are on windows auth and should not be prompted once authenticated.
Same report has worked for a long time prior to latest update and works in other browsers. Chrome Canary does the same thing. All Chrome users are having this same issue rendering chrome unusable for SSRS.
I have access to the reporting services log file, but there is lots of traffic so very hard to read.
I can run profiler, but the server is very busy and I'm since I'm not sure what to look for, leaving it wide open has so many other threads from other users and it seems even my spid changes constantly as ssrs moves through the requests. Enter report, view report, view report, view report, etc..
Cannot find anything close on google except old stuff that we've went through with chrome using the ie lan advanced security settings. None of the old stuff helps. Have also check ssrs configs to make sure we are forcing windows auth and it is.
Any help with the actual problem or even help with how to troubleshoot this would be greatly appreciated.
Screenshot provided just after hitting view report for the third time. Correct credentials will not work at this point.
Ken . . .
Resolved as a Digital Guardian network tool blocking.
I am using Dynamics CRM 2013 on premise.
I have built all the reports based on stored procedures in SSRS.
one report however, that has no issue with execution definitions, permissions or what ever,
once executed causes to browser to crash (any browser, i tried FF, Chrome, IE9 and up, )
it seems the problem is not a report execution problem but a report rendering problem for this specific report.
I cannot cache the report or make a snapshot of it, as the values of the reports also depends on the user running the report (among other parameters user-defined) and each user should get a different result. - i have more than 400 users.
I have tried searching for any one who had face this kind of issue and reported on it but failed. hence decided to post this question my self.
if anyone has any idea, please share.
thanks
Have you enabled tracing/logging in SSRS? http://msdn.microsoft.com/en-us/library/ms156500.aspx
You might turn on verbose logging while trying to run the report to see if you can get more helpful information.
If you write code, you can write a .NET application that calls the SSRS web services to render the report. Doing that will help you know for certain whether it's a browser rendering issue since you can get back the report as a byte array and save it to disk as Word, PDF, etc.
I've been following this tutorial (lesson 6) in order to build and deploy a sample report with an embedded subreport which reads its parameters' values from the parent report. This subreport is embedded in one of the group rows of the report's table, and both share the same datasource. Additionally, detail rows appear collapsed until the user presses the (+) button for each group of data in the table.
The report works great when I preview it at the Business Intelligence Development Studio (by the way, SQL 2005 Express edition) but when I deploy it and try to see in the Report Manager, the subreport is not shown. And, if I press the (+) button, the following message appears:
Some parameters or credentials have not been specified
Does anybody has the slightest idea of what I am doing wrong? Why does it works perfectly in the Report Viewer embedded in Visual Studio but not in the Report Manager web app?
Thanks in advance.
Does the subreport use the same Data Source as the parent report? If not, be sure to check the data source of the subreport to make sure it is correct. Check in Report Manager, not your local copy.
I'm beginning to think this could be an issue with the browser. I'm currently using Internet Explorer 8 Beta and I'm also experiencing weird behavior from the Report Manager. I've tried with Google Chrome and Firefox 3 and, although the navigation is not as smooth as I like, the problem seems fixed.
it happens when you use IE8 as a report browser. I faced same issue and when I tested on chrome it worked fine .
This may or may not be related, but I had a similar problem some time ago (except that in my case the reports were accessed through a custom web page) and it turned out we had an older version of the report viewer control (the version that came with Sql 2005 RTM). After upgrading to the latest version the issue went away.