The date picker on the report viewer control in SSRS 2005 is causing our application to slow down a lot; when the user clicks the calendar icon, it really takes a while to load for them for some reason. Any ideas why?
Thanks.
You can use the newer versions of Report Viewer (2008 or 2010 ) this control performed and may help you to solve your issue.
Note that, report viewer is totaly seperated from your reports and you can easily upgrade it.
Related
All of the reports I have on our SSRS server work great through the SSRS ReportViewer web control but I have 2 reports that will not render. I fill out the parameters and the page refreshes with nothing. No loading gif, no toolbar, just the parameter controls.
I have tried using the ReportViewer on Chrome, Firefox and IE. All reports but these two certain reports work great.
I've tried the methods listed in:
SSRS 2008 R2 - SSRS 2012 - ReportViewer: Reports are blank in Safari and Chrome
Only 2 reports out of >10 fail to render on SSRS 2008R2 SP2
Does anyone know why certain reports may not display while others will?
Update: I have found that if I pass in a test parameter, the report will render with 0 results. However if I pass in a valid value, I get nothing.
Turns out to have been a couple of things.
First was something to do with the query. One of the parameters accepted values with commas in it and when changing the values to not contain commas, the report worked fine. This might have been attributed to how the values were being passed to the parameters.
The DIV containing the report needed overflow: auto; added to it's styles.
I assume you are on SSRS 2008 r2. While I'm not familiar with using the web version of ReportViewer (I always preview my reports in Visual Studio), I have found that if my Data Source loses its connection string this can happen.
Do you have visual studio with SSRS? If so can you open your report there and preview it?
There is an SSRS report embedded into SharePoint that needs to be fixed (the report does). I am familiar with SSRS and SharePoint, but not with the two together. Usually when I work with SSRS it is in Visual Studio. I can fix reports from there, and deploy them to the report server. But I'm not sure how the report got to SharePoint. Someone else put it there and now they are gone and I need to fix it. How do I go about editing / fixing an SSRS report on a SharePoint site? Where is this report anyways, on the report server with a link to it? I cannot find it there.
Please help.
Once in Sharepoint, click the dropdown arrow next to the report as shown below and choose 'Edit in Report Builder'.
Report Builder will take a few minutes to open. Once Report Builder is open, then you can edit the report and save it. Refresh the SharePoint site and your report will be updated.
Depending on your version of SSMS. I have SSMS 2008R2, which is compatible with Report Builder 3.0
Here's the link to download Report Builder 3.0
https://www.microsoft.com/en-us/download/details.aspx?id=6116
I had the same struggle once. Hope this helps.
In Microsoft Visual Studio when i run a Report using a Preview the data is showing and when the same report i run from server side its not showing the same data as per the Visual Studio Preview
please suggest
Visual Studio caches locally data in order to reduce the generation time for design puroposes, it will only update the data if you change the parameters values so if your report doesn't have any parameter you will get old data.
To refresh Visual Studio data preview the report and press the refresh button inside the generated report.
Let me know if this can help you.
I had a very similar problem. When I previewed on VS 2015, everything displayed perfect, but when I deployed to my server successfully, only one field wasn't showing up.
What ended up working was changing my report data sets from shared to embedded. Even though they were referencing the same query, somehow there was a disconnect when referencing the shared data set rather than embedding it directly in the report.
I have a report that gets pulled and exported through sharepoint. Today I made some changes to one of the reports deployed those changes. Now when I render the report in sharepoint everything looks correct. However when I export the report in CSV format the column names revert to the aliases from the sql query instead of what I put in the designer for them.
Has anyone experienced an issue like this?
Any help is appreciated thanks.
I have seen this issue in the past with XML export. This may help:
Select the column, then open the Properties panel (you can also hit F4 as a shortcut)
Change the DataElementName attribute
Try export to CSV again
You didn't specify which version of SSRS you are using. This is a screenshot in Visual Studio 2010 / SSRS 2012:
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.