Internal error when generating PDF in QA about crystalreportsninja HOT 3 CLOSED

First confirm that the same versions of ninja and the crystal reports runtimes are installed across your environments.

What version of ninja are you running? What is the version of the Crystal Runtimes installed on the servers?

The latest version of Ninja can be found at the link below. The parameters may be different than what you are using now depending on how old the version of ninja you are using is. The documentation on the main project page is decent. I would suggest starting there if you choose to upgrade to the latest.

https://github.com/mhertzfeld/CrystalReportsNinja
https://github.com/mhertzfeld/CrystalReportsNinja/releases/tag/v1.8.0.0

from crystalreportsninja.

The one that I'm using is indeed the older one. It's from here:

https://github.com/rainforestnet/CrystalReportsNinja

, and it works on both my worksation and the server where it will be deployed. But it only works in Dev and Prod ; but there it works perfectly.

On that server where we will be deploying it, it won't be possible to upgrade the crystal runtime. I tried, and management of that server refuses to make any changes. But again, Dev and Prod work fine ; so even if I could escalate, they would ask why everything is working perfectly in Dev and Prod, and I wouldn't have an answer for them.

I tried the version from mhertzfeld that you shared, and as you say the parameters from the older version don't work, even in Dev/Prod.

So I guess the next step is to change the parameters, to match the requirements of the mhertzfeld version.

Unfortunately, I can no longer build it. This is unrelated to the thread, but yesterday I tried to update Visual Studio 2017 to the latest build. Little did I know, that Microsoft was upgrading to 2019. Now, there are missing components. So that complicates things, but it means that I have to use an executable that's already built.

Alright, I'll go through the docs at mhertzfeld, and see what the parameter difference are.

T & R,

from crystalreportsninja.

After weeks of chasing down rabbit holes, it looks like the problem was basically typos. Some of the entries in the tnsnames.ora were spelt wrong, and also at least one of the System DNSs wasn't configured properly. Everything is working fine, with the older version of CrystalRuntimeNinja.

Thanks everyone, for their suggestions.

from crystalreportsninja.