Yes. Never.
As they told me, to MS this is a Crystal Report problem. They are not going to do anything to resolve this issue.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We have developed a .Net C# program that uses Crystal reports to create a report from raw data. We started getting customers with crystal reports errors. The only common thread was it started happening after a specific date. After tracing it down we came up with KB3102429 as being the issue.
The app is developed in Visual Studio 2008 and uses Crystal Reports for Visual Studio 2008. Would an upgrade have solved this issue ?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Yes. Never.
As they told me, to MS this is a Crystal Report problem. They are not going to do anything to resolve this issue.
Does anyone know when MS will release a patch to correct the problem?
CR11R2 has the same problem.
As many have already said, it is related to KB3102429 and the fonts it installs.
Our testing showed the following OS systems as relates to this update:
Win 7.1 Pro (it is an Optional update)
Win 8 (Important)
Win 8.1 Pro (Optional)
Win 2008 (Didn't see it available as an update)
Win 2008 R2 (Optional)
Win 2012 (Optional)
Win 2012 R2 (Optional)
Also, from Microsoft's link on this update: https://support.microsoft.com/en-us/kb/3102429
They say:
"Known issues in this update
Microsoft .NET Framework C# applications that were developed in Microsoft Visual Studio 2010 or Microsoft Visual Studio 2008 and that use SAP Crystal Reports to create reports from raw data generate Crystal Reports error messages.
In Crystal Reports version 9 (Crystal 9) and version 10 (Crystal 10), the "export as PDF" functionality fails."
They don't mention CR11 at all. From what I've heard here and elsewhere, CR11R2 might be the way to go for those of us that use CR9 or CR10. There was a similar problem with Times New Roman fonts a couple of years ago, and a few people back then said CR11R2 didn't have this issue.
I'd really like to know for certain if CR11R2 never has this problem, as we would consider migrating from CR10 to CR11R2, for who knows when MS will release a security update that causes this issue.
Hope this helps.
Doug
Hey all, I found this link on another message board that resolved for me without having to roll back security updates. Hopefully it helps: