Using: SQL Server 2012 Reporting Services,
Product Version: 11.0.7462.6
Report Server Mode: Native
A server side rdl report is generated as PDF.
Sample rdl file contents here
On a Windows 2008 R2 Server, the generated PDF looks ok:
On a Windows 2016 Server, there are minor spacing issues with the PDF (see bits underlined in red):
i.e. for line "1", the spacing between the lower case "l" and number "2" is non-existent. The text value for line "1" looks like this:
="Chos achrPapis Frhmistisya Sdt AFT hTe apetociaschmrdtP rilyus TtFam l25044025 - stuTr" & vbcrlf & "a"
Note that line "2" displays ok. Line 2's text value is the same as that for Line 1, but only has 1 line:
="Chos achrPapis Frhmistisya Sdt AFT hTe apetociaschmrdtP rilyus TtFam l25044025 - stuTr"
So it seems having a carriage return is a factor in this problem.
Also, in line 3, there should be a space between "world" and "Support", but there isn't.
The problem only seems to be on export to PDF. The report looks fine when generated in Html, Word etc.
Can anyone shed any light?
EDIT: I should add that there are no special characters or anything like that being used in the report.
Moe,
I can't confirm your issue. I deployed the report on SSRS 2016, and it looks fine to me.
I'm using:
SSRS:
Microsoft SQL Server Reporting Services Version 13.0.4446.0
SQL Server:
Microsoft SQL Server 2016 (SP1-CU4) (KB4024305) - 13.0.4446.0 (X64) Jul 16 2017 18:08:49 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows Server 2016 Standard 6.3 (Build 14393: ) (Hypervisor)
Maybe your CU is not the same as the one I'm using here, so I suggest updating SQL to the latest update.
See the picture below:
Related
When I am trying to edit a report by clicking on the design option, an error message is displayed as:
The report builder is not available. Please check the report builder URL in report setup.
So is there anything new with reports in SQL 2016 or am I missing something.
I am using SQL Server standard edition - 13.0.15700.28
Himanshu,
SQL Server 2016 stopped this feature. till SQL server 2014 this functionality working name as clickOne Technology.Error"The report builder is not available. Please check the report builder URL in report setup." is the custom error of your code not a part of SQLServer 2016.
So find any other way to open SSRS reports in design view with report builder.
Use Below mentioned URL.Maybe it helps you to open Reportbuilder URL in SQl Server 2016.with the help of WebBrowser in C#. now we can open Reports builder Successfully.
URL With Html encoding :-"reportbuilder:Action=Edit&ItemPath=%2FProject%2FReports%2FRealization&Endpoint=http%3A%2F%2F101.11.11.111%3A80%2FReportServer"
URL without HTML encoding :-
"reportbuilder:Action=Edit&ItemPath=Project/Reports/Realization&Endpoint=http//101.11.11.111/ReportServer"
If report builder not install first we need to install in local machine after that it's working.
Thanks ,
Kapil
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)
Calling sp_send_dbmail using the #query option to run a query and use the result as the email body, appears to cut off the resultset at around 64KB maximum, regardless of the mail configuration settings. I have also tried attaching the result as a file attachment to the email, but am having the same problem there as well - the file attachment caps itself around 64KB.
Anyone has a solution or workaround for that problem?
The problem was fixed by Microsoft in CU4 (Cumulative Update) for SQL Serve 2014. Please follow this link in order to obtain the file:
http://support.microsoft.com/kb/2999197
There is a bug in the SQL Server 2014 version of XPStar.dll.
My workaround was to copy the file from a 2012 instance and replace the 2014 one. After a restart the attachment works properly.
We are using Crystal reports 2011 with SQL Server 2008 R2. We are trying to use dynamic parameters and using command object to populate the dynamic pick list.
The dynamic picklist is not populating and showing just a empty textbox while running on 64bit. I tried to run the profiler and there is no db command executed.
If I use a view instead of command object for populating the parameter - then it works. If I set the IIS to have 'Enable 32 bit application' to true, then even the command object works works. Is this a problem with choosing the correct driver? If so how do I do that?
Any ideas/help?
Thanks
Shankar.
This seems to be a bug in the crystal reports 2011 version.
More details:
http://scn.sap.com/message/14117796
http://scn.sap.com/thread/3342435?start=30&tstart=0
Thanks
Shankar.
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: