Windows Update KB3102429 Does not play well with Crystal Reports for Visual Studio 2008

Anonymous
2015-11-20T18:50:29+00:00

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 ?

Windows for home | Previous Windows versions | Apps

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.

0 comments

50 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2016-01-06T13:04:50+00:00

    There is always that danger. We've opted to have users remove and hide the update (or in the case of an update server, remove it from the deployment list) since the only reason for the update was to add currency symbols that we and our customers will never use. Of course there's always the danger of the update being reapplied as well. Getting rid of the update seemed like the lesser of the two evils.

    Naturally, if you can swing it, changing the fonts in your reports away from the affected fonts solves the issue entirely. For us, we have hundreds of templates out there and such a change would take a significant amount of time that we don't have at the moment.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2015-12-23T22:13:56+00:00

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2015-11-30T20:54:34+00:00

    Same problem: Crystal 10, exporting to PDF, error "Failed to export the report". Reported and reproduced on Windows 8.1. Our problem appears to be with Times New Roman and Arial fonts only. All other fonts tested so far worked fine. Problem observed with v6.88 of both of those fonts, included in KB3102429, installation of which definitely caused the problem. (I suppose it is possible it's not the font files causing the problem but some other file included in the update. I have not tested that.)

    Previous v6.87 of both fonts worked fine. V6.90 of both fonts (Windows 10) also seem to work fine. We had a similar problem with TNR v6.85 (initial Windows 8.1 release) but it seems to have been fixed by v6.87. 

    KB3102429 has different versions of fonts for Windows 7. I have not yet tried to reproduce the problem on Windows 7 but I have seen reports that this update does cause a similar problem on Windows 7.

    A workaround is to replace the TNR and Arial fonts in the report with other fonts, at design time or runtime. I can confirm that uninstalling KB3102429 reverted to v6.87 of both fonts and solved the problem for me.

    See also this SAP forum.  Peace.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2015-12-04T19:28:35+00:00

    Tried with Crystal XI (C++ app. using RDC) on Win2008 R2 and don't see the issue. Any idea if I'm missing something or I shouldn't expect any impact?

    Thanks!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2015-11-26T09:04:34+00:00

    This issue is also affect the normal Crystal Reports version. The error messages which you get are "Cannot find the QE property" or "Failed to export the report".

    After deinstall the update the export is function again.

    Was this answer helpful?

    0 comments