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?
Related
I have several SSRS reports (RDL) created in SQL Server 2014. I want to run these multiple RDLs through Visual Studio 2015.
I am able to run one RDL through VS2015 by giving the server name and report path in the report viewer as shown in this ReportViewer image.
But I am not able to run multiple RDLs. Can someone help me out in this project?
Here is a link. https://msdn.microsoft.com/en-us/library/aa337089.aspx
reportViewer1.ProcessingMode = ProcessingMode.Local;
LocalReport localReport = reportViewer1.LocalReport;
localReport.ReportPath = "Sales Order Detail.rdl";
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)
I'm using SQL Server 2008 R2 Reporting Services. I'm seeing different data in a dropdown that's on the report, depending on whether I'm running the report in 'preview' mode from VS2008, or whether I'm running it from the report viewer at http://localhost/ReportServer_SQL2008. Any suggestions?
I'm using SSRS via SQL Server 2008 R2 Report Server
When I preview my report (originally created by another developer) in VS2008 I see correct data in one of the dropdowns for my report:
When I run the report via the report viewer on my machine at http://localhost/ReportServer_SQL2008, I see an incorrect GUID displaying in place of some recently added items in the dropdown
I've re-built the report in VS2008, and I've manually re-uploaded the .rdl file to my report server using the Report Manager at http://local-machine-name/Reports_SQL2008/, but I still see the incorrect data when using the IE report viewer.
I've looked at where the data is coming from that's used for populating the dropdown, using Query Analyser - when both viewing the report preview and viewing the report through the report viewer, the data is coming from the same database, using exactly the same stored procedure call
The 'raw' data being pulled from SQL gets some processing before it's used in the relevant data field in the report - it gets processed by using a custom .NET assembly, to pull back a 'friendly' string based on the report user's locale. This uses .resx files held in the VS2012 project for the custom assembly , that transpose the data. The entries in the .resx all seem to be correct.
I've manually deployed a debug version of the custom assembly that does this locale translation to C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PublicAssemblies (my own default location for custom assemblies)
When I debug against this assembly in VS2012 by attaching VS2008 to the debug process and running the report preview in VS2008, the correct program name e.g. 'GRIT CARDIO' is returned
So the question is 'why is this not being returned when I run the report in the IE report viewer'?
I'm using Report Builder 3.0 to create some reports for an application. I'm using Report Builder because I'd like the client to be able to customize the reports as needed in the future. Now, when I edit a report in Visual Studio (that is using Business Intelligence Development Studio), I can set the properties for the report. That way I can set the language for the report which is important to ensure that all the number/date formats appear correctly, as my client is in France, and they're fussy about that sort of thing. Setting the language adds an element to the report xml as follows:
</ReportParameters>
<Language>=User!Language</Language>
<rd:ReportUnitType>Mm</rd:ReportUnitType>
<rd:ReportServerUrl>http://localhost/reportserver_sql2008r2</rd:ReportServerUrl>
<rd:ReportID>24c58c7f-2a6a-4f68-878d-d26d97bb16e8</rd:ReportID>
</Report>
How can I access the report properties, and specifically the report language in Report Builder?
Thanks,
Patrick Collins
I know this is way old, but it's a valid question. I've verified that you can do this in Report Builder 2.0 (10.0.4.4000.0) and Report Builder 3.0 (11.0.2100.60):
Go to the "View" tab of the ribbon at the top of the screen.
Check the box next to "Properties" - voila, the familiar Properties Pane appears.
Go to Localization - Language and use the dropdown to select your desired language
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