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
    2015-12-14T13:32:00+00:00

    We have the same problem with KB3102429 and opened a support ticket with Microsoft. This is what they told us:

    "This is a third party issue related to SAP Crystal Report. Microsoft will not be involved in a solution for an external problem. Please contact with SAP to resolve this problem."

    So don't expect any help or solution to this problem from Microsoft.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-12-12T23:16:11+00:00

    I can confirm that uninstalling KB3102429 resolved this problem for our internal users but you also need to prevent it from being installed again by disabling windows updates!

    This is a HUGE HUGE problem and hope Microsoft resolves it very SOON.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-12-11T21:33:36+00:00

    Do you have CRXI R2?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-12-11T21:32:11+00:00

    This issue also happened about 2 years ago.  I saw a thread (on SAP?) that said Crystal XIR2 didn't have this problem.  Do you have R2?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2015-12-11T10:54:02+00:00

    I can confirm that uninstalling KB3102429 resolved this problem for our internal users but you also need to prevent it from being installed again by disabling windows updates!

    This is a huge problem hope Microsoft resolves it very soon.

    Was this answer helpful?

    0 comments