Crystal reports error 'unable to cast COM object of type 'crystaldecisions.reportappserver.controllers.reportsourceclass'

Question

0.00/5 (No votes)

See more:

VS2019

Hello,
I'm using VS2019 with Crystal Reports version 13.0.3500.0. When I'm trying to create a pdf on production machine i get the following error "Error message: Unable to cast COM object of type 'CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass' to interface type 'CrystalDecisions.ReportAppServer.Controllers.ISCRReportSource'. This operation failed because the QueryInterface call on the COM component for the interface with IID".

I opened my project on VS2015, convert Crystal Reports to 13.0.2000.0 and everything works fine on production machine.

Is there a solution for this error without going back to VS2015? I can't update CR on production machine, because I might have errors on the other applications running with CR 13.0.2000.0 version.

Thank you in advance.

What I have tried:

I added to app.config the dependency lines based on this article but I still get the same error: Crystal Reports, Developer for Visual Studio Downloads - Business Intelligence (BusinessObjects) - Community Wiki[

Posted 28-Jan-20 20:22pm

Chriz12

Updated 28-Jan-20 21:42pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CHill60 · Answer 1 · 2020-01-28T21:43:00

You say you can't update CR on the prod machine, then don't build with a newer version on your dev machine! :-)

The new version of CR is likely to be backward compatible but old versions cannot cope with new functionality they know nothing about.

Try targeting an earlier version of .NET in your build and check the framework version on the production machine - note

Quote:
As of SP 26 we no longer support .Net Framework 3.5 and recommend upgrading to 4.5.2 or above

I personally would set up a machine (probably virtual) with the new versions and regression test the "other applications", then bite the bullet and upgrade across the board.