Our reporting services migrated from SSRS 2005 to SSRS 2016. In one specific report, a particular field of looks different on the pdf export. The font that's specified in the report rdl file for that specific field was internally designed a long time ago. We thought the problem had to do with it not being installed in the new server and we proceeded to installing it. After the installation, the result looked different (meaning that the recently installed font was being used) but still very different from the pdf export on the original server. Keep in mind that the rdl files for the report are exactly the same.
My questions is: is it possible to configure some kind of font mapping at server level, so it will replace one font for other, when exporting to pdf?
Any other ideas that explain why the same rdl file looks different in the two SSRS servers when exported to PDF?
Thanks in advance!
Related
I have a crystal report .RPT file which was created in 2004. I am having trouble opening it using software like VB or Crystal Report. It shows "Failed to open Document", follow by "Invalid Report Schema". Seems like the file itself it corrupted, but there is an application generating reports using this file that is still running fine, and it is able to read the file without any problem.
Is there any other software I can use to possibly open this file up? I need to edit the formula expression in a couple fields. When I tried NotePad++, it shows a bunch of unreadable characters which don't help at all. By the way, this file seems to be consisted with a bunch of reports. (There are about 10 reports within this .RPT file.)
I am not sure what the problem is here, could anyone please help me? Any help/suggestion is greatly appreciated!
Thanks,
In that era of Crystal Reports, version 10 would have been the current release. Through version 10, .rpt files could not be successfully opened by any version earlier than the version which last saved the file. Ergo, to open and edit the file, you need the designer/editor for the version which produced that file, or else a newer designer/editor.
If your current Crystal Developer tool wont open it, then it is from a newer one than you are using, or it is truly corrupted ( but since you say it is running well within an application then it's almost certainly not corrupted ).
You need to determine specifically what version of Designer DLL is being invoked by the application that is running the report. Open the source code project and look at the REFERENCES, get the name and GUID of the CRAXDRT.DLL ( or CRAXDDRT.DLL ) and then find exactly that entry in the registry. There you will see which version of Crystal Designer deployed that CRAXDRT.DLL. THAT is the edition you should be able to open the file with.
If you dont have that edition in house, you will have to go to SAP ( or eBay , etc ) and buy one. The oldest SAP sells now is version 11, which should be able to open 8.5 rpts and above. version 11 no longer has support from SAP ( yes, they sell it but no longer sell support, I know, it was only a week ago I talked to them about upgrading my v10 to something newer ). And v12 support is soon to be dropped.
It looks like you are at the crossroads of a Crystal upgrade. If you are still working with VB6 as your application language, then V11 R2 is probably your best bet. g'luck.. I feel your pain. I been there.
Since migrating from Windows Server 2008 to Windows Server 2012, ligatures (eg. "fi") are getting replaced with X's when a report is exported to PDF. This occurs when exporting directly from Report Builder 3.0 on the server, and also from any Dynamics CRM 2011 client. The version of SQLServer/SRSS is 2012.
These same reports and same font (Calluna Regular) have always worked fine for us on Windows 2008/SQL 2008. I have observed that on 2012 the ligatures are visible in the text from Report Builder before exporting whereas on 2008 you do not see them at all.
So what can I fix to be able to continue exporting all text successfully? I should add we are viewing the PDFs with Adobe Reader 11.0.07.
Happy to provide screenshots to illustrate the problem, but not sure how to attach them here as this is my first post. Thanks in advance for any assistance you can offer.
As a workaround, I used FontForge to remove the ligature glyphs from the font in question. So that one's solved but I'm sure it will come up again. Interesting that a different TT font also containing ligatures renders to PDF just fine, although it does it using the individual letters not the ligature. The problem must be in how the PDFs are created by SRSS; any further insights from anyone will be appreciated.
This may be a newbie question, and I have done quite a lot of searching for an answer but have had no luck.
I am using SSRS on SQL Server 2008 R2 (Standard edition) to generate XML reports. I have developed my report in Report builder 3 and uploaded the report to the Report server.
So far so good
Now I want to have a subscription that generates the reports in XML format and deposits it into a folder
No problem with this straight forward enough
How do I install an XML transform or specify the actual XML schema for the rendered document as I don't want to manually handle the generated report.
In the Report Builder software there appears to be a report property where I can specify as path which would have to be to a file on my local desktop but nothing on how to supply a similar file to the reporting server to use.
How do I do this?
And I thank all of you kindly stackoverflow souls in advance for your collective wisdom.
The answer to this is Read the Manual !
However finding information through the myriad of MS pages is an excercise in Google-foo
and old fashioned primary school collage.
You upload XSL through the Report Manager UI using IE and make sure that you have a server side path specified in the DataTransform field in Report Properties in ReportBuilder 3 for your RDL file
The essential confusion that I suffered from was that I thought the XSL transform would be incorporated into the RDL file for publication to the report server. It isn't
SO
For the DataTransform property:
1 A local absolute file path with a drive letter will not work
2 Use a path that makes sense on the report server
3 Either a relative path to the XSL file from the location of the RDL file
OR an absolute path from the Report Server should be used
Angus
I am using visual studio 2008 and reporting service 2008.
I created a .rdl reports. Now I want to convert .rdl to .rdlc. How can I do it?
Good question. According to spec whey should be more or less the same, but in reality they differ wildly depending on version. For instance if I open an RDLC file I created in Visual Studio 2010 in Report Builder 3.0 it works. But if I make a change in my RDL(C) file and try to open it in VS2010 I first get asked if I want to convert it to RDLC 2008 format (yes) and then I get the error message "The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition' which cannot be upgraded."
There is nothing to convert. All you have to do is to rename the file to .rdlc. This converts it from a server report to a client report. The underlying schema is the same, whether it's an .rdl or .rdlc file.
Take a look at FAQ #8 here: http://www.gotreportviewer.com/
I found working with MS support that converting an RDL to RDLC merely by changing the extensions results in a ReportViewer Control HTTPHandler error which is shown with a style of "dsiplay:none". It accuses the developer of not including the HTTPHandler in the web.config, when it is actually in the web.config. Using an rdlc created by VS in that project, then the reportviewer opens just fine and properly displays. MS support and I are still researching what other changes need to be made, but as of now, I can let people know not to drink the MSDN Kool-Aid.
I also tried changing the schemas namespace in the XML file and I got the same report definition cited above.
i have read this article about custom report items(CRI)
http://msdn.microsoft.com/en-us/magazine/cc188686.aspx
The only problem is that CRI are only usable in reporting service and not in local reports. My question is it possible some how to use CRI in local reports( RDLC ). Also i am interested in which version of reporting service is this possible, if possible
Best Regards,
Iordan
Custom report items are not supported in .rdlc files. (http://msdn.microsoft.com/en-us/library/ms251712(v=vs.90).aspx) This is likely the approach taken by Microsoft because the ReportViewer used with these files is a free control, while more complex features like third-party controls are supported only on a full SQL Server report server.
One thing in particular I have done in the past to get around this is generate custom charts/controls/images etc. As images and then send them into the report as an image. Not an ideal solution but it works.