on 10-31-2015 8:37 PM
Hi,
I would like to know when Crystal Reports can work on Windows 10.
I saw that fix 15 holds a fix if I understand correctly but only for Visual Studio.
Any roadmap to support Windows 10?
Regards,
Roei
What version of CR are you asking about?
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow me on Twitter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm confused...
You say:
would like to know when Crystal Reports can work on Windows 10.
I saw that fix 15 holds a fix if I understand correctly but only for Visual Studio.
CR for VS is version 13.x. So, if you have SP 15, you're set. Perhaps you are looking for SP 15? If that is the case, look here:
- Ludek
Hi Don,
Yes I did.
I also tried to install the msi files below:
For 32 bit: http://downloads.businessobjects.com/akdlm/cr4vs2010/CRforVS_redist_install_32bit_13_0_15.zip
For 64 bit: http://downloads.businessobjects.com/akdlm/cr4vs2010/CRforVS_redist_install_64bit_13_0_15.zip
but got the following error when trying to see the report via the CR viewer in Windows 10
Thanks in advanced,
Roei
This could be CR related. Or not. Googling the error, I get tons of posts re. possible issues and solutions. One of the better posts: https://www.ascadnetworks.com/Guides-and-Tips/IE-error-%2522Could-not-complete-the-operation-due-to-...
So, for now I'd start really simple;
New one line app;
Add a viewer to a form
in Page INIT add; crystalreportsviewerone.reportsource = <path to a saved data report>
Compile.
Throw this app on the server.
Test. If this app works, more than likely the issue is not CR. Rather something else is going on in your app. You could test this possibility by commenting out the CR code in your app and see if the app runs.
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow me on Twitter
Got Enhancement ideas? Use the SAP Idea Place
See if this is the problem:
Symptom
Framework 4.6 causes Crystal Reports for Visual Studio to create a unique folder path to the Crystalreportsviewer13 folder in IIS and IISExpress DEV.
Environment
Reproducing the Issue
Hi Don, We’re aware of such problem. Actually it’s related to .Net Framework 4.6, not only limited to Win10 or Windows Server 2016 preview(these OS by default installed .Net 4.6 ). If you install .Net 4.6 on Win7 there will be same issue. The root cause is MS provide the update to .Net Framework 4.6 via windows update, then the small version of .Net 4.6 will changed. For ASP.NET web site target to .Net 4.6 app pool, CR viewer will try to find the viewer resource file(js & icon) from ..\aspnet_client\system_web\4_6_xx\crystalreportviewers13\ The highlight xx is the small version of .Net Framework 4.6. On Win10 RTM, it’s 4_6_79; on Win7+.Net 4.6 it’s 4_6_81, if user installed recent KB3098786 it will be 4_6_118… The version number will change again if next KB update for .Net Framework 4.6. So please create a BOSAP case for it. At least in SP16 we need add more symbol link to support different small version of .Net Framework 4.6. And a better solution is change the path of viewer resource file loaded, eg, point to a virtual folder under IIS. That required fix in Viewer side and need more time, we will try to implement it in SP16… Thanks, Soda
Resolution
Our Developers are aware of this issue and we should be able to provide a fix in Service Pack 16
The issue is related to .Net Framework 4.6.
The root cause is MS provide the update to .Net Framework 4.6 via Windows Update
ASP.NET web site will target the .Net 4.6 app pool, CR viewer will try to find the viewer resource file(js & icon) from
..\aspnet_client\system_web\4_6_xx\crystalreportviewers13\
The xx is the small version of .Net Framework 4.6.
The version number will change again when the next KB update for .Net Framework 4.6 is installed.
Current work around is to update the Web.Config file to include the updated version of the Framework
And then to copy the \CrystalReportsViewer13 folder into the new path:
..\aspnet_client\system_web\4_6_xx\crystalreportviewers13\
For updates and the latest downloads please go to this link:
http://scn.sap.com/docs/DOC-7824
Home page is:
http://scn.sap.com/community/crystal-reports-for-visual-studio
Keywords
Crystal Reports for Visual Studio, cr for vs, \aspnet_client\system_web\4_6_xx\crystalreportviewers13\, 4.6 framework, iis
Dear Don,
The workaround you suggested fits for a single installation, since we have thousands of installations world wide, is there any workaround that we can apply so it fits for all .NET versions?
Meaning can we set the path for crystal viewer folder eg. all .NET versions will be guided to Crystal folder?
In our registry we saw that our .NET Framework version is 4.6.00079 however we saw that Crystal Viewer is seeking for its files in 4_6_114 folder, how is it been decided?
Regards,
Roei
Hi Roei,
You can get the latest framework this way:
using (RegistryKey ndpKey = RegistryKey.OpenBaseKey(RegistryHive.LocalMachine, RegistryView.Registry32).OpenSubKey("SOFTWARE\\Wow6432Node\\Microsoft\\.NET Framework Platform\\Setup\\Multi-Targeting Pack\\v4.6\\"))
foreach (string versionKeyName in ndpKey.GetSubKeyNames())
{
//if (versionKeyName.StartsWith("v4"))
{
RegistryKey versionKey = ndpKey.OpenSubKey(versionKeyName);
string name = (string)versionKey.GetValue("Version", "");
string sp = versionKey.GetValue("SP", "").ToString();
string install = versionKey.GetValue("Install", "").ToString();
if (install == "") //no install info, must be later.
{
btnSQLStatement.Text += "\nFramework Patch: " + name;
btnSQLStatement.AppendText("\n");
}
else
{
if (sp != "" && install == "1")
{
btnSQLStatement.Text += "\nFramework Patch: " + name + "\n";
}
}
if (name != "")
{
continue;
}
}
}
Once you have it you would need to copy over the \CrystalViewer13 folder structure every time a new 4.6 framework patch is installed.
I'm not sure how R&D is going to handle this change by MS.... What ever it is SP 16 should have it.
Don
Hi Don,
We looked and examine your suggested code, but the registry path you mentioned, the .NET version number shows the wrong .NET version where windows update do not override this path with the new version.
I owns windows 7 and till 3 weeks ago the Crystal Viewer works, windows update was performed and the KB with the new CLR was update and since then the Crystal viewer is not working.
We are talking about all Windows versions, which makes it a critical issue that I`m sure customers are complaining about this to SAP.
We need an hotfix as soon as possible or a better workaround so we can handle from our platform and release an hotfix as soon as possible.
Please let us know what to do.
Roei
Hi Roei,
Interesting.... So I did some more testing, using 2.0 to 3.5 framework CR generates the correct folder path.
If I select any 4.x framework then IISExpress/IIS automatically generates the wrong path but always inserts the 4_6_xxx path to the viewer even though I selected 4.0, 4.5.1 or 4.5.2...
So I'm thinking this has something to do with the 4.6 framework and possibly now 4.5.x Windows updates. R&D never said why it was happening nor if it's the Framework or the templates or... was causing the problem, they just confirmed it as an issue.
Curious why you do not have 4.6 installed on your Windows 10 image? You first screen shot show 4.6 installed. What OS is this last screen shot.
As for a hot fix, not going to happen, CR for VS is a free product so we only release full builds, not patches ever. Unfortunately when SP 15 was released they did not have time or the resources to fully integrate and test VS 2015 due to 4.2 builds and testing. It consumed most of the DEV resources to get it out to Beta testing.
I assumed you would have 4.6 installed, never tried it without it.
I believe this was all due to 4.6 framework and the project templates in VS and CR. nothing more I can do....
Thinking of another way around this by using a redirect.
See if this works for you, add the CrystalReportViewer13 folder to your project, copy it into you app folder:
<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>
...
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.