Skip to Content
Former Member
Dec 06, 2010 at 12:48 AM

deploying crystal reports 8.5 - error in exporting to RTF & PDF


Hi guys. I'm at my wits end, trying to get a valid build of a legacy app running reports under Crystal 8.5 going.

I've scoured google for days, and I've tried almost everything people have suggested. At the moment I've got the installer working, it installs and registers all the crystal dll's that everyone says are needed. However, when I try and and export a report to RTF or PDF (other options like excel work fine), it simply dies, doing basically nothing. The save to disk dialog just closes and nothing happens. If I rename or delete crxf_rtf.dll, the program will crash or hang, indicating that this is the file responsible for exporting to rtf.

However, the only machine in our office that this will work on is one with a C:\Program Files\Seagate Software\crtslv.dll file.. Same kind of test indicates that on this machine, the above file is being used for exporting. So, where am I going wrong? It seems ludicrously difficult to find a straight, no-nonsense guide on how to deploy crystal reports 8.5; the official documentation doesn't even mention it! What is the easiest way to do this?

I have tried several third-party options ( ) like these..

Any ideas?

Ok so here's a further breakdown with some more information; hoping it might help someone to come up with an answer...

If I install a crystal "distributable", like the one linked above, and then install my project (with all crystal stuff turned off in the installer), everything works perfectly apart from exporting reports to rtf.

If I make my own installer, following the Runtime.hlp and the crpe32.dep, and put all dll's in the windows/system32 folder (apart from two, can't remember their names), I get two different errors, depending on the version of crpe32.dll I use.

One gives me "Error 20599: Cannot connect to SQL Server", whenever I try and run a report.

The other gives me "Error 20000: N", whenever I try and run a report.

Anything sound familiar here guys? I have dll dependency headache.

Again, more info - I just checked out the PC's already in deployment (we had to re-do in the installer for some changes, the guys who did it originally aren't around anymore), and here is a list of the dll's installed on the machine.. what deployment method would this point to? And how can I replicate it? I'm not sure if I grabbed all the required DLL's from the client machine, as it didn't seem to follow the Crystal 8.5 deployment instructions, I could have easily have missed some? So I can't just use what I've got to create an installer and hope that it works...