Purpose
This is a list of fixed issues in Service Pack 15 for Crystal Reports for Visual Studio (CRVS).
Overview
This wiki documents 5 issues and 3 Enhancement Requests that have been addressed in Service Pack 15 for CRVS. The issues are documented in individual KBases. For details, see the table under the List of Fixed Issues heading. “SAP Crystal Reports, developer version for Microsoft Visual Studio” can be used with Visual Studio 2010 to 2013 as well as Visual Studio 2015.
New in this Release
- Added support for Visual Studio 2015 RC.
- Added an easy way to use Print Output Control in WinForm Viewer.
- Addressed several Incidents.
- Support for FireFox ESR 38.
Where to Download Service Pack 15
Service Pack 14 for “SAP Crystal Reports, developer version for Microsoft Visual Studio” can be downloaded using the links documented in the Document SAP Crystal Reports, developer version for Microsoft Visual Studio Updates & Runtime Downloads. The Document includes links for the runtime MSM, MSI files and more. Developer Help files can be downloaded from the following links
SAP Crystal Reports .NET API Guide
SAP Crystal Reports .NET SDK Developer Guide
Report Application Server .NET SDK Developer Guide
Report Application Server .NET API Guide
List of Fixed Issues - Note: SAP is no longer using Adapt - SAP Note will have link to Work Bench ID
2051790 1916075CSS / ADAPT ID | Synopsis | KBA number | SAP Note ID |
|---|---|---|---|
| Incident 663010 | PrintOutputController printmode from viewer does not print/export the tab view | 2209712 | |
| Incident 577155 | Error in Conditional Formula no longer generates a valid .NET SDK error message | 2194352 | |
Incident 508399 | VS 2015 Community not detected | 2181302 | |
| Incident 205148 | Get Saved XLSX Export options gen Exception | 2181164 | |
| Incident N/A | Printer Tray in the new POC feature did not use what was saved in the report |
Known issues:
Issue has been found - Located in the \crystalreportsviewer13 folder under the framework there is a crviewer.aspx file. Delete ALL copies of it. It is not required and can cause bobj not defined and possibly an AllInOne error in WEB applications.
Installing onto Windows 10 x86 format indicates there is no VS installed - as a temporary workaround create the 64 bit regsitry key the installer is looking for:
HKLM\SOFTWARE\Wow6432Node\Microsoft\DevDiv\vs\Servicing\14.0\professional
Create key named “Install” REG_DWORD and value as 1
For Web applications and Framework 4.x updates with 4.6 installed the CR Viewer folder will get a \4_6_xxx added to the path.
To work around this copy the \CrystalReportViewer13 folder to your project and add the following to your web.config file:
We discovered as soon as you update your version of 4.6 framework it's going to rename the folder being used.
Work around now is to do this...
add the CrystalReportViewer13 folder to your project, copy it into you app folder. then update your web.config file with the following:
<configSections>
<sectionGroup name="businessObjects">
<sectionGroup name="crystalReports">
<section name="crystalReportViewer" type="System.Configuration.NameValueSectionHandler"/>
<section name="rptBuildProvider" type="CrystalDecisions.Shared.RptBuildProviderHandler, CrystalDecisions.Shared, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304, Custom=null"/>
</sectionGroup>
</sectionGroup>
</configSections>
<businessObjects>
<crystalReports>
<crystalReportViewer>
<add key="ResourceUri" value="/crystalreportviewers13"/>
</crystalReportViewer>
</crystalReports>
</businessObjects>
<appSettings>
...
This will redirect all requests to that viewers folder.
Related Content
Related Documents
SAP Crystal Reports, developer version for Microsoft Visual Studio - Supported Platforms
Crystal Reports for Visual Studio 2010 - Service Pack 1 - Fixed Issues
Crystal Reports for Visual Studio 2010 - Service Pack 2 - Fixed Issues
Crystal Reports for Visual Studio 2010 - Service Pack 3 - Fixed issues
Crystal Reports for Visual Studio 2010 - Service Pack 4 - Fixed issues
SAP Crystal Reports, developer version for Microsoft Visual Studio - Service Pack 5 - Fixed Issues
SAP Crystal Reports, developer version for Microsoft Visual Studio - Service Pack 6 - Fixed Issues
SAP Crystal Reports, developer version for Microsoft Visual Studio - Service Pack 7 - Fixed Issues
SAP Crystal Reports, developer version for Microsoft Visual Studio - Service Pack 8 - Fixed Issues
SAP Crystal Reports, developer version for Microsoft Visual Studio - Service Pack 9 - Fixed Issues
SAP Crystal Reports, developer version for Microsoft Visual Studio - Service Pack 10 - Fixed Issues
SAP Crystal Reports, developer version for Microsoft Visual Studio - Service Pack 12 - Fixed Issues
SAP Crystal Reports, Developer version for Microsoft Visual Studio - Service Pack 13 - Fixed Issues
SAP Crystal Reports, Developer version for Microsoft Visual Studio - Service Pack 14 - fixed Issues
SAP Crystal Reports .NET API Guide
SAP Crystal Reports .NET SDK Developer Guide
5 Comments
Andrew Scott
The "New in this Release" section above is just a copy of the section from Service Pack 14 page, it hasn't been updated for SP15.
Presumably it should list that Windows 10, Microsoft Edge and VS2015 RTM are now supported?
Kevin Hicks
I am getting "unreachable code after return statement" after allInOne.js loads. I do not have crviewer.aspx as referenced above. I refreshed the app on the server and removed copy local from the cr references. Not sure if the issue will reappear, but it seems to have cleared for now. If it happens again, then I might uninstall dist. from server and start with clean install.
INFO: Win Server 2008 x86, .net 4.5.1, 564 files and 49 folders in crreportviewer13 folder, published site from VS 2015, upgraded CR on server from SP14
Don Williams
Please post questions to the forum
Former Member
Not mentioned in the release notes is that date time fields now appear to round up automatically e.g. a value of 31st December 2015 23:59:59.980 passed in to a report outputs 1st January 2015 00:00:00.000. This is a very significant change for the way we use reports.
Don Williams
Please post the issue to Forums with example reports etc. and I will look into it.
Thank you