Is there a new Report Viewer runtime for SQL 2016? I get the new report viewer UI when I log into the SSRS Reports manager, but, if I embed those reports in a website, it requires the Report Viewer redistributable, and the most recent one I can find is from 2015, which I assume will not have the new UI.
Thanks!
Ryan
No, there isn't, at least not yet.
The ReportViewer installed by SQL-Server 2016 is v12, which is the 2015 Viewer.
Also, it seems SSRS 2016 uses a RS:ReportHost tag, wheras < 2016 used to use the rs:ReportViewer tag.
Edit:
But now you can download the preview here:
https://www.nuget.org/api/v2/package/Microsoft.ReportingServices.ReportViewerControl.WebForms.Preview/130.1700.305
Rename
microsoft.reportingservices.reportviewercontrol
.webforms.preview.130.1700.305.nupkg
to
microsoft.reportingservices.reportviewercontrol
.webforms.preview.130.1700.305.nupkg.zip
and then unzip it.
It still is using .NET Framework 4.0.
I got it working, here:
https://github.com/ststeiger/ReportViewerWrapper/tree/master/Embedded2016
Just in the nick of time, had to fix a nasty bug with WordOpenXML export.
In versions of ReportViewer < 2016, you can't print a Word 2007+ (WordOpenXML) document when in landscape-format).
Switching to ReportViewer 2016 Preview solved this.
There appears to be a bug in ReportViewer, when you export to word.
Vertical alignment is not center by default, in Visual Studio it is (old bug).
And merging the last row of a table in a word-document will result in a garbage-layout - when pageformat = landscape (new bug).
If you put this formula into the footer
=System.Convert.ToString(Globals!PageNumber) + "/" + System.Convert.ToString(Globals!TotalPages)
you always get 1/1 in Word.
If you use
=Globals!PageNumber & "/" & Globals!TotalPages
then it works correctly... (old bug)
There is a latest nuget package of Report Viewer 2016 Preview: Microsoft.ReportingServices.ReportViewerControl.WebForms.Preview (version 130.1700.305, published 2016-09-20).
And read carefully this page to setup it properly: https://github.com/Microsoft/Reporting-Services/blob/master/Docs/Get-Started-With-RVC.md#next-steps---read
The Nuget package is now no longer in Preview, so you can get Report Viewer 2016 as detailed here:
https://learn.microsoft.com/en-us/sql/reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls-get-started
If required, SQL Server Data Tools will install the latest Report Viewer control:
https://learn.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt
Have you looked inside
C:\Windows\assembly\GAC_MSIL\Microsoft.ReportViewer.Common\13.0.0.0__89845dcd8080cc91\ ?
When we upgraded our v12 to v13, that we had Power BI issues :
SQL Server 2016 CTRP3.2 Report Viewer is missing a JavaScript method
The drawback is Microsoft haven't exposed the ReporViewer controls as a redistributable runtime package (yet)
Related
SSRS report wont work with a shared data source .
Report works perfectly fine if i use embedded data source.
The moment i switch back to shared data source the report goes blank again, no error shown.
I am trying to preview the report in visual studio 2013.
Any one got a similar problem? any suggested fix for this?
Sql server BI plugin update fixed the rendering issue
I can generate a report in SSRS 2008 but when I try to generate it again it will fail with exception below. It will however work again once after SSRS is restarted. What configuration option could be affecting this? (I have added all necessary extensions.)
processing!ReportServer_0-1!1ef4!01/28/2013-16:39:41::
ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: You have attempted to use a rendering extension that is either not registered for this report server or it is not supported in this edition of Reporting Services., ;
INFO: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: You have attempted to use a rendering extension that is either not registered for this report server or it is not supported in this edition of Reporting Services.
library!ReportServer_0-1!1ef4!01/28/2013-16:39:41::
WARN: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: You have attempted to use a rendering extension that is either not registered for this report server or it is not supported in this edition of Reporting Services.
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.CreateRenderer(String format, IRenderingExtension& newRenderer)
at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderSnapshot(RenderingContext rc, ProcessingContext pc, GetResource getResourceCallback)
at Microsoft.ReportingServices.Library.RenderFromSnapshot.DoRendering(ProcessingContext pc, RenderingContext rc)
at Microsoft.ReportingServices.Library.RenderFromSnapshot.CallProcessingAndRendering(ProcessingContext pc, RenderingContext rc, OnDemandProcessingResult& result)
at Microsoft.ReportingServices.Library.RenderStrategyBase.ExecuteStrategy(OnDemandProcessingResult& processingResult)
It seems SSRS is trying to load an assembly containing some report rendering functionality (maybe some charts you added)?
If this is the case, this article explains how to register a DLL with SSRS.
It turned out the problem was SQL Web Edition does not support html extensions. You need at least Standard. Why it worked once remains the question.
The problem in our case is that via API we were requesting a report and attempting to convert the report from HTML to a different rendering extension. And, unfortunately, the specific Reporting Services instance’s configuration file has not been configured\extended to support the requested rendering format.
In MS SQL Server 2008-R2, the configuration file is located in a directory structure resembling the following:
E:
\Program Files
\Microsoft SQL Server
\MSRS10_50.MSSQLSERVER_RS
\Reporting Services
\ReportServer
And, the actual file name is rsreportserver.config
In the configuration file, find the “Render” section:
< Configuration >
< Extensions >
< Render >
Within the Render section, find the corresponding “Extension” entry.
If the extension is not found, add it:
I followed the steps listed on these MSDN pages:
Creating a Custom Report Item Run-Time Component
Creating a Custom Report Item Design-Time Component
How to: Deploy a Custom Report Item
I have now a custom report item that works fine in Visual Studio 2010, but does not show up when rendering the report in a web browser. The Windows Event Log is saying:
"Report Server (MSSQLSERVER12) cannot load the CRITest extension."
CRITest is the name I gave my CRI.
I developed the same object in Visual Studio 2008, because I thaught that SSRS 2012 does not support .NET 4.0 (in the ReportingServicesService.exe.config you find SupportedRuntime=2.0). Result: the object cannot be dropped into a report developed with Visual Studio 2010, because the Common7/IDE/PrivateAssmblies needed for Reporting Services has another version number.
Does anyone have a good suggestion?
I have some reports that optionally, redirect to another report.Of course parameters are passed during the redirection. The problem is that in Report Viewer the link that should take the action isn't clickable. This works fine when running from Report Manager.The links do what they're meant to (they link to other reports passing through parameters). When the report is run from the asp application with the report viewer, the links do not work at all.This problem became consistent when Report Viewer was upgraded from version 9 to 10 (to eliminate other problems).What should be done?
Not found what was the real problem.Sure it had to do with the fact that after upgrading Report Viewer from 9 to 10 while Visual Studio version is 2008 in our server.However it was resolved after copy-pasting a "good" cell, which did't cause problems from one report to the problematic ones.Only changing the link redirecting to the other level report was left to do in the copied cell.Now all it is fine.
In the process of deploying Reporting Services 2008, some users get confused with the new Report Builder 3.0 it comes with, especially its differences versus version 2.0 which came with SSRS 2005.
Is there a way to configure Reporting Services so it shows 2 buttons to run Report Builder? One pointing to current version, the other to the previous, so users can continue creating their reports whilst they explore 3.0's new options at their own pace.
If this is not possible, is there a way to configure Rep. Services so it uses Report Builder 2.0 and not 3.0?
Thanks in advance.
You need to set the "Custom Report Builder launch URL" in report manager. To do it go to report manager (usually http://<reportserverhost>/reports) and click Site Settings in the upper right corner. Then you'll see Custom Report Builder Launch URL field in the bottom of the General settings tab. By default it is blank but you can force a specific version of report builder to load from there. For Report Builder 2.0 you should be able to set the value to "/ReportBuilder/ReportBuilder_2_0_0_0.application".
The Site Settings Page (Report Manager) documentation topic and How to: Set Report Builder 2.0 as the Default ClickOnce Report Builder Version explains more detail.
I guess it is impossible to do some changes on the menu but I you can do a bit of a hack where you overwrite the ReportBuilder.application to an application that you self built which contains button to the version of the ReportBuilder you want to run something like this.
On that button you just define an event to do the following
ProcessStartInfo sInfo = new ProcessStartInfo("http://YourServer/LocationOfYourV2Appplication/ReportBuilder.application");
Process.Start(sInfo);
The following path where the files you need to manipulate is by default here C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\ReportBuilder